tidy-docs
Skill0 starsChanged 6 days agoMITView on GitHub
Review and tidy documentation, including skills and AGENTS.md files, across a repository or selected scope. Use when asked to tidy, clean up, or check documentation for consistency, outdated content, or wording.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- trsrm/skillstheir own version, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- trsrm/skills★ 2same 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- clarifySkill
- collectSkill
- handoffSkill
- interrogateSkill
- pendingSkill
- progressSkill
- recapSkill
- restateSkill
- spawnSkill
- warmupSkill
- yieldSkill
- glossarySkill
- writing-agentsSkill
- writing-skillsSkill
- writing-textSkill
- teachSkill
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 9
Use the supplied scope, or the entire repository if none is provided.
- Distinctive: line 13
Read outside the edit scope as needed to understand the repository, unless the user excludes those files from reading too.
- Distinctive: line 21
Update evolving documents, such as specs, tasks, and improvement notes, to reflect the repository's current state.
≈ “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
Scope
Use the supplied scope, or the entire repository if none is provided.
Scope limits which documentation files may be modified. Include hidden directories unless excluded by the scope. Skip generated files, dependencies, and version-control internals.
Read outside the edit scope as needed to understand the repository, unless the user excludes those files from reading too.
Process
Apply the writing-text skill and other relevant writing skills to each document. Before finishing, check each edited document against them, including prose punctuation. Reading the guidance alone does not complete the review.
Resolve inconsistencies and outdated links. Preserve behavior, requirements, and invocation settings.
Update evolving documents, such as specs, tasks, and improvement notes, to reflect the repository's current state. Distinguish intended behavior from implemented behavior. Preserve unresolved requirements and decisions.
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.