CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plain-language

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Write in plain language. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plain-language/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 concise, well-structured overview with a clean Check/Fix/Explain flow and a properly signaled single reference file that exists in the bundle. Its main weakness is actionability: verification steps (reading level, accessibility tooling) are named but not given concrete methods, with all examples and specifics pushed to the reference.

Suggestions

Add one concrete method for the Check step, e.g., a named readability measure (Flesch-Kincaid grade level) or a one-line ❌/✅ rewrite example inline so the review loop is executable without opening the reference.

Deduplicate repeated guidance — "Define technical terms when first used" and the cognitive-disability audience sentence each appear twice — to tighten the body.

Name a specific browser accessibility tool or check in the Code Review section instead of the generic "browser accessibility tooling or assistive tech".

DimensionReasoningScore

Conciseness

The body is lean — short bullets, four brief sections, no explanations of concepts Claude already knows. It loses a point for redundancy: "Define technical terms when first used" appears in both Quick Reference and Fix, and the Explain section repeats the intro sentence nearly verbatim ("helps users with cognitive disabilities, learning differences, attention disorders, non-native speakers...").

4 / 5

Actionability

The Fix section gives concrete directives ("Simplify complex sentences", "Write in active voice", "Target a reading level appropriate for your broadest audience") and Quick Reference adds "often 8th grade", but the Check section says what to verify without any method — no readability formula, tool, or before/after example inline (those live in references/rule.md). Not 2 because the guidance is more than high-level hints; not 4 because key execution details are delegated entirely to the reference file.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure lays out a clear, simple sequence appropriate to a single-purpose review skill, and the Check section acts as checkpoints ("Review content for jargon... Verify reading level is appropriate... Check that instructions are clear"). Not 5 because "Verify reading level" and "note how to verify the fix with browser accessibility tooling" name verification without any concrete step or tool, leaving minor gaps.

4 / 5

Progressive Disclosure

The body is a short, well-organized overview with clearly labeled sections, and it points to exactly one one-level-deep reference — "see `references/rule.md`" — which exists in the bundle and is explicitly scoped ("full implementation details, code examples, and framework-specific guidance"). This matches the simple-skill pattern of a clear overview with well-signaled references.

5 / 5

Total

16

/

20

Passed

Description

63%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 "Use when" trigger and a list of concrete inspection actions, satisfying both what and when. However, the actions describe generic accessibility inspection rather than plain-language review, and the awkward "related to Write in plain language" phrasing weakens trigger quality and distinctiveness.

Suggestions

Rewrite the action list to describe the actual plain-language task (e.g., "Review content for jargon, passive voice, and long sentences; simplify text and define technical terms") instead of generic accessibility inspection steps.

Add natural trigger terms users would say for this task — "readability", "reading level", "jargon", "simplify the text" — to improve keyword coverage.

Fix the templated phrasing "related to Write in plain language" so the when-clause reads naturally (e.g., "Use when reviewing or writing UI copy, documentation, or error messages for plain language").

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — which goes beyond naming the domain. It falls short of 5 because the actions describe generic accessibility inspection rather than comprehensively covering the plain-language review task the skill is named for, and no reading-level/jargon actions are stated.

4 / 5

Completeness

Both parts are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Write in plain language" (when) and a concrete what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). Not 5 because the when-clause is awkwardly phrased ("related to Write in plain language") and conflates plain-language review with accessibility inspection, leaving the actual triggering scenario less crisp than the anchor-5 example.

4 / 5

Trigger Term Quality

"plain language" is a natural user phrase, and terms like "rendered HTML", "interactive components", and "screen-reader output" are plausible triggers, but common variations users would actually say for this task — "readability", "jargon", "reading level", "simplify text" — are absent. Not score 2 since more than one relevant keyword is present; not 4 because the natural-term coverage for the plain-language domain itself is thin.

3 / 5

Distinctiveness Conflict Risk

The stated actions (native semantics, keyboard behavior, focus flow, accessible names, screen-reader output) are the standard checklist of any generic accessibility-review skill, so in a collection of related skills it would overlap heavily. It is not score 2 because the plain-language anchoring and "Use when" scoping give it some distinguishing signal.

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/plain-language/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.