CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

select-name

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

Quality

80%

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/select-name/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-structured single-purpose skill: the body gives concrete check/fix guidance and cleanly defers code examples to a real, one-level reference file. Main gaps are the absence of any inline HTML snippet and an implicit rather than explicit verification checkpoint.

Suggestions

Replace the opening rationale sentence with a minimal correct-vs-incorrect HTML snippet so the most common case is fixable without opening the reference.

Make the verification step explicit in the Check or Code Review section (e.g., a named tool/command such as an accessibility-tree inspection or axe DevTools) instead of the vague 'where relevant'.

Drop or merge the 'Code Review' paragraph, which restates the frontmatter description, to remove redundancy.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with a quick-reference list and terse Check/Fix sections, but the opening sentence explains why accessible names matter (which Claude already knows) and the 'Code Review' paragraph largely restates the frontmatter description, so a few tokens could be trimmed.

4 / 5

Actionability

Concrete, executable guidance is present ('Use the `<label>` element with a matching `for` attribute', 'aria-label or aria-labelledby', 'matches the `id` of the `<select>` tag'), and the one-level reference carries full correct/incorrect HTML examples, but the body itself contains no code snippet and omits details like the title-attribute fallback, leaving minor gaps.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence exists with a verification mention ('note how to verify the fix with browser accessibility tooling'), but the validation step is loose ('where relevant') rather than an explicit checkpoint, so it sits between anchors 4 and 5 — not the fully explicit validation loop of a 5.

4 / 5

Progressive Disclosure

A short, well-sectioned overview delegates full implementation details, code examples, and framework guidance to a single well-signaled, one-level-deep reference (`references/rule.md`, which exists and contains real content), matching the clear-overview pattern the rubric rewards for simple skills.

5 / 5

Total

17

/

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 explicit 'Use when' triggers, third-person voice, and several concrete inspection actions. Its main weaknesses are the awkward embedded rule title in the when clause and missing common synonyms like 'label' and 'dropdown'.

Suggestions

Reword the when clause to natural phrasing, e.g., 'Use when reviewing forms or rendered HTML with <select> elements that need labels or accessible names', instead of embedding the rule title verbatim.

Add missing natural trigger terms users would actually say: 'label', 'dropdown', 'form controls', 'screen reader'.

Mention the fix side of the skill (adding labels/aria attributes) so the what-clause covers both checking and remediation.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') in a named domain, but coverage has minor gaps (no mention of fixing/adding labels) — anchor 4, not the comprehensive coverage of 5.

4 / 5

Completeness

Both parts are present: an explicit 'Use when reviewing rendered HTML...' trigger and a concrete what ('Check native semantics first, then inspect...'). The when clause is explicit but awkwardly phrased ('related to Provide accessible names for select elements' embeds the rule title verbatim), keeping it below the cleanly concrete anchor 5 and clearly above anchor 3's missing/weak when.

4 / 5

Trigger Term Quality

Good natural-term coverage ('rendered HTML', 'select elements', 'accessible names', 'screen-reader', 'keyboard behavior', 'focus flow'), but common user phrasings like 'label', 'dropdown', and 'form' are missing, so it falls just short of the synonym-complete anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (accessible names for select elements) is distinct, but the templated trigger prefix ('rendered HTML, interactive components, or design-system patterns') is generic and shared by sibling accessibility rules, creating minor overlap risk with closely related skills — anchor 4 rather than the minimal-conflict anchor 5.

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/select-name/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.