D
DriftLoom.ai
OpenClaw skill trust index
🧪 runtime dashboard live
☰ Menu
publisher profilecommunity

qsmtco

qsmtco publishes 5 tracked skills in DriftBot.

Catalog decision: Review-first publisher: this catalog currently carries failed runtime rows or high-risk labels, so inspect individual skills before trusting the brand halo.
5
indexed skills
60
average score
0
manual reviews
2
high-risk labels
catalog evidence snapshotbaseline-v3 coverage 3/5functionality-v2 coverage 3no manual reviews yet2 high-risk labels
Read this row as a catalog snapshot: runtime coverage, deeper follow-on coverage, human review presence, and high-risk concentration before you compare individual skills.

📊 Runtime quality summary

Runtime read: stronger publisher evidence means more than broad coverage — look for low current failure pressure, some functionality depth, and stale-runtime counts that stay under control.
eligible runtime skills: 5latest touch: 19h agono current regressions
Baseline coverage
360% of eligible skills have baseline-v3 receipts
Baseline pass rate
100%3 passed · 0 currently failing
Functionality coverage
3100% of baseline-cleared skills have functionality-v2
Fixture-backed rate
0%0 functionality-v2 rows have richer fixture/example proof
Stale baseline rows
0baseline receipts older than 7 days
Functionality failures
0current failed functionality-v2 rows in the latest publisher state

This is the quality surface for the publisher, not just a directory listing. It shows how much of the catalog has real receipts, how often those receipts are passing, whether richer fixture-backed proof exists, and whether the publisher currently carries regressions, reproduced failures, or stale runtime evidence.

Latest runtime touch: 2026-03-15 12:45 UTC. Publisher-level summaries do not replace skill-level review, but they do make reputation more earned: a publisher with broader coverage, stronger pass rates, and fixture-backed proof looks different from one living on thin smoke tests.

If you want the system-wide view, open the runtime dashboard. If you want the scoring logic, read the methodology.

Fresh runtime sliceStale runtime slice
passedfunctionality-v219h ago
yacy
7/7 passed
passed
passedbaseline-v319h ago
yacy
8/8 passed
passed
passedfunctionality-v222h ago
token-optimizer-qsmtco
6/6 passed
passed
passedbaseline-v322h ago
token-optimizer-qsmtco
8/8 passed
passed
passedfunctionality-v225h ago
tokenqrusher
8/8 passed
passed
passedbaseline-v325h ago
tokenqrusher
8/8 passed
passed

Skills from this publisher

Showing 5 of 5 skills

Label mix on this page

Trusted: 1Use Caution: 2Insufficient Evidence: 0High Risk: 2

This distribution is a quick provenance cue, not a verdict. A publisher can have a mix of safer and riskier skills, so the useful move is to compare patterns here and then open the individual scorecards.

Publisher profiles are best for spotting catalog patterns: repeated shell access, common external services, whether manual review exists, and whether higher-risk labels are isolated or widespread.

On this page: 5 source-scanned, 0 catalog-only, and 0 manually reviewed entries in the current slice.

If you want the scoring logic, read the methodology. If you want the broader landscape, go back to the full index.

session-state-tracker

qsmtco · vsource-scanned
72
overall

Persistent session state management across compaction and restarts via lifecycle hooks

Trustedconfidence: source evidencesource-scanned
+ 1 more
privileged capability
Take: Source-aware scan found higher-privilege capability areas (token), but that alone is not evidence of malicious behavior.
Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

curated-search

qsmtco · vsource-scanned
61
overall

Domain-restricted full-text search over curated technical documentation

Use Cautionconfidence: source evidencesource-scanned
+ 1 more
suspicious
Take: Potentially suspicious implementation signals detected: sudo .
Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

tokenqrusher

qsmtco · vsource-scanned
61
overall

Token optimization system for OpenClaw reducing costs 50-80%

Use Cautionfollow-on functionality checks passed · 8/8confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what passed2026-03-15 07:15 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 7 dayspassedoutput 133 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2927 msbaseline-v3 8/8
RatioDaemon on this skillTokenqrusher sits in the token optimization system for OpenClaw reducing costs 50-80% lane. Functionality-v2 currently passes, the trust label is High Risk, and setup looks advanced.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: rm -rf.
Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

token-optimizer-qsmtco

qsmtco · vsource-scanned
57
overall

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and multi-provider fallbacks. Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. Includes ready-to-use scripts for task classification, usage monitoring, and optimized heartbeat scheduling. All operations are local file analysis only - no network requests, no code execution. See SECURITY.md for details.

High Riskfollow-on functionality checks passed · 6/6confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what passed2026-03-15 10:00 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 99 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2036 msbaseline-v3 8/8
RatioDaemon on this skillToken Optimizer Qsmtco sits in the token optimizer qsmtco lane. Functionality-v2 currently passes, the trust label is High Risk, and setup looks advanced.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: eval(, rm -rf.
Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

yacy

qsmtco · vsource-scanned
51
overall

Control and manage a local YaCy search engine instance.

High Riskfollow-on functionality checks passed · 7/7confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what passed2026-03-15 12:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 120 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2238 msbaseline-v3 8/8
RatioDaemon on this skillYacy looks aimed at control and manage a local YaCy search engine instance. Functionality-v2 currently passes, the trust label is High Risk, and setup looks advanced.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: sudo , password.
Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.
Page 1 / 1

Trust reading guide

Publisher-level summaries help with provenance context, but trust still lives at the skill level. Use this page to compare patterns across the publisher’s catalog, then inspect the raw findings on individual skill pages.

Back to the full index