CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

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

78%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 tight, well-structured overview with concrete readability thresholds and a clean analysis→fix→report flow, deferring depth to a single well-signaled reference. Main weakness is minor repetition in the Explain section and no inline score-computation method.

DimensionReasoningScore

Conciseness

The body is lean with tight Quick Reference bullets and sectioned Check/Fix steps; the only padding is the 'Explain' section, which restates the bounce-rate/engagement-signal point already made in the intro.

4 / 5

Actionability

Check and Fix give concrete, specific thresholds (sentences > 25 words, paragraphs > 4 sentences, Flesch Reading Ease 60+) and Code Review specifies exactly what to count and report, though no inline formula/tool for computing the score is given.

4 / 5

Workflow Clarity

Check → Fix → Explain → Code Review forms a clear sequence ending in a reporting/verification step; as a non-destructive analysis skill it avoids the destructive-cap, but lacks an explicit validation checkpoint.

4 / 5

Progressive Disclosure

The SKILL.md is a well-sectioned overview that defers full details, examples, and the Flesch scale to a single clearly signaled one-level-deep reference (references/rule.md, which exists).

5 / 5

Total

17

/

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 leads with a clear 'Use when' trigger and a broad content-review framing, but it omits the skill's core capability — assessing reading level/readability — leaving the 'what' generic and raising overlap risk with other SEO skills.

Suggestions

Name the concrete action up front, e.g. 'Assesses page readability and estimates Flesch-Kincaid reading grade level.'

Add readability-specific trigger terms users would say ('reading level', 'readability', 'Flesch', 'too hard to read', 'reading grade').

Tighten the what/when pairing so the distinctive purpose (reading-level analysis) is explicit before listing applicable content types.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing content pages for user experience and SEO') and a single action ('reviewing'), but the action is generic and it never names the actual task (readability / reading level), so it is not comprehensive.

3 / 5

Completeness

An explicit 'Use when...' clause supplies the trigger, and 'reviewing content pages for user experience and SEO' gives a what, but the what is vague and does not state the skill's true purpose (assessing reading level).

4 / 5

Trigger Term Quality

It uses natural phrases users would say ('blog posts', 'landing pages', 'how-to guides', 'long-form content', 'user experience', 'SEO') with good coverage, though it omits readability-specific terms a user might actually mention.

4 / 5

Distinctiveness Conflict Risk

Framed as broad 'content review for UX and SEO', it overlaps with general SEO/content-quality skills and lacks the distinctive readability/reading-level trigger that would separate it from siblings.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.