writing-review
Skill0 starsChanged 3 months agoMITView on GitHub
Quality pass for prose deliverables — reports, docs, READMEs, emails, summaries, plans. Use before shipping ANY document a human will read, after generating a first draft, or when the user asks to polish/tighten/review writing. First drafts are never final drafts.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- slogsdon/skills-writingtheir own version, first seen Nov 12, 2026
- gwpicard/ai-loop-kittheir own version, first seen Nov 1, 2026
- michaelwjohnson/claude-skillstheir own version, first seen Nov 1, 2026
- ragnos-labs/skill-indextheir own version, first seen Aug 23, 2026
- markrstevenson/skillstheir own version, first seen Aug 10, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- gwpicard/ai-loop-kit★ 0same name
- markrstevenson/skills★ 0same name
- michaelwjohnson/claude-skills★ 0same name
- ragnos-labs/skill-index★ 0same name
- slogsdon/skills-writing★ 0same 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- cleanupSkill
- context-managementSkill
- critiqueSkill
- debuggingSkill
- design-decisionsSkill
- diff-managementSkill
- fan-outSkill
- final-checkSkill
- handoverSkill
- loopsSkill
- memorySkill
- orientSkill
- planningSkill
- researchSkill
- roadmapSkill
- verificationSkill
- web-testingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
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
Who reads this, and what do they DO after reading?: If the document doesn't serve that action, no amount of polish saves it.
- Distinctive: line 19
Every claim: supported (source, number, example) or cut.
- Distinctive: line 20
Every number: recomputed or traced to source (verification skill).
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Writing review
A document succeeds when the intended reader gets what they need in one pass. Review for the reader, not for the author.
Pass 1 — Reader fit (the pass that matters most)
- Who reads this, and what do they DO after reading? If the document doesn't serve that action, no amount of polish saves it.
- Lead with the payload. Conclusion, recommendation, or answer first; background after. Readers who want the reasoning will keep reading; readers who don't shouldn't have to.
- One document, one job. Mixed audiences (exec summary + implementation detail) get explicit sections, not interleaving.
- Does the title/first line let someone decide whether to read it at all?
Pass 2 — Substance
- Every claim: supported (source, number, example) or cut. "Significantly improves" with no number is decoration.
- Every number: recomputed or traced to source (verification skill).
- Hedge audit: keep hedges that convey real uncertainty ("unverified", "as of June"); cut hedges that convey cowardice ("somewhat", "arguably", "it could be said").
- What would a hostile reader attack first? Fix or preempt it.
Pass 3 — Line editing
- Cut ruthlessly: if a sentence survives with a word removed, remove the word. Target: -20% length with zero meaning lost. Read it aloud mentally; stumbles mark rewrites.
- Kill throat-clearing openers ("It is important to note that...", "In today's world..."), empty intensifiers ("very", "extremely", "incredibly"), and unnecessary meta-commentary about the document itself.
- Concrete beats abstract: "cuts build time from 4 min to 40 s" > "dramatically improves performance".
- Parallel structure in lists; consistent terminology (one name per concept — synonyms are for novels).
- Formatting serves scanning: headers that summarize (not "Overview"), lists only where order/enumeration matters, bold only for genuine keystones.
Mechanics gate (always, last)
Names spelled right (people, products, files), dates correct against today's date, links resolve, code blocks run, numbers consistent between summary and body, no leftover placeholders (TODO, TKTK, <name>, lorem).
Verdict
Like the critique skill: findings with severity, then loop. A review that only fixes commas has failed — Pass 1 findings are the reason this skill exists.
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.

