attic-doctor
Skill5 starsChanged 2 months agoMITView on GitHub
Check the CONTENTS of .attic/ for drift: orphaned items, stale index lines, malformed frontmatter, oversized hooks, and leaked credentials. Use when the user says "check the attic", "attic doctor", "is the attic healthy", or "did anything leak into the attic". Never use this for git, merge or conflict problems, even though they sound like breakage: every merge conflict goes to attic-git.
In this repository12 other files it gives its agents.
- attic-failSkill
- attic-gitSkill
- attic-helpSkill
- attic-indexSkill
- attic-pinSkill
- attic-pruneSkill
- attic-recallSkill
- attic-reviewSkill
- atticSkill
- attic-stashSkill
- attic-statsSkill
- attic-sweepSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
If the index is badly out of step with the items (many orphans, or it has been hand-edited into garbage), rebuild it rather than fixing …
- Distinctive: line 43
Do not bulk-delete items to make the check pass.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Attic doctor
node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" validateExit 0 is healthy. Exit 3 means errors were found.
Report what it printed, then act:
| Problem | Fix |
| INDEX line points at a missing item file | Remove the line, or restore the item if it was deleted by mistake. |
| Item file not listed in INDEX.md | Run attic.js rebuild to regenerate the index from the item files. |
| Missing or malformed frontmatter | Repair the file to match references/item-format.md. |
| Hook over 100 chars | Shorten it; the index is injected into every session. |
| Possible credential | Stop. Tell the user which file and line, recommend rotating the credential, and remove the value from the item. If .attic/ is committed, it is in git history too. |
If the index is badly out of step with the items (many orphans, or it has been hand-edited into garbage), rebuild it rather than fixing lines one by one. Items are the source of truth; the index is derived:
node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" rebuild --dry-run
node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" rebuildDo not bulk-delete items to make the check pass. Ask before removing anything the user did not create in this session.
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.

