debugging-playbook
Skill1 starsChanged 4 months agoNo licenceView on GitHub
Symptom-to-fix triage playbook for this repo's known failure modes — load it the moment something is BROKEN and you need to know why. Use when the claude-council skill won't trigger in Claude Code or on claude.ai, triggers too eagerly, leaks its internal deliberation phases into visible output, produces a verdict over ~200 words or refuses to commit, shows an inflated/fake-looking vote tally, when an edit to SKILL.md doesn't show up in a session ("stale skill"), or when files.zip artifacts disagree with the working tree. Do NOT use for what-am-I-allowed-to-change questions (change-control), for the historical incident record (failure-archaeology), for shipping artifacts (release-and-packaging), for running behavioral evals (validation-and-evals), or for routinely CHECKING whether the zip matches the tree — that parity check is diagnostics-and-tooling's; come here only when a mismatch is already suspected of causing breakage.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- andymai/gridfinity-layout-tooltheir own version, first seen Oct 8, 2026
- MichaelRDionne/clinical-agent-skillstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- andymai/gridfinity-layout-tool★ 525same name
- MichaelRDionne/clinical-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- architecture-contractSkill
- build-and-envSkill
- change-controlSkill
- claude-councilSkill
- diagnostics-and-toolingSkill
- docs-and-writingSkill
- domain-referenceSkill
- eval-harness-campaignSkill
- failure-archaeologySkill
- logic-treeSkill
- release-and-packagingSkill
- research-methodologySkill
- skill-authoringSkill
- validation-and-evalsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.