publisher profilecommunity

echennells

echennells 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.

indexed skills

average score

manual reviews

high-risk labels

catalog evidence snapshotno baseline-v3 receipts yetno functionality-v2 receipts yetno 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: 2latest touch: n/ano current regressions

Baseline coverage

00% of eligible skills have baseline-v3 receipts

Baseline pass rate

0%0 passed · 0 currently failing

Functionality coverage

00% 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: n/a. 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 slice Stale runtime slice

No runtime receipts for this publisher yet.

Skills from this publisher

Showing 3 of 3 skills

Label mix on this page

Trusted: 0Use Caution: 1Insufficient 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: 2 source-scanned, 1 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.

sparkbtcbot

echennells · vcatalog

overall

Set up Spark Bitcoin L2 wallet capabilities for AI agents.

Insufficient Evidenceconfidence: limited evidencecatalog-only

+ 1 more

Take: Indexed from the community catalog. Source-aware static analysis and manual review are still pending.

Decision cue: Thin evidence slice — do not treat this card like a verified green light.

sparkbtcbot-proxy-deploy

echennells · vsource-scanned

overall

Deploy a serverless Spark Bitcoin L2 proxy on Vercel with spending limits, auth, and Redis logging. Use when user wants to set up a new proxy, configure env vars, deploy to Vercel, or manage the proxy infrastructure.

Use Cautionconfidence: source evidencesource-scanned

+ 1 more

Take: Source-aware scan found higher-privilege capability areas (wallet, token, email), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

sparkbtcbot-proxy

echennells · vsource-scanned

overall

Use a Spark Bitcoin L2 wallet proxy for AI agents via HTTP API. Check balances, send payments, create invoices, pay L402 paywalls — all without holding the mnemonic. Use when user mentions "Spark proxy," "wallet API," "L402," "proxy payment," "bearer token auth," or wants secured Bitcoin capabilities for an agent.

High Riskconfidence: source evidencesource-scanned

+ 1 more

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