CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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/search-input/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 well-structured body for a rule-based review skill: exact attributes are named, code examples are correctly pushed to a real, substantive one-level reference, and the review scope is stated concretely. The main flaw is redundancy — Quick Reference, Check, and Fix repeat the same four requirements and the Explain section is filler.

Suggestions

Merge the Quick Reference, Check, and Fix sections into one statement of requirements to eliminate the three-fold repetition of type='search', labels, and role='search'.

Drop or tighten the Explain section, which restates the intro sentence ('Search is a primary navigation method...') without adding guidance.

Add one short compliant-vs-violating markup snippet inline in the Check section so reviewers can pattern-match the rendered HTML without opening the reference.

DimensionReasoningScore

Conciseness

The body is short but noticeably repetitive: the Quick Reference bullets, the Check section ("Verify search inputs use type='search', have accessible labels, and use role='search'"), and the Fix section ("Implement search with type='search', visible or aria-label, form role='search'...") restate the same four requirements three times, and the Explain section ("Explain how accessible search implementations help users find content efficiently regardless of their abilities") is filler that repeats the intro. Merging Check/Fix and dropping the Explain restatement would reach anchor 4.

3 / 5

Actionability

Concrete, specific guidance for an instruction-only skill: exact attributes are named ("type='search' and role='search' on the form", "visible or screen reader accessible label", "Make autocomplete suggestions keyboard navigable", "Announce result counts"), and executable code is appropriately deferred to the real references/rule.md (which contains a complete working form example). Minor gap: no inline snippet of compliant markup in SKILL.md itself and 'keyboard navigable' / 'announce result counts' don't say how in the body.

4 / 5

Workflow Clarity

The Check -> Fix -> Explain -> Code Review sequence gives a clear order of operations for applying the rule, and the Code Review section states the review scope concretely ("Flag exact elements, attributes, and routes where the rendered HTML violates the rule"). It falls short of 5 because there is no severity/output guidance (how to report findings) and the section boundaries blur due to repetition, but the single action — validate rendered markup against the rule — is largely unambiguous and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

A ~45-line overview with a clearly signaled, one-level-deep pointer to the verified 405-line references/rule.md ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The bundle check confirms the reference exists, contains substantive implementation detail and executable code, and contains no nested references — matching the well-signaled, appropriately split structure of anchor 5.

5 / 5

Total

16

/

20

Passed

Description

62%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 serviceable description with an explicit and well-targeted Use-when clause plus a useful what-statement about validating rendered markup over framework abstractions. Its weaknesses are a mangled embedded rule title that hurts readability, thin enumeration of concrete capabilities, and missing natural accessibility synonyms.

Suggestions

Rewrite the spliced clause 'related to Make search inputs accessible' into natural prose, e.g., 'Use when reviewing templates, rendered HTML, or shared components that render search inputs, to check their accessibility.'

Add the concrete checks as capabilities and natural trigger synonyms: 'Verify type="search", accessible labels, form role="search", keyboard-navigable autocomplete, and screen-reader result announcements. Use when the user mentions search inputs, search forms, a11y, or screen-reader accessibility.'

Distinguish the trigger from sibling accessibility rules by scoping it to search functionality specifically (e.g., 'search bars, search forms, or site search') rather than the generic 'templates, rendered HTML, or shared components' framing shared by all rules in this category.

DimensionReasoningScore

Specificity

The description names the domain ("Make search inputs accessible") and 1-2 concrete actions ("reviewing templates, rendered HTML, or shared components", "Validate the final browser-facing markup"), but stops short of the several specific actions of anchor 4 — e.g., it never mentions checking type='search', labels, or role='search, which are the skill's actual capabilities.

3 / 5

Completeness

Both parts are explicitly present: an explicit trigger ("Use when reviewing templates, rendered HTML, or shared components related to...") and a what-statement ("Validate the final browser-facing markup, not just the source framework abstraction"). It does not reach 5 because the what is a single scope clarification and the mangled "related to Make search inputs accessible" phrase leaves the concrete capabilities unstated; it is above 3 because the when-clause is explicit and specific, not weakly implied.

4 / 5

Trigger Term Quality

Some relevant natural keywords are present ("templates", "rendered HTML", "shared components", "search inputs"), but common variations users would say are missing ("accessibility", "a11y", "search bar", "screen reader", "search form"), and the embedded clause "related to Make search inputs accessible" reads as a rule title spliced into a sentence rather than a natural trigger phrase.

3 / 5

Distinctiveness Conflict Risk

"search inputs" carves out a clear niche with minimal conflict risk, though the generic trigger framing "reviewing templates, rendered HTML, or shared components" is shared verbatim by sibling HTML/accessibility rules (forms, labels, landmarks), creating minor overlap with closely related skills rather than none.

4 / 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/search-input/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.