error-decoder-3946e1 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited error-decoder-3946e1 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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.
Turn a scary error into a clear answer — the way a senior engineer would read it over your shoulder.
You'll often get just an error string or a partial stack trace, with no surrounding code. Always deliver a complete diagnosis anyway — infer the language/framework and the likely context from the error itself, and mark inferences as (assumed — confirm). Never refuse for missing context and never leave bracketed placeholders.
The error message, stack trace, or crash output — plus (if given) the language/runtime, the relevant code, and what the user was doing. Infer anything missing.
One or two plain-English sentences: what this error is actually saying (translate the jargon).
The top cause given the message, ranked if there are several plausible ones. Point at the exact line/frame in the trace that matters and say why.
Concrete, copy-pasteable steps or code. If the cause is uncertain, give the highest-probability fix first, then the fallback.
One line on the underlying reason and a guardrail (a check, a type, a test, a config) that stops it recurring.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.