CtrlK
BlogDocsLog inGet started
Tessl Logo

accesskeys

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure accesskey values are unique. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

61

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/accesskeys/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-organized, brief skill body that appropriately offloads detail to one referenced file. Its main weakness is actionability: the inline guidance describes what to check but stops short of giving an executable method or selector for finding duplicate accesskeys.

Suggestions

Add an executable check to the 'Check' section, e.g. a grep/selector for duplicate accesskey values (e.g. `grep -rhoi 'accesskey="\(.\)"' | sort | uniq -d`) so Claude can run it directly.

Make the 'Fix' step prescriptive with a concrete example (assign a unique unused value, or remove the redundant attribute) rather than the generic 'assign unique values or remove redundant ones'.

Tighten the 'Explain' section to a one-liner or fold it into Quick Reference to remove restatement of obvious accessibility rationale.

DimensionReasoningScore

Conciseness

The body is lean and sectioned with minimal padding; a few lines (the 'Explain' section and Quick Reference bullet on keyboard users) restate obvious context, keeping it just below a 5.

4 / 5

Actionability

Guidance is concrete in direction ('Check for duplicate accesskey attributes across the document') but lacks executable commands or a specific verification query, and the 'Fix' step is generic rather than prescriptive.

3 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sequence gives a clear flow for this simple review skill; no explicit validation checkpoint is stated in the body itself, but the rule is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep pointer to references/rule.md, matching the ideal structure for a simple skill.

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.

The description is concrete, third-person, and includes an explicit trigger clause covering both what and when. It is strong but not exceptional: a few natural synonyms and tighter user-facing trigger phrasing would push it to the top level.

DimensionReasoningScore

Specificity

Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), with only minor coverage gaps; not quite the comprehensive set needed for a 5.

4 / 5

Completeness

Both 'what' (the review actions) and an explicit 'Use when...' trigger clause are present; the 'when' could be tied more tightly to user phrasing rather than review contexts.

4 / 5

Trigger Term Quality

Strong natural-term coverage ('rendered HTML', 'interactive components', 'design-system patterns', 'accesskey values', 'keyboard behavior', 'focus flow', 'accessible names', 'screen-reader output'); a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

'accesskey values are unique' carves a clear niche, though the surrounding general accessibility-review language creates minor overlap risk with sibling a11y skills.

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.

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.