sweeper
Skill1 starsChanged 3 months agoMITView on GitHub
Remove stale content, broken references, unused assets, unsafe configuration, and accumulated repository debt while preserving provenance, retention obligations, and rollback ability. Use for cleanup audits, archive plans, deprecation, and post-migration hygiene.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/PilotSwarmtheir own version, first seen Mar 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- microsoft/PilotSwarm★ 14same 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 repository5 other files it gives its agents.
- builderSkill
- growerSkill
- maintainerSkill
- prototypeSkill
- ux-ui-cx-market-intelligenceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to make a project easier to trust and maintain.
- Distinctive: line 20
Verify affected routes, links, structured data, dependencies, repository health, and rollback ability after completion.
- Distinctive: line 28
Do not delete unverified material, erase audit history, retire a property without its steward, remove a domain merely to simplify a …
≈ “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
Sweeper
Use this skill to make a project easier to trust and maintain. Cleanup is a governed operation: inventory first, dry run second, named approval before destructive change, and preserved evidence throughout.
Intake
Record the property, cleanup objective, inventory scope, owner, retention obligations, dependency map, affected users or contributors, rollback window, and approval level.
Workflow
- Inventory candidates and classify each as retain, correct, archive, deprecate, or remove.
- Identify inbound links, references, security implications, legal or retention obligations, and affected contributors before changing anything.
- Produce a dry-run report containing proposed action, reason, risk, fallback, archive location, and reviewer.
- Obtain named approval for deletion, domain change, archival, credential rotation, or other irreversible action.
- Verify affected routes, links, structured data, dependencies, repository health, and rollback ability after completion. Preserve redirects or archive records where appropriate.
Deliverable
Provide the inventory, dry-run plan, approval record, change log, verification report, and archive or rollback location. State what remains, who owns residual work, and the next review date.
Boundaries
Do not delete unverified material, erase audit history, retire a property without its steward, remove a domain merely to simplify a portfolio, disclose private data in a cleanup report, or treat silence as approval.
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.