troubleshooting
Skill8 starsChanged 43 days agoNo licenceView on GitHub
Produce a troubleshooting guide in docs/troubleshooting/, one file per architectural seam, organized by symptom. Before real incidents exist, it maps the system's seams with the user (database, cache, proxy, external APIs, auth, build and deploy) and seeds the likely failures at each seam. The guide grows as real incidents land. It links to docs/deployment-plan/ instead of repeating it. Use when the user wants a troubleshooting guide, a runbook of common problems, an ops FAQ, or asks to "write a TROUBLESHOOTING".
- Reads credentials
26 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- onelastcommit/noctratheir own version, first seen Nov 8, 2026
- zakirkun/slayerclawtheir own version, first seen Nov 8, 2026
- snowfluke/tech-lead-skillsword for word, first seen Nov 8, 2026
- jkitchin/knowhowtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use architecture.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 1
- snowfluke/tech-lead-skills★ 8100% same
Edited · 0
None found.
Wrote their own version · 25
- ChromeDevTools/chrome-devtools-mcp★ 55ksame name
- cartography-cncf/cartography★ 4.2ksame name
- jasonkneen/kiro★ 753same name
- nanvix/nanvix★ 318same name
- duyet/clickhouse-monitoring★ 303same name
- davidYichengWei/agentic-engineering-framework★ 158same name
- projectbluefin/finpilot★ 131same name
- mycelium-io/mycelium★ 127same name
- NVIDIA/elements★ 115same name
- emanueleielo/ciana-parrot★ 77same name
15 more not listed
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 repository19 other files it gives its agents.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- lead-reviewSkill
- product-discoverySkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- tech-lead-setupsSkill
- technical-specSkill
- test-auditSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- us-ac-formatterSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
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 measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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.