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.

68

Quality

82%

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

72%

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 simple review skill with clean progressive disclosure to one real reference. It is held back by guidance that describes what to check without a concrete method to find duplicates and by the absence of an explicit verification step in the body.

Suggestions

Add a concrete detection method, e.g. `document.querySelectorAll('[accesskey]')` and a note to compare attribute values, so the Check step is executable rather than descriptive.

Insert an explicit verification checkpoint in the body (e.g. re-run the duplicate scan and confirm with keyboard-only navigation) rather than leaving it implied by the Code Review section.

DimensionReasoningScore

Conciseness

The body is lean with short Quick Reference, Check, Fix, Explain, and Code Review sections and no padding with concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Guidance is instruction-only and reasonably specific ("Check for duplicate `accesskey` attributes across the document", "Assign unique values… or remove redundant ones") but omits the how — no selector, command, or method to actually locate duplicates, so key details are missing.

2 / 3

Workflow Clarity

A Check→Fix→Explain→Code Review sequence is present, but the body has no explicit validation/verification checkpoint even though the Code Review section implies verifying the fix; checkpoints are implicit rather than stated.

2 / 3

Progressive Disclosure

A single one-level-deep reference (`references/rule.md`, verified to exist) is clearly signaled at the end, and the body is well-organized into short sections — appropriate for a sub-50-line simple skill.

3 / 3

Total

10

/

12

Passed

Description

92%

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 strong description with an explicit trigger, concrete multi-action capability list, and natural trigger terms. Its main weakness is the boilerplate accessibility-review framing that reduces distinctiveness against other frontendchecklist accessibility skills.

Suggestions

Lead with the accesskey-specific trigger (e.g. "Use when auditing `accesskey` attributes for uniqueness") so the skill is distinguishable from generic accessibility-review skills.

Drop the awkward embedded phrase "related to Ensure accesskey values are unique" in favor of natural user phrasing.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" lists multiple specific concrete actions, matching the score-3 anchor.

3 / 3

Completeness

An explicit "Use when…" clause supplies the trigger and the subsequent action list supplies the what, answering both required questions.

3 / 3

Trigger Term Quality

Natural review-time terms appear ("accesskey", "keyboard behavior", "focus flow", "accessible names", "screen-reader output") giving good coverage of what a user would actually say.

3 / 3

Distinctiveness Conflict Risk

"reviewing rendered HTML, interactive components, or design-system patterns" is generic accessibility-review phrasing shared by many similar skills; only the embedded "accesskey values are unique" phrase narrows it, so it could still overlap with sibling accessibility skills.

2 / 3

Total

11

/

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.