attic-prune
Skill5 starsChanged 2 months agoMITView on GitHub
Find stale attic items and archive them. Use when the user says "prune the attic", "the attic is getting big", "clean up old items", or "archive old findings". This is about the ATTIC's own contents, never about cleaning up source code.
In this repository12 other files it gives its agents.
- attic-doctorSkill
- attic-failSkill
- attic-gitSkill
- attic-helpSkill
- attic-indexSkill
- attic-pinSkill
- attic-recallSkill
- attic-reviewSkill
- atticSkill
- attic-stashSkill
- attic-statsSkill
- attic-sweepSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run it without --apply first, always.
- Very specific: line 28
Ask for confirmation before --apply.
- Very specific: line 37
Never delete an item file.
≈ “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
Prune the attic
node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" prune $ARGUMENTSDry run is the default. The command lists candidates and moves nothing
until --apply is passed.
- Run it without
--applyfirst, always. Show the candidate list. - Archiving is not deletion: items move to
.attic/archive/, stay recallable by/attic-recall, and simply stop being injected. Say this, because "prune" sounds destructive and users hesitate. - Ask for confirmation before
--apply. Never apply in the same turn the user first mentions pruning, unless they explicitly said to go ahead. - Pinned items are skipped automatically. Report how many were skipped.
- Restore anything with
node .../attic.js archive <slug> --restore.
Defaults to items older than 90 days. --kind output is the safest filter,
since stale command output ages worst.
Never delete an item file. Never pass --apply without the user having seen
the candidate list.
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.

