clarity
Skill7 starsChanged 34 days agoMITView on GitHub
Reviews and repairs text that is hard to follow: unclear wording, buried answers, dense paragraphs, and structure that is hard to scan, including for readers with ADHD or dyslexia. Use whenever someone asks to make a passage clearer, easier to scan, or answer-first without changing its claims or voice.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- flowcopilot/skillstheir own version, first seen Nov 15, 2026
- raditia/CraftKittheir own version, first seen Nov 8, 2026
- JBSommeling/claude-configtheir own version, first seen Nov 1, 2026
- jackson2w/claude-code-skillstheir own version, first seen Nov 1, 2026
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
- getedgehq/skillstheir own version, first seen Nov 1, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- addyosmani/clarity★ 219same name
- getedgehq/skills★ 5same name
- rogue-dev-studio/ai-agents-rogue★ 2same name
- X-FRI/skills★ 2same name
- cemkazim/claude-skill-clarity★ 1same name
- Claude-Mem/clarity★ 1same name
- flowcopilot/skills★ 1same name
- jackson2w/claude-code-skills★ 1same name
- raditia/CraftKit★ 1same name
- bob-bach/clarity★ 0same name
2 more not listed
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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- claim-fidelitySkill
- copywritingSkill
- glossarySkill
- im-not-a-humanSkill
- im-part-humanSkill
- pull-request-summarySkill
- readmeSkill
- release-notesSkill
- slop-naming-recoverySkill
- technical-guideSkill
- verify-examplesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 25 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
25
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 11
Follow the target's instructions, terminology, canonical wording, and requested output format.
- Distinctive: line 16
Read the complete passage and any supplied reader preferences.
- Distinctive: line 18
Consider their starting knowledge and the explanation they need to understand or act.
- Distinctive: line 20
If a missing choice changes the result materially, ask before dependent edits.
- Distinctive: line 27
Do not infer a diagnosis or claim that most readers have one.
- Distinctive: line 32
Use the reader, purpose, destination, and supplied preferences to make that prediction.
- Distinctive: line 33
Treat it as an editorial assumption, not a measured reading time.
- Distinctive: line 36
Keep less important material brief, linked, or optional.
- Distinctive: line 43
Put optional exceptions and background later.
- Distinctive: line 45
Prefer familiar words, explicit actors, and direct instructions.
- Distinctive: line 49
Make sections findable: Use descriptive headings for distinct questions, tasks, or reference entries.
- Distinctive: line 50
Keep a logical heading hierarchy.
- Distinctive: line 52
Choose the useful format: Use bullets for parallel points, numbers for ordered steps, and tables for comparisons.
- Distinctive: line 53
Use diagrams for relationships or branching processes.
- Distinctive: line 54
Add an artifact only when it reduces reading effort.
- Distinctive: line 57
Use whitespace and restrained emphasis.
- Distinctive: line 59
Leave clear sentences and useful headings unchanged.
- Distinctive: line 61
Keep exact code, commands, names, numbers, units, attribution, uncertainty, and required wording.
- Distinctive: line 62
Keep conditions, negation, exceptions, permissions, and step order attached to their actions.
- Distinctive: line 63
Never invent an actor, explanation, experience, or example to make a passage sound clearer.
- Distinctive: line 64
Do not use em dashes or hyphens as sentence punctuation in new prose.
- Distinctive: line 70
Before delivery, check that the reader can find the answer, understand the terms, and follow the required steps.
- Distinctive: line 71
Check whether the whole output fits the predicted attention and gives the important points enough depth.
- Distinctive: line 73
If rendering is available, inspect the actual output at a narrow width.
- Distinctive: line 74
If no repair is needed, say so.
“Common” is measured: kept by at least 6 in 10 of the 12 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
Clarity
Help the intended reader find the point and understand the next action. This pass reviews wording and structure. It does not run a full style rewrite or verify factual truth. Follow the target's instructions, terminology, canonical wording, and requested output format. Installing this Skill does not authorize publication or unrelated edits.
Establish the reading task
Read the complete passage and any supplied reader preferences. Identify the reader, purpose, and requested scope. Infer them when the context is clear. Consider their starting knowledge and the explanation they need to understand or act. Show respect and empathy through clear connections, accurate meaning, and no unnecessary reading effort. If a missing choice changes the result materially, ask before dependent edits. For mixed documents, distinguish stories, instructions, explanations, and reference sections. Preserve deliberate narrative openings. Keep technical instructions predictable.
Review wording and structure
Design for readers with varied attention, working memory, and reading needs, including ADHD and dyslexia. Do not infer a diagnosis or claim that most readers have one. Respect stated reader preferences. Reader comprehension takes priority over stylistic variety. Brevity removes unnecessary words. Keep the explanations, conditions, and connections this reader needs.
Reader attention is finite. Before writing or editing, predict how much attention this piece will receive. Use the reader, purpose, destination, and supplied preferences to make that prediction. Treat it as an editorial assumption, not a measured reading time. Let it govern scope, order, and depth across the complete output. Spend the most attention on what affects the reader's decision, understanding, or next action. Keep less important material brief, linked, or optional. Do not give every point equal space. Preserve critical conditions and warnings on the main reading path. Short sentences alone do not make an output worth the attention it requires.
- Start simple. Lead with the answer or action. Then give the common case, an example, and deeper detail. For a story, preserve a deliberate narrative opening. Apply answer-first ordering to its technical sections. Define necessary terms before using them. Keep prerequisites and consequential warnings beside the action. Put optional exceptions and background later. A deep dive still needs a clear entry point.
- Keep blocks small. Give each sentence one main idea and each paragraph one job. Prefer familiar words, explicit actors, and direct instructions. Explain necessary jargon on first use. As editing defaults, aim for sentences under 20 words and paragraphs of one to three sentences. Review three consecutive prose paragraphs for a useful heading, list, example, table, or diagram. These numbers are review prompts, not research thresholds. Preserve meaning and deliberate literary voice.
- Make sections findable. Use descriptive headings for distinct questions, tasks, or reference entries. Keep a logical heading hierarchy. Avoid vague labels, decorative headings, and filler between sections. Readers should find the answer by scanning headings and opening lines.
- Choose the useful format. Use bullets for parallel points, numbers for ordered steps, and tables for comparisons. Use diagrams for relationships or branching processes. Keep connected explanations in short prose. Add an artifact only when it reduces reading effort. Avoid long lists, wide tables, and decorative visuals.
- Keep alternatives accessible. Explain a visual's useful point in nearby text. Supply meaningful text alternatives for images. Label table columns and keep cells short. Never make color, position, or an icon the only carrier of meaning. Use whitespace and restrained emphasis. Avoid full paragraphs in bold, italics, or capitals.
Leave clear sentences and useful headings unchanged. Do not split sentences mechanically or add filler for rhythm. Preserve stable anchors and check affected links when changing headings. Keep exact code, commands, names, numbers, units, attribution, uncertainty, and required wording. Keep conditions, negation, exceptions, permissions, and step order attached to their actions. Never invent an actor, explanation, experience, or example to make a passage sound clearer. Do not use em dashes or hyphens as sentence punctuation in new prose.
Deliver the requested pass
For review only, return concrete reading problems and proposed repairs. Leave the source unchanged. For an edit, change only passages with a reading problem. Explain meaningful repairs outside the edited text. Before delivery, check that the reader can find the answer, understand the terms, and follow the required steps. Check whether the whole output fits the predicted attention and gives the important points enough depth. Compare the result with the source for changed claims, conditions, uncertainty, and voice. If rendering is available, inspect the actual output at a narrow width. Otherwise report that limit when relevant. If no repair is needed, say so. Do not invent findings or claim an accessibility audit passed.
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.

