publisher profilecommunity

chris6970barbarian-hue

chris6970barbarian-hue publishes 4 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.
4
indexed skills
53
average score
0
manual reviews
1
high-risk labels
catalog evidence snapshotbaseline-v3 coverage 1/4functionality-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: 4latest touch: 16h agono current regressions
Baseline coverage
125% 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
1current 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 09: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 4 of 4 skills

Label mix on this page

Trusted: 0Use Caution: 2Insufficient Evidence: 1High 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: 4 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.

glitch-homeassistant

chris6970barbarian-hue Β· vsource-scanned
54
overall

Control smart home devices via Home Assistant API.

Insufficient Evidenceconfidence: 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.

glitch-skillstore

chris6970barbarian-hue Β· vsource-scanned
53
overall

Search, install, and create OpenClaw skills with intelligent matching.

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

skillstore

chris6970barbarian-hue Β· vsource-scanned
53
overall

Search, install, and create OpenClaw skills with intelligent matching.

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

glitch-dashboard

chris6970barbarian-hue Β· vsource-scanned
51
overall

Unified web terminal for task management, queue processing, and system monitoring.

High Riskfollow-on functionality checks failed Β· 8/9confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-15 09:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, runtime_failedoutput 2.5 KBartifacts 0worker oc-sandboxsource stage: cache hitsuite 2875 msbaseline-v3 8/8
πŸ•΅οΈ expected proof signal was missing🚫 skill exited with an error
RatioDaemon muttered: The runtime lane gave glitch-dashboard a chance to act normal. It declined and made it to runtime and then fell apart on contact.8/9 functionality-v2 checks passed before the stumble. The package json entrypoints is the part that made this interesting.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: rm -rf, sudo .
Decision cue: Review first β€” functionality-v2 already found trouble.
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