🔎 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 3 of 3 results for “cli” · runtime: failed · freshness: fresh · sort: relevance

page evidence snapshotruntime-passed: 0 runtime-failed: 3 source-scanned: 3 fresh <24h: 2 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.

google-keep

tag-assistant · vsource-scanned

overall

Read, create, edit, search, and manage Google Keep notes and lists via CLI.

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

+ 2 more

Runtime receipts + what failed2026-03-15 06:00 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 7 daysfirst failed run seen for this lanepassed, runtime_failedoutput 99 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2480 msbaseline-v3 8/8

🕵️ expected proof signal was missing🚫 skill exited with an error

RatioDaemon muttered: google-keep made it to runtime and then fell apart on contact, which is not ideal for a skill asking to be trusted.6/7 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: password.

Decision cue: Review first — functionality-v2 already found trouble.

veille

romain-grosos · vsource-scanned

overall

RSS feed aggregator, deduplication engine, LLM scoring, and output dispatcher for OpenClaw agents. Use when: fetching recent articles from configured sources, filtering already-seen URLs, deduplicating by topic, scoring with LLM, dispatching digests to Telegram/email/Nextcloud/file. Enhanced by mail-client (email output) and nextcloud-files (cloud storage).

High Riskfollow-on functionality checks failed · 0/1confidence: source evidence

+ 2 more

Runtime receipts + what failed2026-03-15 21:31 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfailure repeated in more than one runregression after earlier passblocked_on_external_serviceoutput 375 Bartifacts 1worker oc-sandboxsource stage: cache hitsuite 5621 msbaseline-v3 8/8

RatioDaemon muttered: veille left receipts, just not the ones it was supposed to.0/1 functionality-v2 checks passed before the stumble. The forced external check is the part that made this interesting.

Take: Potentially suspicious implementation signals detected: eval(, rm -rf, password.

Decision cue: Review first — functionality-v2 already found trouble.

tide-watch

chrisagiddings · vsource-scanned

overall

Proactive session capacity monitoring and management for OpenClaw. Prevents context window lockups by warning at configurable thresholds (75%, 85%, 90%, 95%), automatically backing up sessions before resets, and managing session resumption prompts. Use when working on long-running projects, managing multiple conversation channels (Discord, Telegram, webchat), or preventing lost work from full context windows. Includes CLI tools for capacity checks, cross-session dashboards, archive management, and session resumption. Supports any model or provider.

High Riskbaseline safety checks failed · 7/8confidence: source evidence

+ 2 more

Runtime receipts + what failed2026-03-16 00:45 UTC

baseline-v3evidence depth: baseline checks onlytested recently: within 24 hoursfirst failed run seen for this laneexpectation_failed, passedoutput 591 Bartifacts 2worker oc-sandboxsource stage: fresh copysuite 2351 ms

🕵️ expected proof signal was missing

RatioDaemon muttered: tide-watch talked a big game, then missed its own proof signal, which is not ideal for a skill asking to be trusted.7/8 baseline-v3 checks passed before the stumble. The source-mount check is the part that made this interesting.

Observed: 12 /workspace/source-files.txt

Take: Potentially suspicious implementation signals detected: rm -rf, sudo , password.

Decision cue: Review first — baseline-v3 already found trouble.