CtrlK
BlogDocsLog inGet started
Tessl Logo

draggable-accessibility

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

67

Quality

81%

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

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.

The body is a well-structured overview that pairs concise actionable review guidance with a clearly signaled one-level reference for full examples. Tightening the minor redundancy between Quick Reference and Check, and adding an explicit verification checkpoint, would lift the remaining dimensions.

Suggestions

Remove the conceptual opening sentence or fold it into Quick Reference to eliminate padding that Claude already knows.

Dedupe the Quick Reference bullets against the Check section so the review actions appear once, authoritatively.

Add an explicit verification step in the workflow (e.g., 'Confirm keyboard-only and screen-reader paths complete the task') to give the review sequence a clear checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and delegates detail to references/rule.md, but the opening 'Drag and drop is mouse-dependent by default…' and overlap between Quick Reference bullets and the Check section add mild padding, keeping it just below fully lean.

4 / 5

Actionability

Concrete, specific guidance naming 'arrow keys, Enter/Space', 'aria-grabbed, aria-dropeffect', and 'status announcements'; no inline executable code, but as an instruction/review skill the actionable specifics are sufficient, with minor gaps filled by the reference.

4 / 5

Workflow Clarity

Check / Fix / Explain / Code Review sections give a clear sequenced review workflow; this is a non-destructive review skill so the validation-cap does not apply, though the sequence lacks an explicit checkpoint, holding it at 4 rather than 5.

4 / 5

Progressive Disclosure

A concise overview with well-signaled, one-level-deep navigation to references/rule.md (a real bundle file), matching the anchor for clear overview plus appropriately split detail with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong description with explicit what/when triggers and concrete review targets scoped to drag-and-drop accessibility. It could be slightly more distinctive and add a few more natural synonyms, but it clearly communicates scope and trigger conditions.

DimensionReasoningScore

Specificity

Names concrete review targets ('templates, rendered HTML, or shared components') and a specific validation action ('Validate the final browser-facing markup, not just the source framework abstraction'); not a level-5 exhaustive action list but clearly above the 1–2 action midpoint.

4 / 5

Completeness

Explicitly answers 'when' with a 'Use when reviewing...' trigger and 'what' with 'Validate the final browser-facing markup...', matching the anchor that requires concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Natural terms like 'templates', 'rendered HTML', 'shared components', and 'drag and drop' are present and would be said by users, but a few common synonyms/variations are missing, fitting the 'good coverage, a few missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The drag-and-drop accessibility niche is distinct, but the broad 'templates, rendered HTML, or shared components' framing carries minor overlap risk with general HTML/accessibility review skills rather than the minimal-conflict level 5.

4 / 5

Total

17

/

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.