readability-check

Name: readability-check
Author: jdevalk

85stars9forks

How to install readability-check?

jdevalk/skills/readability-check

$npx -y skills add jdevalk/skills --skill readability-check

Installs into the current project.

Summary

Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language. Checks ten categories — overall structure and topic order, paragraph structure, opening paragraph strength, tiered sentence length, passive

Files · 1

View on GitHub

SKILL.md

1	# Readability check
2
3	Run a readability audit on a blog post draft or other multi-paragraph prose. Use when the user asks to check readability ("check readability", "readability pass", "is this readable"), or proactively after a substantial draft is complete — as a second pass after the blog-drafting skill's critical read, not during active drafting.
4
5	For short strings — page titles, meta descriptions, schema `description` fields, FAQ answers, profile bios, repo taglines — use the `metadata-check` skill. Flesch scoring and the ten-category rubric below don't fit a 5–30 word string and will mislead.
6
7	For whether a post earns a ranking — search intent fit, keyphrase placement, E-E-A-T, internal linking — chain into the `content-seo` skill after this audit. Readability is a prerequisite for ranking, not a substitute.
8
9	## Audience calibration
10
11	Always assume the reader reads English as a second language. That's the default, not a fallback.
12
13	In technical posts, the technical sections can use domain terms the audience expects — but any non-technical paragraph (introduction, context, conclusion, transitions, examples, analogies) must be readable by a non-technical L2 reader. Setup and motivation paragraphs carry the post for readers who don't know the domain yet; they're where you lose people.
14
15	Conversational beats formal. Posts that address the reader directly ("you", "your") and occasionally ask them a question hold L2 readers far better than impersonal prose. Flag long stretches of detached, third-person register in non-technical sections.
16
17	## How readers actually read
18
19	Readers scan before they commit. They look at the headings, the first paragraph, and the first sentence of each paragraph, and decide from those alone whether to read on. Search engines and AI systems weight the same elements when working out what a text is about. That's why the audit leans hard on those three places: a post whose headings and first sentences carry the argument works for scanners, full readers, and machines at once.
20
21	## What to check
22
23	Read the full post, then report on each criterion below. For every issue, quote the specific text, reference its location (section heading or "intro" / "conclusion"), explain the problem, and suggest a concrete fix.
24
25	### 1. Overall structure and topic order
26
27	The post should read as if it was planned before it was written — topics grouped, ordered, and finished one at a time.
28
29	- The post should follow one recognizable ordering principle: thematic (aspect by aspect), chronological (old to new), didactic (easy to hard — best for explaining complicated subjects), problem–solution (state the problem, then the options), or inverted pyramid (most important first, details and background after — best for news and announcements).
30	- Related topics must sit together. Flag topic ping-pong: a subject discussed, dropped, and picked up again two sections later.
31	- The skim test: reading only the headings and the first sentence of each paragraph should yield the post's full argument. If a skimmer would miss a key point, it's buried mid-paragraph — surface it.
32	- The conclusion should restate the core message, using concluding signal words (so, in short, the takeaway is). If the intro opened with a story, question, or statistic, the conclusion should circle back to it — that closes the loop and makes the post feel complete.
33
34	### 2. Paragraph structure
35
36	A paragraph is a thematic unit, not a visual one. Whitespace placed for looks, with no shift in topic, breaks the reader's map of the text.
37
38	- Every paragraph must lead with its most important sentence — the core sentence. The opening sentence should make sense standalone: it's what scanners read and the unit AI systems extract for answers.
39	- The rest of the paragraph elaborates on that core sentence: supporting sentences that explain, evidence, or add nuance, optionally ending with a concluding or transitional sentence. Longer paragraphs benefit from a final summarizing sentence.
40	- One idea per paragraph. Break par

jdevalkPublisher · 13 listings

Preview

jdevalk/skills

# Readability check

Run a readability audit on a blog post draft or other multi-paragraph prose. Use when the user asks to check readability ("check readability", "readability pass

For short strings — page titles, meta descriptions, schema `description` fields, FAQ answers, profile bios, repo taglines — use the `metadata-check` skill. Fles

For whether a post earns a ranking — search intent fit, keyphrase placement, E-E-A-T, internal linking — chain into the `content-seo` skill after this audit. Re

Repojdevalk/skills

LicenseMIT

TypeSkills

CategoryMarketing

UpdatedJul 2026

Repo stars85

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

readability-check

85stars9forks

View on GitHub

How to install readability-check?

jdevalk/skills/readability-check

$npx -y skills add jdevalk/skills --skill readability-check

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Readability check
2
3	Run a readability audit on a blog post draft or other multi-paragraph prose. Use when the user asks to check readability ("check readability", "readability pass", "is this readable"), or proactively after a substantial draft is complete — as a second pass after the blog-drafting skill's critical read, not during active drafting.
4
5	For short strings — page titles, meta descriptions, schema `description` fields, FAQ answers, profile bios, repo taglines — use the `metadata-check` skill. Flesch scoring and the ten-category rubric below don't fit a 5–30 word string and will mislead.
6
7	For whether a post earns a ranking — search intent fit, keyphrase placement, E-E-A-T, internal linking — chain into the `content-seo` skill after this audit. Readability is a prerequisite for ranking, not a substitute.
8
9	## Audience calibration
10
11	Always assume the reader reads English as a second language. That's the default, not a fallback.
12
13	In technical posts, the technical sections can use domain terms the audience expects — but any non-technical paragraph (introduction, context, conclusion, transitions, examples, analogies) must be readable by a non-technical L2 reader. Setup and motivation paragraphs carry the post for readers who don't know the domain yet; they're where you lose people.
14
15	Conversational beats formal. Posts that address the reader directly ("you", "your") and occasionally ask them a question hold L2 readers far better than impersonal prose. Flag long stretches of detached, third-person register in non-technical sections.
16
17	## How readers actually read
18
19	Readers scan before they commit. They look at the headings, the first paragraph, and the first sentence of each paragraph, and decide from those alone whether to read on. Search engines and AI systems weight the same elements when working out what a text is about. That's why the audit leans hard on those three places: a post whose headings and first sentences carry the argument works for scanners, full readers, and machines at once.
20
21	## What to check
22
23	Read the full post, then report on each criterion below. For every issue, quote the specific text, reference its location (section heading or "intro" / "conclusion"), explain the problem, and suggest a concrete fix.
24
25	### 1. Overall structure and topic order
26
27	The post should read as if it was planned before it was written — topics grouped, ordered, and finished one at a time.
28
29	- The post should follow one recognizable ordering principle: thematic (aspect by aspect), chronological (old to new), didactic (easy to hard — best for explaining complicated subjects), problem–solution (state the problem, then the options), or inverted pyramid (most important first, details and background after — best for news and announcements).
30	- Related topics must sit together. Flag topic ping-pong: a subject discussed, dropped, and picked up again two sections later.
31	- The skim test: reading only the headings and the first sentence of each paragraph should yield the post's full argument. If a skimmer would miss a key point, it's buried mid-paragraph — surface it.
32	- The conclusion should restate the core message, using concluding signal words (so, in short, the takeaway is). If the intro opened with a story, question, or statistic, the conclusion should circle back to it — that closes the loop and makes the post feel complete.
33
34	### 2. Paragraph structure
35
36	A paragraph is a thematic unit, not a visual one. Whitespace placed for looks, with no shift in topic, breaks the reader's map of the text.
37
38	- Every paragraph must lead with its most important sentence — the core sentence. The opening sentence should make sense standalone: it's what scanners read and the unit AI systems extract for answers.
39	- The rest of the paragraph elaborates on that core sentence: supporting sentences that explain, evidence, or add nuance, optionally ending with a concluding or transitional sentence. Longer paragraphs benefit from a final summarizing sentence.
40	- One idea per paragraph. Break par

jdevalkPublisher · 13 listings

Preview

jdevalk/skills

# Readability check

Run a readability audit on a blog post draft or other multi-paragraph prose. Use when the user asks to check readability ("check readability", "readability pass

For short strings — page titles, meta descriptions, schema `description` fields, FAQ answers, profile bios, repo taglines — use the `metadata-check` skill. Fles

For whether a post earns a ranking — search intent fit, keyphrase placement, E-E-A-T, internal linking — chain into the `content-seo` skill after this audit. Re

Repojdevalk/skills

LicenseMIT

TypeSkills

CategoryMarketing

UpdatedJul 2026

Repo stars85

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type