writing-quality
Skill5 starsChanged 22 days agoMITView on GitHub
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
9 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- shawnclybor/clybor-claude-toolingtheir own version, first seen Nov 8, 2026
- getsentry/software-factoryedited, first seen Oct 25, 2026
- attilaszasz/sdd-pilottheir own version, first seen Oct 20, 2026
- vercel-labs/typefully-eve-templateedited, first seen Oct 13, 2026
- vercel-labs/kody-eve-templateedited, first seen Oct 13, 2026
- vercel-labs/eve-software-factory-templateedited, first seen Oct 13, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- vercel-labs/eve-software-factory-template★ 1.2k87% same
- vercel-labs/kody-eve-template★ 1387% same
- vercel-labs/typefully-eve-template★ 862% same
- getsentry/software-factory★ 087% same
Wrote their own version · 5
- attilaszasz/sdd-pilot★ 98same name
- shawnclybor/clybor-claude-tooling★ 6same name
- guerrilla2799/event-and-scale-os★ 2same name
- guerrilla2799/ops-and-scale-os★ 1same name
- ItalyPaleAle/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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- content-experimentation-best-practicesSkill
- content-modeling-best-practicesSkill
- portable-text-conversionSkill
- portable-text-serializationSkill
- sanity-best-practicesSkill
- seo-aeo-best-practicesSkill
- writing-qualitySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative.
“Common” is measured: kept by at least 6 in 10 of the 9 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 Quality
House-neutral rules for making drafted content read like a person wrote it. They apply to any prose surface. Layer project- or brand-specific voice guidance on top of them.
When to Apply
Load this skill before:
- Drafting new content (a blog post, landing-page copy, a Notion draft, release notes)
- Editing or rewriting existing content
- Reviewing a draft before proposing it to the user
Core Rules
- Kill the AI tells: em-dash overuse, "delve", "leverage", "it's not just X, it's Y", rule-of-three padding, and the rest of the patterns in
references/ai-phrases-to-avoid.md. - Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative.
references/plain-english-alternatives.mdis the lookup table. - Front-load the point. Lead sentences, paragraphs, and sections with the conclusion, because readers scan.
- Concrete over abstract. Show an example before stating a principle, and cut hedges like "just", "simply", "very", and "really".
- Match the user's voice, not a default. When editing existing content, keep its register and conventions. These rules trim the noise; they don't impose a personality.
References
Load the reference that matches the task rather than all of them at once:
references/ai-phrases-to-avoid.md: words, phrases, and punctuation patterns that mark text as AI-generated, with replacements. Load when drafting or editing any prose.references/plain-english-alternatives.md: plain-English swaps for corporate, padded, or vague wording. Load when drafting or editing any prose.references/web-writing-best-practices.md: a sourced checklist for long-form web content, covering scanning behavior, hooks, structure, readability, length by intent, SEO basics, and closes. Load when writing or restructuring articles, blog posts, or guides.references/web-content-specs.md: the concrete numbers behind that checklist (slug rules, heading cadence, readability thresholds, word count by intent, alt text, internal links). Load for a final spec check on a piece. Title, meta, and Open Graph specs live in theseo-aeo-best-practicesskill.
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.