debug-playbook — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited debug-playbook (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.
The order of operations matters more than the tools.
Nothing else is useful until you can make the bug happen on demand.
List 2–3 concrete theories. For each:
If you have only one hypothesis, you're not thinking hard enough — or it's so obvious you should skip to step 4.
Add the cheapest probe that separates your top two hypotheses.
git bisect when the timeline is wide and the test is binarystrace / dtrace / perf when the surface is the runtime, not the codeResist the urge to add logs everywhere. Add one at the pivot point.
When observation singles out the hypothesis, point at the line. Not the region — the line.
Ask: why does this line break? What invariant did we assume here that isn't true?
Minimum change that resolves the root cause. Nothing adjacent.
Add a test that fails without your fix and passes with it. The test should target the condition, not mimic the scenario.
Short report:
What happened: <observable>
Root cause: <one sentence, concrete>
Why tests missed it: <honest answer>
Fix: <the change, minimum>
Regression guard: <the test>If you can't write this report, you haven't finished debugging.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.