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.

57

Quality

66%

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/draggable-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well structured with a clean overview and a real one-level-deep reference, but the body spends tokens restating a known concept and repeats guidance across sections without concrete markup or an explicit verify step.

Suggestions

Remove the opening explanatory sentence about drag and drop being mouse-dependent — Claude already knows this — and de-duplicate the keyboard/ARIA/live-region items across Quick Reference, Check, and Fix to tighten conciseness.

Add a short concrete HTML/ARIA markup snippet in the Fix section showing an accessible draggable element with aria-grabbed, aria-dropeffect, and a live region, instead of only naming the attributes.

Make the Check-to-Fix flow explicit with a verification checkpoint, e.g. 'Confirm a keyboard user can complete the drag operation and that a live region announces each state change,' to add a validation feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the opening sentence ('Drag and drop is mouse-dependent by default—keyboard and screen reader users are completely locked out') explains a concept Claude already knows, and the Quick Reference, Check, and Fix sections repeat the same items.

2 / 3

Actionability

The Fix section names concrete specifics (arrow keys, Enter/Space, aria-grabbed, aria-dropeffect, status announcements) but provides no actual markup example in the body, delegating all code to the reference.

2 / 3

Workflow Clarity

Check/Fix/Explain/Code Review sections imply a loose sequence but there is no explicit ordering or validation checkpoint to confirm the fix restored keyboard/screen-reader equivalence.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md') for full implementation details, and that file exists, matching the well-signaled one-level-deep anchor.

3 / 3

Total

9

/

12

Passed

Description

75%

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 clearly states both when to use the skill and what it validates, with an explicit trigger clause and a distinct niche. It is slightly held back by actions that are somewhat abstract and trigger phrasing that echoes the rule title rather than natural user speech.

DimensionReasoningScore

Specificity

It names the domain ('templates, rendered HTML, or shared components') and actions ('reviewing', 'Validate the final browser-facing markup') but does not list multiple specific concrete actions like the top anchor.

2 / 3

Completeness

It has an explicit 'Use when reviewing templates, rendered HTML, or shared components' trigger plus a clear what-it-does clause ('Validate the final browser-facing markup, not just the source framework abstraction').

3 / 3

Trigger Term Quality

Relevant keywords appear (templates, rendered HTML, shared components, drag and drop, accessible, markup) but common variations are missing and 'Make drag and drop accessible' reads as a rule title rather than natural phrasing.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and distinct (drag-and-drop accessibility in rendered HTML), qualified by 'related to Make drag and drop accessible', making overlap with other skills unlikely.

3 / 3

Total

10

/

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.