CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reading-level

Use when reviewing content pages for user experience and SEO. Applies to blog posts, landing pages, how-to guides, and any long-form content intended for a broad audience.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/reading-level/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable overview with concrete thresholds and a clean single-level reference into references/rule.md. Its main weaknesses are redundancy — the 'Code Review' section nearly duplicates 'Check' and 'Explain' restates common knowledge — and the absence of any post-fix verification step or method for computing the readability score.

Suggestions

Merge the near-duplicate 'Check' and 'Code Review' sections into one procedure to remove redundancy and free token budget.

Cut or shrink the 'Explain' section — Claude already knows what readability, bounce rate, and dwell time are.

Add a verification loop after 'Fix' (e.g., 'Recompute the Flesch score and iterate until FRE ≥ 60') and specify how to compute the grade level (formula or tool).

DimensionReasoningScore

Conciseness

The body is compact overall, but the 'Explain' section covers concepts Claude already knows ("Readability measures how easy content is to understand...") and the 'Code Review' section duplicates 'Check' almost verbatim ("Calculate or estimate the Flesch-Kincaid Grade Level... sentences longer than 25 words, paragraphs longer than 4 sentences"). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably-verbose anchor at 2.

3 / 5

Actionability

The guidance is concrete with specific thresholds — "Flesch Reading Ease score of 60–70", "sentences longer than 25 words", "paragraphs longer than 4 sentences", "subheadings to break up text every 200–300 words" — plus concrete fix techniques ("break long sentences at conjunctions, replace passive voice with active voice"). Not a 5 because 'Calculate or estimate the Flesch-Kincaid Grade Level' gives no method or command for actually computing the score.

4 / 5

Workflow Clarity

The Check → Fix sequence is clear and unambiguous for a simple single-purpose skill, so no destructive-operation cap applies. Not a 5 because there is no verification loop after fixing (e.g., re-check that the revised text hits FRE 60+), and the redundant 'Code Review' section slightly muddles the flow.

4 / 5

Progressive Disclosure

The body is a clean overview (Quick Reference, Check, Fix, Explain) that defers detail via one clearly signaled, one-level-deep reference — "see `references/rule.md`" — which exists in the bundle and contains the promised implementation details without further nested bundle references. This matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit and well-scoped 'Use when...' trigger with good natural keywords for content types, but the 'what' is thin: it never mentions reading level, readability, or grade-level assessment, which are the skill's distinctive capabilities. This weakens both specificity and distinctiveness against other SEO/content skills.

Suggestions

Name the concrete actions in the description, e.g., 'Calculates Flesch Reading Ease / Flesch-Kincaid grade level, flags long sentences, passive voice, and jargon, and suggests plain-language rewrites.'

Include the skill's distinctive trigger terms — 'readability', 'reading level', 'reading grade' — so it is distinguishable from generic SEO-review or UX-review skills.

Tighten the 'when' clause to lead with the readability intent (e.g., 'Use when checking whether a page's reading level matches its audience') rather than broad 'user experience and SEO' phrasing.

DimensionReasoningScore

Specificity

The description names the domain ("content pages", "user experience and SEO") and a single action ("reviewing") but lists no further concrete actions, matching the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because several specific actions (e.g., readability scoring, sentence simplification) would need to be named, and not a 2 because it goes beyond a bare domain mention with a purpose-scoped action.

3 / 5

Completeness

Both parts are present: a 'what' ("reviewing content pages for user experience and SEO") and an explicit 'when' ("Use when reviewing content pages... Applies to blog posts, landing pages, how-to guides..."). It is not a 5 because the 'what' is generic and never states the core capability (assessing reading level / readability), while the 'when' is fully explicit.

4 / 5

Trigger Term Quality

It includes natural phrases users would say — "blog posts", "landing pages", "how-to guides", "long-form content", "SEO" — giving good keyword coverage. It falls short of 5 because common natural terms for this skill's actual niche, such as "readability", "reading level", or "plain language", are absent.

4 / 5

Distinctiveness Conflict Risk

"Reviewing content pages for user experience and SEO" is broadly phrased and could overlap with general SEO-audit, UX-review, or content-quality skills; the content-type list narrows it but the skill's true niche (reading level) is unstated. This fits 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct anchor at 4.

3 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/reading-level/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.