publisher profilecommunity

deeqyaqub1-cmd

deeqyaqub1-cmd publishes 3 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.
3
indexed skills
44
average score
0
manual reviews
1
high-risk labels
catalog evidence snapshotbaseline-v3 coverage 1/3functionality-v2 coverage 1no manual reviews yet1 high-risk label
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: 3latest touch: 29m agono current regressions
Baseline coverage
133% of eligible skills have baseline-v3 receipts
Baseline pass rate
100%1 passed Β· 0 currently failing
Functionality coverage
1100% 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-16 04: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.

Skills from this publisher

Showing 3 of 3 skills

Label mix on this page

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

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: 3 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.

zero-rules

deeqyaqub1-cmd Β· vsource-scanned
51
overall

Intercept deterministic tasks (math, time, currency, files, scheduling) BEFORE they hit the LLM. Saves 50-70% on token costs by resolving simple queries locally with zero API calls.

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

skillfence

deeqyaqub1-cmd Β· vsource-scanned
43
overall

Runtime security monitor for OpenClaw skills. Watches what your installed skills actually DO β€” network calls, file access, credential reads, process activity. Not a scanner. A watchdog.

High Riskfollow-on functionality checks passed Β· 6/6confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what passed2026-03-16 04:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 97 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 1946 msbaseline-v3 8/8
RatioDaemon muttered: skillfence behaved itself under runtime pressure.6/6 functionality-v2 checks passed. Pleasantly boring.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: eval(, password.
Decision cue: Proceed carefully β€” suspicious signals matter more than capability surface alone.

hyperstack

deeqyaqub1-cmd Β· vsource-scanned
37
overall

The Agent Provenance Graph for AI agents β€” the only memory layer where agents can prove what they knew, trace why they knew it, and coordinate without an LLM in the loop. Timestamped facts. Auditable decisions. Deterministic trust. Ask 'what blocks deploy?' β†’ exact typed answer. Git-style branching. Three memory surfaces: working/semantic/episodic. Decision replay with hindsight bias detection. Conflict detection. Staleness cascade. Utility-weighted edges that self-improve from agent feedback. Agent identity + trust scoring. Time-travel to any past graph state. Works in Cursor, Claude Desktop, LangGraph, any MCP client. Self-hostable. $0 per operation at any scale.

Use Cautionconfidence: source evidencesource-scanned
+ 1 more
suspicious
Take: Potentially suspicious implementation signals detected: 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