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

Security GitHub Weather Trusted only Higher-confidence picks Lower-friction local candidates Review-first installs Sandbox-tested Fresh runtime Stale runtime Hall of Shame Stronger evidence imports Needs review Clear filters

All categories awesome-index · 5367 catalog-only · 5367 coding-agents-and-ides · 1200 web-and-frontend-development · 924 devops-and-cloud · 392 search-and-research · 352 browser-and-automation · 320 productivity-and-tasks · 204 ai-and-llms · 184 cli-utilities · 180

✨ 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 4 of 4 results for “prior” · runtime: passed · freshness: fresh · sort: relevance

page evidence snapshotruntime-passed: 4 runtime-failed: 0 source-scanned: 4 fresh <24h: 4 manual review: 0

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.

issue-prioritizer

glucksberg · vsource-scanned

overall

Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.

Use Cautionfollow-on functionality checks passed · 6/6confidence: source evidence

+ 2 more

Runtime receipts + what passed2026-03-15 10:45 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 80 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 1974 msbaseline-v3 8/8

RatioDaemon muttered: issue-prioritizer cleared baseline-v3 without trying anything cute.6/6 functionality-v2 checks passed. Pleasantly boring.

Observed: skill-structure-ok

Take: Potentially suspicious implementation signals detected: password.

Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

aiusd

chaunceyliu · vsource-scanned

overall

AIUSD trading and account management skill. Calls backend via MCP for balance, trading, staking, withdraw, gas top-up, and transaction history. Auth priority: MCP_HUB_TOKEN env, then mcporter OAuth or local token file.

High Riskfollow-on functionality checks passed · 7/7confidence: source evidence

+ 2 more

Runtime receipts + what passed2026-03-16 05:30 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 115 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2264 msbaseline-v3 8/8

RatioDaemon muttered: aiusd cleared baseline-v3 without trying anything cute.7/7 functionality-v2 checks passed. Pleasantly boring.

Observed: skill-structure-ok

Take: Potentially suspicious implementation signals detected: rm -rf.

Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

aiusd-skills

chaunceyliu · vsource-scanned

overall

High Riskfollow-on functionality checks passed · 7/7confidence: source evidence

+ 2 more

Runtime receipts + what passed2026-03-16 02:45 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 115 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2216 msbaseline-v3 8/8

RatioDaemon muttered: aiusd-skills behaved itself under runtime pressure.7/7 functionality-v2 checks passed. Pleasantly boring.

Observed: skill-structure-ok

Take: Potentially suspicious implementation signals detected: rm -rf.

Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

email-importance-content-analysis

shingo0620 · vsource-scanned

overall

Judge whether an email is important/urgent using content-based analysis rather than sender name or mailbox labels (which can be spoofed). Use when asked to triage emails, decide priority, detect phishing/social-engineering, or recommend next actions (reply/pay/login/download/click) based on what the message asks the user to do.

High Riskbaseline safety checks passed · 8/8confidence: source evidence

+ 2 more

Runtime receipts + what passed2026-03-16 05:15 UTC

baseline-v3evidence depth: baseline checks onlytested recently: within 24 hourspassed, handled_fake_credentials_cleanlyoutput 266 Bartifacts 2worker oc-sandboxsource stage: fresh copysuite 2401 ms

RatioDaemon muttered: email-importance-content-analysis cleared baseline-v3 without trying anything cute.8/8 baseline-v3 checks passed. Pleasantly boring.

Observed: 3 /workspace/source-files.txt

Take: Potentially suspicious implementation signals detected: password.

Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.