CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

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

70%

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-organized, concise overview that correctly defers detail to a real one-level-deep reference file, scoring well on workflow clarity and progressive disclosure. It loses points on conciseness due to a duplicated beneficiary list and on actionability because concrete examples live only in the reference, leaving the body's guidance somewhat abstract.

Suggestions

Remove the near-verbatim duplication of the beneficiary list between the opening paragraph and the "Explain" section; keep it in one place.

Add one or two concrete ❌/✅ plain-language examples directly in the body (e.g., "utilize" → "use") so the core guidance is actionable without opening the reference.

Tighten the Check/Fix sections from abstract directives into specific, scannable checks the reviewer can apply immediately.

DimensionReasoningScore

Conciseness

The opening line ("Plain language helps users with cognitive disabilities, learning differences, attention disorders, non-native speakers, and anyone reading quickly or under stress") is repeated nearly verbatim in the "Explain" section, so the body is mostly efficient but carries unnecessary repetition, matching the score-2 anchor; not 3 because not every token earns its place, not 1 because it is not padded with concepts Claude does not need.

2 / 3

Actionability

Quick Reference gives concrete directives ("Define technical terms when first used", "Write in active voice, not passive", "Target reading level appropriate for your audience (often 8th grade)"), but the body itself holds no concrete examples and Check/Fix are abstract ("Review content for jargon", "Simplify complex sentences"), matching the score-2 "some concrete guidance but incomplete" anchor; not 3 because there are no copy-paste-ready examples in the body, not 1 because the guidance is concrete and directive.

2 / 3

Workflow Clarity

The body is organized as a clear Check → Fix → Explain → Code Review structure for a simple, single-purpose content rule; per the simple-skills scoring note, clear organization can score 3 without explicit multi-step workflows, and this is not a destructive or batch operation requiring validation checkpoints.

3 / 3

Progressive Disclosure

The SKILL.md body is a concise overview that clearly signals a one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"); the referenced file exists and contains the detailed content, matching the score-3 anchor.

3 / 3

Total

10

/

12

Passed

Description

77%

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 is well-formed with explicit "Use when..." trigger guidance and concrete actions, so completeness and specificity score high. However, the actions described (native semantics, keyboard behavior, focus flow, screen-reader output) are generic accessibility-review behaviors that do not match the skill's actual plain-language purpose, weakening trigger-term quality and distinctiveness.

Suggestions

Rewrite the description to describe plain-language actions (reviewing and simplifying wording, checking reading level, removing jargon) instead of generic accessibility semantics like keyboard behavior and screen-reader output.

Add natural trigger terms users would say for this skill, such as "plain language", "simplify this text", "make this clearer", "reading level", or "jargon".

Narrow the "Use when" clause to plain-language scenarios so the skill is distinguishable from sibling accessibility skills and does not trigger for the wrong skill.

DimensionReasoningScore

Specificity

Quotes concrete actions: "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — a list of multiple specific actions, matching the score-3 anchor; not 2 because it goes beyond naming a domain and some actions. The actions are concrete even though they describe general accessibility review rather than plain-language work.

3 / 3

Completeness

Explicitly answers both: an explicit "Use when..." trigger clause and stated actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), matching the score-3 anchor; not 2 because the "when" is explicitly stated rather than merely implied.

3 / 3

Trigger Term Quality

Contains some relevant keywords ("reviewing rendered HTML, interactive components, or design-system patterns", "related to Write in plain language") but lacks the natural terms a user would actually say for plain language ("simplify this text", "make this clearer", "reading level", "jargon"), matching the score-2 anchor; not 3 because coverage of natural plain-language triggers is thin, not 1 because some relevant keywords are present.

2 / 3

Distinctiveness Conflict Risk

The named actions ("native semantics", "keyboard behavior", "focus flow", "accessible names", "screen-reader output") describe general accessibility review that overlaps with sibling accessibility skills, matching the score-2 "could still overlap with similar skills" anchor; not 3 because it is not a clearly distinct niche, not 1 because it does name specific domains.

2 / 3

Total

10

/

12

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.