error-handling — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited error-handling (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Good error handling makes failures visible and recoverable. The worst bug is the one a bare except hides.
you can actually do something useful about it. Otherwise let it propagate to a layer that can.
catch-all. A broad except hides real bugs and turns a crash into silent corruption.
context. Don't except: pass over something that matters. Empty handlers are only OK for genuinely-optional, best-effort side work.
chain the original cause (don't discard the traceback). The message should tell the next reader how to fix it.
Handle gracefully only expected operational errors (network, missing file, bad user input).
on both the success and failure paths.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.