cdeust/zetetic-team-subagents/failure-forensics
Claude Code and agent skill by cdeust/zetetic-team-subagents
- community
Checking that the SKILL.md file is still in the repository.
Read the wreckage before rebuilding. Use for incident post-mortems, "what happens when everything goes wrong at once?", flaky or anomalous cases being filtered out as noise, "that's weird" moments nobody wrote down, oscillating or unstable feedback behavior, and designs whose only failure mode is crash.
Install
npx vskill@latest install cdeust/zetetic-team-subagents/failure-forensicsSKILL.md
Failure Forensics
Problem shape: something failed (or will fail) and the evidence is being averaged away, cleaned up, or explained by its most convenient story. The move: treat anomalies as data, reconstruct the timeline at the right timescale, and design the degraded state as a first-class behavior.
Relevant geniuses
| Agent | Use when | |
|---|---|---|
| hamilton | overload and simultaneous failure scenarios; priority shedding by criticality; the degraded mode is undesigned; "users will never do that" | |
| mcclintock | aggregate metrics look smooth but one specific case is weird; a class of observations is being trimmed as noise | |
| fleming | anomalies keep appearing during routine work and being cleaned up; "that's weird" said and never investigated | |
| ginzburg | reconstruct what happened from marginal traces and involuntary evidence (logs, timestamps, artifacts nobody meant to leave) | |
| braudel | the incident needs three-timescale decomposition — event, cycle, structure — before a root cause is named | |
| wu | the failure hides under an assumption everyone considered too obvious to test | |
| maxwell | the system oscillates, overshoots, or hunts — feedback stability and gain-margin diagnosis |
Invocation
- Pick the best-fit agent above. If two or more fit, run
tools/genius-invoker.sh route "<problem>" and take the top ranked match.
- Load it:
tools/genius-invoker.sh invoke <agent> "<problem>", then read
agents/genius/<agent>.md in full.
- Apply the agent's
<workflow>step by step and answer in its
<output-format>. Reproduce before claiming a cause; classify the cause before proposing the fix (coding-standards §6 root-cause protocol).
- Typical chain: ginzburg reconstructs the timeline → braudel separates
timescales → hamilton designs the degraded state. Run via tools/genius-invoker.sh compose ginzburg hamilton -- "<problem>".
- If no shape above matches, use a built-in agent with the closest
GENIUS:pattern fromrules/agent-routes.jsoninstead.
Refuse when
- No reproduction and no trace evidence exist — forensics reads records, it
does not invent narratives.
- The requested output is a fix at the throw site with no cause classification.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/failure-forensics/SKILL.md
Popularity
- Repository stars
- 8
- Repository forks
- 3
- 7-day trend score
- 10
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/cdeust/zetetic-team-subagents/failure-forensics)