🔎 Evidence browser

Search the skill radar

Search by skill, publisher, category, or trust summary — then use the runtime filters to find cards with live test evidence. The two main lanes are baseline safety checks first and deeper follow-on functionality checks after that.

⚙️ Filters · 3 active
✨ Quick picks
🏷 Categories

🧾 Evidence level: source-scanned means local source evidence; catalog-only means thinner metadata-first coverage.

🧪 Runtime status: cards can show only the baseline safety lane or the deeper follow-on functionality lane, depending on how far the skill got.

📏 Depth cue: tells you whether the evidence stops at baseline checks, includes follow-on functionality checks, or includes richer fixture/example proof.

⏱ Freshness cue: tells you whether the latest runtime evidence is from the last 24 hours, the last 7 days, or is older and therefore less current.

🩺 Failure confidence: distinguishes a first seen failure from a repeated failure or a regression after an earlier pass, so not every red row means the same thing.

Results

Showing 2 of 2 results for “scottcjn · runtime: passed · freshness: fresh · sort: relevance
This snapshot is for the current page of results, not the whole filtered universe.
Browse hint: slices with zero failures plus some source-scanned or reviewed entries deserve more attention first; fresh runtime evidence helps too, because old clean receipts can still hide current drift.

grazer

scottcjn · vsource-scanned
53
overall

Multi-Platform Content Discovery for AI Agents

High Riskfollow-on functionality checks failed · 9/12confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-15 23:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, ambiguous_entrypoint, expectation_failed, runtime_failedoutput 2.2 KBartifacts 0worker oc-sandboxsource stage: cache hitsuite 4217 msbaseline-v3 8/8
🕵️ expected proof signal was missing🚫 skill exited with an error
RatioDaemon muttered: The runtime lane gave grazer a chance to act normal. It declined and left receipts, just not the ones it was supposed to.9/12 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 , password.
Decision cue: Review first — functionality-v2 already found trouble.

beacon

scottcjn · vsource-scanned
57
overall

Agent-to-agent protocol for social coordination, crypto payments, and P2P mesh.

High Riskfollow-on functionality checks failed · 13/14confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-15 20:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, runtime_failedoutput 5.7 KBartifacts 0worker oc-sandboxsource stage: cache hitsuite 5032 msbaseline-v3 8/8
🕵️ expected proof signal was missing🚫 skill exited with an error
RatioDaemon muttered: beacon made it to runtime and then fell apart on contact, which is not ideal for a skill asking to be trusted.13/14 functionality-v2 checks passed before the stumble. The python help is the part that made this interesting.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: rm -rf, password.
Decision cue: Review first — functionality-v2 already found trouble.