project-cleanup
Skill0 starsChanged 5 months agoMITView on GitHub
For the Technical Writer (10). Inventory and delete (only with an orchestrator-approved list) obsolete root files; no archiving, no quarantine, no 'just in case'. Use it for active root cleanup.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- windgeek/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- windgeek/skills★ 1same 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 repository20 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- adopt-groundSkill
- agent-authoringSkill
- architecture-decisionSkill
- asset-sourcingSkill
- brand-evaluation-rubricSkill
- criticSkill
- data-integritySkill
- diagrams-gateSkill
- drift-protocolSkill
- env-reproducibleSkill
- orchestrator-bridgeSkill
- qa-eyesSkill
- qa-visual-criteriaSkill
- research-methodologySkill
- security-auditSkill
- setupSkill
- smoke-testSkill
- technical-documentationSkill
- visualizerSkill
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 12
If NOT → a deletion candidate.
- Distinctive: line 14
If it's in Git, it's in the history.
≈ “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.
Files
SKILL: project-cleanup
For: Agent 10 — TECHNICAL WRITER
Version: 1.0.0
Core principle
Deletion criterion: "Does this file serve anyone working on the project today?" If NOT → a deletion candidate. No quarantine. No archiving. No "just in case". With orchestrator approval → delete for good. If it's in Git, it's in the history. It doesn't need to exist live.
Process
STEP 1 — Inventory: list all non-code files with name, date, size, description. STEP 2 — Classify: ACTIVE (don't touch) / OBSOLETE (candidate) / HISTORICAL (evaluate) / DUPLICATE (delete the old one). STEP 3 — Candidate list: name, why it's a candidate, what replaces it, risk (low/medium/high). STEP 4 — Present CLEANUP_LIST.md to the orchestrator. Delete nothing without approval. STEP 5 — With approval → delete and report.
OBSOLETE — delete with approval
Prompts from earlier versions, specs of already-built features, resolved QA reports, unused experimentation files, intermediate documents with an approved final version.
HISTORICAL — evaluate before deciding
Architecture decisions (keep if they explain what was discarded), very old changelogs (if the info is already in Git → delete), specs of cancelled features (delete — if resumed, they're redesigned).
NEVER DELETE without consensus
× Active AGENTS.md, README.md, CLAUDE.md × Runbooks for processes in use × Contracts of active APIs × Files the code references directly × .env.example and environment configs
Signs of a contaminated root
More than 5 .md in the root beyond the standard ones, files named "prompt_X/fix_v1/issues_vX/spec_draft", multiple versions of the same doc, files untouched for over 3 months, more docs than code.
CLEANUP_LIST.md structure
Summary (inventoried/candidates/kept) → Candidate table (file/category/reason/risk/replaced by) → Kept files with description → Pending decision
Mistakes to avoid
× Deleting without an approved list × Archiving in old/ or backup/ instead of deleting × Deleting files the code references × "Just in case" as a keep criterion
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.