flesch-kincaid-proofreader
Skill8 starsChanged 2 months agoMITView on GitHub
Measure and improve the readability of English copy with the Flesch–Kincaid grade-level test. Use when proofreading or simplifying READMEs, documentation, product copy, help text, announcements, or other prose, especially when a target reading grade is requested.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the bundled script for measurement and sentence triage.
- Distinctive: line 14
Run the analyzer before editing:
- Distinctive: line 30
Do not estimate the grade yourself, count words or syllables manually, or ask the model to rank every sentence.
- Distinctive: line 52
Use as a check that exits with status 1 when any document is above target (or has no prose):
- Very specific: line 58
Run node scripts/readability.mjs --help for all options.
- Distinctive: line 74
After changing the analyzer, run:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Flesch–Kincaid Proofreader
Use the bundled script for measurement and sentence triage. Use the language model only for the semantic work a deterministic tool cannot do: preserving meaning, voice, and technical accuracy while rewriting.
Workflow
- Choose the target grade. Use the user's target when given; otherwise grade 8.
Run the analyzer before editing:
node scripts/readability.mjs --target 8 path/to/README.md- Review difficult sentences in descending grade order. Start with sentences that are both long and far above target. Listed complex words are candidates, not automatic errors.
- Rewrite only where useful. Prefer:
- one main idea per sentence;
- familiar, precise words over longer synonyms;
- active, concrete constructions;
- bullets for genuine lists;
- keeping required technical terms and explaining them once.
- Re-run the same command. Continue until the copy meets the target or further simplification would harm accuracy, voice, or usefulness.
- Report the before/after grade and any intentional exceptions. Never claim a passing score proves the copy is clear or correct.
Do not estimate the grade yourself, count words or syllables manually, or ask the model to rank every sentence. The script owns those deterministic steps.
Commands
Analyze one or more files:
node scripts/readability.mjs --target 8 README.md docs/getting-started.mdAnalyze selected text through stdin:
printf '%s\n' 'Paste the copy here.' | node scripts/readability.mjs --target 8Produce structured output for another tool:
node scripts/readability.mjs --json --target 8 README.mdUse as a check that exits with status 1 when any document is above target (or has no prose):
node scripts/readability.mjs --target 8 --fail-above README.mdRun node scripts/readability.mjs --help for all options. Markdown code blocks, link destinations, HTML tags, comments, headings, tables, and frontmatter are excluded by default. Inline code remains because it is often part of a technical sentence. Pass --include-code only when fenced code blocks should count as prose.
Interpretation
The script implements:
0.39 × (words / sentences) + 11.8 × (syllables / words) − 15.59A result of 8.0 roughly indicates text suited to a US eighth-grade reader. Negative values are valid for very simple text. The test measures sentence length and estimated word length; it does not measure correctness, structure, jargon familiarity, accessibility, tone, or reader knowledge.
Syllable counting is a deterministic English heuristic, so names, acronyms, code identifiers, and specialist terms may be miscounted. Treat small score differences as noise. Keep accurate terms rather than gaming the score, and use judgment for text that is not English.
Validation
After changing the analyzer, run:
node --test tests/*.test.mjsIn this repository20 other files it gives its agents.
- autonomous-maintainerSkill
- commitSkill
- competitive-ads-extractorSkill
- compress-skillsSkill
- extract-design-systemSkill
- fix-ciSkill
- frontendSkill
- get-pr-commentsSkill
- gogSkill
- grillingSkill
- grill-meSkill
- hairline-createSkill
- image-generationSkill
- posthogSkill
- shipSkill
- signoz-investigating-alertsSkill
- teachSkill
- thermo-nuclear-code-quality-reviewSkill
- update-agents-mdSkill
- visualizeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

