doc-polish
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Restructure a design doc, investigation write-up or analysis so its main point is not buried, and hold its wording to the code-polish skill's language rules. Moves code samples, internal file paths and chains of function names out of the main text into a numbered Notes section, keeps the experiment code that shows how a result was measured, labels each claim as measured, read in the source or estimated, re-reads the code behind every claim the doc makes about code and corrects the doc where they disagree, and fixes the layout problems that break rendering (footnote syntax, a table with no blank line after it, letters reused for two things). Use when a doc reads as a wall of code and internal names, after a doc has grown through many rounds of edits, or when the user says a doc "detracts from the point", is "too much", or asks to clean up, restructure or polish a doc.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- branchSkill
- bugfixSkill
- check-screenshotSkill
- code-polishSkill
- commitSkill
- featureSkill
- loadSkill
- prSkill
- saveSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.