CtrlK
BlogDocsLog inGet started
Tessl Logo

search-input

Use when reviewing templates, rendered HTML, or shared components related to Make search inputs accessible. Validate the final browser-facing markup, not just the source framework abstraction.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a well-structured, lean rule-style skill: concise, with concrete actionable attribute-level guidance, a clear simple-task workflow, and proper one-level-deep progressive disclosure to a real reference file. It scores maximally across all content dimensions.

DimensionReasoningScore

Conciseness

The body is a lean ~30-line overview with one- or two-line sections and no padding or explanation of concepts Claude already knows; the single motivational intro line is brief and earns its place.

3 / 3

Actionability

Gives concrete, specific guidance naming exact attributes to verify and apply ("type='search'", "role='search'", "aria-label", "accessible autocomplete suggestions"); as an instruction-only skill, the absence of inline code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

For a simple single-task skill the action is unambiguous and well-organized into Quick Reference, Check, Fix, Explain, and Code Review sections; no destructive or batch operation requires validation checkpoints.

3 / 3

Progressive Disclosure

The body is a concise overview that defers full details to a clearly signaled, one-level-deep reference ('see references/rule.md'), and the referenced file exists and is real.

3 / 3

Total

12

/

12

Passed

Description

67%

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 names a clear domain with concrete actions, scoring well on completeness. It loses points on specificity and trigger coverage for listing only two actions and omitting common accessibility-related trigger terms, and has mild overlap risk with general HTML accessibility skills.

Suggestions

Enumerate more concrete actions (e.g., 'check type=\"search", role="search", labels, and keyboard-navigable autocomplete') to lift specificity from 2 to 3.

Add common natural trigger terms users would say, such as 'accessible', 'accessibility', 'a11y', or 'screen reader', to improve trigger term coverage.

Tighten the trigger to reduce overlap with generic HTML skills, e.g., 'Use when reviewing rendered HTML for accessible search inputs specifically'.

DimensionReasoningScore

Specificity

Names the domain ('templates, rendered HTML, or shared components') and concrete actions ('reviewing', 'Validate the final browser-facing markup'), but enumerates only two actions rather than a comprehensive list of specific concrete actions, matching the 'names domain and some actions' anchor rather than the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

Explicitly answers what ('reviewing templates, rendered HTML, or shared components... Validate the final browser-facing markup') and when ('Use when reviewing...'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms ('rendered HTML', 'templates', 'shared components', 'search inputs') but omits common variations a user might say such as 'accessibility', 'a11y', or 'screen reader', so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The 'search inputs accessible' niche is fairly distinct, but the broader triggers ('rendered HTML', 'shared components') overlap with general frontend/HTML accessibility skills, so it could still trigger for the wrong similar skill.

2 / 3

Total

9

/

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.