CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

form-validation

Use when reviewing templates, rendered HTML, or shared components related to Validate forms accessibly. Validate the final browser-facing markup, not just the source framework abstraction. Distinguish between browser-posted forms and client-handled React forms so you do not over-report missing `method` or `action` as accessibility defects.

Quality

77%

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/form-validation/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.

A lean, well-structured instruction-only review skill with concrete attribute-level checks and an appropriately deferred one-level reference. Its main costs are a motivational intro sentence and heavy repetition of the same checks across the Check, Fix, and Code Review sections.

Suggestions

Cut the motivational opening sentence about screen reader frustration and form abandonment — Claude already knows why accessible validation matters.

Deduplicate guidance repeated across sections: the React method/action caveat appears in both Check and Fix, and the aria-describedby/required-field guidance appears in Quick Reference, Check, Fix, and Code Review.

Merge or clearly differentiate the Check and Code Review sections, which describe substantially the same review activity.

DimensionReasoningScore

Conciseness

The ~35-line body is mostly efficient, but the motivational intro ("leaves screen reader users unable to understand what went wrong... causing frustration and form abandonment") explains what Claude already knows, and the same guidance repeats across sections — aria-describedby/required appears in Quick Reference, Check, Fix, and Code Review, and the React method/action caveat appears in both Check and Fix.

3 / 5

Actionability

Concrete attribute-level guidance ("aria-describedby", "aria-invalid", "required or aria-required", "fieldset and legend") plus a specific false-positive rule ("Do not flag React forms... when onSubmit clearly handles submission client-side"); no inline code, but full examples are appropriately carried in references/rule.md, leaving only minor gaps.

4 / 5

Workflow Clarity

A clear single-action review flow (Quick Reference → Check → Fix → Explain → Code Review) that is unambiguous about the core task — flag rendered-markup violations — but the Check and Code Review sections describe substantially the same review activity, blurring which governs the review pass.

4 / 5

Progressive Disclosure

A concise overview that defers "full implementation details, code examples, and framework-specific guidance" to references/rule.md, which exists, is one level deep (416 lines of worked examples), and is clearly signaled — an appropriate split with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

75%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.

A solid description with an explicit "Use when" trigger, several concrete actions, and a genuinely useful false-positive guard. Its weaknesses are mild: awkward phrasing ("related to Validate forms accessibly") and missing common synonyms like "a11y" or "ARIA".

DimensionReasoningScore

Specificity

Names several concrete actions — "reviewing templates, rendered HTML, or shared components", "Validate the final browser-facing markup, not just the source framework abstraction", "Distinguish between browser-posted forms and client-handled React forms" — with minor gaps (the specific accessibility techniques like aria-describedby are not named).

4 / 5

Completeness

Both what and when are present with an explicit "Use when reviewing templates, rendered HTML, or shared components..." trigger, but the what is muddied by the awkward "related to Validate forms accessibly" phrasing and leans on edge-case guidance rather than a crisp capability statement.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say — "templates", "rendered HTML", "shared components", "React forms", "accessibility" — but misses common variations like "a11y", "ARIA", "screen reader", or "form validation".

4 / 5

Distinctiveness Conflict Risk

A mostly distinct niche — accessible form validation on rendered markup with a React false-positive guard — with only minor overlap risk against sibling HTML/accessibility review skills triggered by terms like "rendered HTML" or "accessibility".

4 / 5

Total

16

/

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/form-validation/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.