CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

77%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 lean, well-organized overview with excellent progressive disclosure to a verified single reference file and a clear single-task review workflow. The main weakness is actionability: the body names attributes and keys but includes no executable example, and it recommends deprecated ARIA attributes (aria-grabbed, aria-dropeffect) while leaving the '(or newer attributes)' unspecified.

Suggestions

Name the current alternatives to the deprecated aria-grabbed/aria-dropeffect attributes (or drop the hedge), since '(or newer attributes)' gives no actionable guidance.

Include one minimal inline markup or keyboard-pattern snippet in the Fix section so the body's guidance is executable without opening the reference file.

Trim the redundancy between the Quick Reference bullets and the Check section, which restate the same three points.

DimensionReasoningScore

Conciseness

The body is lean (~45 lines) with a tight Quick Reference and short sections. There is minor redundancy — 'Verify drag and drop interfaces have keyboard alternatives, proper ARIA attributes, and live region announcements' restates the Quick Reference bullets, and the Code Review section echoes the frontmatter description — matching anchor 4 (efficient, minor trimming possible) rather than anchor 3's noticeable padding.

4 / 5

Actionability

Concrete specifics are named ('aria-grabbed', 'aria-dropeffect', 'arrow keys, Enter/Space', 'live region announcements', 'status announcements'), but there is no executable code inline and the hedge '(or newer attributes)' leaves the current alternatives unnamed — notable since aria-grabbed and aria-dropeffect are deprecated ARIA attributes. This matches anchor 3 (some concrete guidance but incomplete, key details deferred to the reference file) rather than anchor 4.

3 / 5

Workflow Clarity

This is a simple, single-purpose review skill under 50 lines, and the Check → Fix → Explain → Code Review sequence is unambiguous and well-organized, so the simple-skill exception applies and workflow clarity scores 5. No destructive or batch operations are involved that would require validation checkpoints.

5 / 5

Progressive Disclosure

The body is a clear overview with a single well-signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and the referenced file exists and appropriately holds the bulk content (code examples, React and Kanban patterns, verification steps). This matches anchor 5.

5 / 5

Total

17

/

20

Passed

Description

70%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 well-formed description with an explicit 'Use when' trigger, good natural keywords, and a clearly distinct niche. Its main weakness is a thin 'what' side: it says to validate the final markup but never states the concrete checks (keyboard alternatives, ARIA attributes, live-region announcements) the skill performs.

Suggestions

State the concrete validation actions in the description, e.g., 'Check for keyboard alternatives, ARIA attributes, and live-region announcements in the rendered markup.'

Add natural trigger terms users would say, such as 'ARIA', 'keyboard navigation', 'screen reader', or 'sortable', to improve trigger-term coverage.

Clarify the 'what' beyond a single validate directive so the description comprehensively covers what the skill does, not just when to use it.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing templates, rendered HTML, or shared components related to Make drag and drop accessible') and 1-2 concrete actions ('Validate the final browser-facing markup'), but does not list several specific actions or state what accessibility criteria are checked. This matches anchor 3; it falls short of anchor 4 because it does not enumerate several specific capabilities.

3 / 5

Completeness

Both 'what' and 'when' are present: the explicit trigger 'Use when reviewing templates, rendered HTML, or shared components...' and the action 'Validate the final browser-facing markup, not just the source framework abstraction.' The 'when' is fully explicit with concrete phrases, but the 'what' is thin — it does not state what is validated (keyboard alternatives, ARIA attributes, live regions) — so it matches anchor 4 rather than anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'drag and drop', 'accessible', 'templates', 'rendered HTML', 'shared components', 'reviewing'. A few natural terms users would say are missing (e.g., 'ARIA', 'keyboard navigation', 'screen reader', 'sortable'), which matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (drag-and-drop accessibility of rendered markup) and triggers are specific to reviewing rendered output, so it is mostly distinct. Minor overlap risk exists with general HTML or accessibility review skills, matching anchor 4 rather than anchor 5.

4 / 5

Total

15

/

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/draggable-accessibility/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.