failure-archaeology
Skill31 starsChanged 29 days agoLicence not identifiedView on GitHub
Never re-fight a settled battle. Discipline for recording and RETRIEVING past failures — gotchas, incidents, postmortems, dead ends, reverted fixes — as symptom → root cause → evidence → status. Use before debugging anything that smells familiar, when an incident closes, when a fix gets reverted, when an approach is abandoned, or when asked to document a bug just solved, write a postmortem, do failure archaeology, incident memory, or "did we hit this before". Not for capturing general knowledge (use brain_capture / brain_write) or live task tracking.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- nic095layson/claudetheir own version, first seen Jul 10, 2026
- LJMStark/geo-doctortheir own version, first seen Jul 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- nic095layson/claude★ 1same name
- LJMStark/geo-doctor★ 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 repository30 other files it gives its agents.
- adversarial-deliberationSkill
- agent-paymentsSkill
- autoresearchSkill
- brain-due-diligenceSkill
- check-brain-healthSkill
- create-task-cardSkill
- cross-model-handoffSkill
- cs-fashion-triageSkill
- cs-triage-finalizationSkill
- employee-onboardingSkill
- handoff-taskSkill
- klaviyo-fashionSkill
- log-capability-gapSkill
- omnichannel-foot-traffic-attributionSkill
- omnichannel-growth-loopSkill
- pinterest-ads-integrationSkill
- refresh-world-modelSkill
- research-promptingSkill
- restock-triggerSkill
- review-outputSkill
- sell-through-dashboard-syncSkill
- session-handoffSkill
- shopify-inventory-syncSkill
- skill-authoring-standardsSkill
- skill-evaluationSkill
- spec-driven-executionSkill
- suggest-skillsSkill
- swarm-propagationSkill
- visual-reviewSkill
- weekly-top5-digitalSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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.