Resilience audit
Failure-mode audit (FMEA for software) — for each way the system can fail (network, storage, partial completion, crash, concurrency, bad input), check whether code DETECTS, HANDLES, RECOVERS, and COMMUNICATES it. Triggers on: "/resilience-audit", "resilience-audit", "FMEA audit". Use when touching network, storage, async, retry, or rollback paths. Flags data loss, silent-success-on-failure, missing rollback/retry/idempotency. Reports; does not fix unless asked.From its SKILL.md
npx -y skills add HetCreep/CoalMine --skill resilience-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.5 KB, as published. Nobody here has run it
Resilience Audit
<!-- SHARED:LANGUAGE_HEADER -->For every operation: "what happens when this FAILS?" Report; do NOT fix unless asked.
Failure categories
- External I/O — network down/slow, API 4xx/5xx/timeout, rate-limit. Retry w/ backoff? Timeout set? Clear error vs hang?
- Storage — disk full, permission denied, partial write. Atomic write (temp+rename)? Cleanup on failure? Existing good copy untouched?
- Partial completion — half-done op (50/100 files). Reported as FAILURE, never success.
- Crash / OOM — killed mid-op. Idempotent restart? No orphaned half-state?
- Concurrency — two instances, race, deadlock. Locking / idempotency / safe re-entry?
- Input / data — malformed, null, truncated, huge. Validate at boundary? Fail-fast?
- Dependency down — fallback/cache/graceful degrade? Clear error vs silent hang?
- Resource exhaustion — bounded? Backpressure? Cleanup on error path?
Per-stack timeout/atomicity/idempotency patterns to grep: read references/checks.md before scanning.
For each failure point, check 4 things
- Detected? code notices it (doesn't swallow)?
- Handled? retry/fallback/fail-clean — not ignored, not silent-success?
- Recoverable? rollback/idempotent; no data loss or corruption?
- Communicated? clear error to user+log; not a hang, not a false "done"?
Discipline
- Trace actual failure path (cite file:line). Don't assume handling exists; prove it.
- "partial = failure" — any path reporting success on partial completion = CRITICAL.
- "logged" ≠ "handled" — swallowed+logged error that corrupts state or returns success = CRITICAL.
Fix mode (choice-gated)
After the report, present via ask_question:
- Fix safe ones — add missing timeout, null/input validation, clear error+log on unhandled path. Each: checkpoint → fix → build+tests → revert if newly red.
- Let me pick — user-selected fixes only.
- Report only — change nothing.
NEVER auto-fix: retry/rollback/recovery/atomicity logic (semantic changes can introduce new failure modes).
Grants & denials (CLASSIFY-BLOCK)
| class | step it powers | grant | on denial |
|---|---|---|---|
| read | trace failure paths for the 8 categories above | Read·Grep·Glob | refuse that file, name it — never a clean bill |
| write | Fix mode's safe-guard apply, incl. checkpoint → build+tests → revert if newly red | Edit·Bash (checkpoint/build/revert need exec) | report the fix as NOT applied AND the checkpoint/revert as NOT available, never claim done |
Output
| operation | failure mode | effect | handling (file:line) | severity | recommended guard |
Ordering/atomicity findings · Summary (counts + top fixes) · Not assessed
Severity: CRITICAL (data loss/corruption/silent-success) · HIGH (crash/hang/partial-no-recovery) · MEDIUM (poor degradation/missing retry) · LOW (cosmetic)
<!-- SHARED:REPORTING_FOOTER --> <!-- SHARED:ORCHESTRATION --> <!-- SHARED:ESCALATION_FOOTER -->What ships with it: 2 files
2.8 KB alongside SKILL.md
references/
- checks.md2.6 KB
- skill-meta.json181 B
Gives 0 of the 12 instructions most audit compliance skills give
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- Ask what happens when this fails
- Check detection handling recovery and communication
- Read checks reference before scanning
- Present fix mode choices via ask_question
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.