CtrlK
BlogDocsLog inGet started
Tessl Logo

audio-descriptions

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide audio descriptions for video. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

64

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/audio-descriptions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, well-organized checklist for a simple single-purpose rule: concrete detection criteria, the exact fix mechanism, and a clean hand-off to a verified one-level-deep reference holding the full code examples. Only a small redundancy between the intro and Explain sections keeps it from full marks on conciseness.

DimensionReasoningScore

Conciseness

Lean, checklist-style sections with no tutorials on concepts Claude already knows; only minor trimmable redundancy — the intro line 'Blind users miss critical plot points...' duplicates the Explain section's content.

4 / 5

Actionability

Names the exact mechanism ('Use track element with kind=descriptions'), concrete detection criteria (actions, expressions, scene changes, on-screen text), and fallback options (extended version, narration integration), with full code appropriately delegated to references/rule.md. Per the instruction-skill note, missing inline code is not penalized since the guidance is actionable.

4 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous Check -> Fix -> Explain -> Code Review sequence; verification is explicitly addressed ('note how to verify the fix with browser accessibility tooling or assistive tech'), and no destructive or batch operations apply the validation cap.

5 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a single clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle and contains the full code examples.

5 / 5

Total

18

/

20

Passed

Description

71%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 has an explicit trigger clause and several concrete review actions, but the actions are generic accessibility-review boilerplate rather than audio-description-specific capabilities, weakening both the 'what' answer and distinctiveness from sibling a11y skills. Adding the skill's actual mechanism (description tracks via kind='descriptions') and natural synonyms would raise specificity, completeness, and trigger quality.

Suggestions

State the skill's actual capability in the 'what' clause, e.g. 'Add and verify audio description tracks for video using the track element with kind=descriptions, including extended-description versions when dialogue gaps are too short'.

Include natural trigger synonyms such as 'described video', 'audio description track', '.vtt', and 'captions vs descriptions' so users' phrasings match.

Lead with the audio-description-specific trigger instead of the shared 'reviewing rendered HTML / keyboard behavior / focus flow' template to reduce overlap with sibling accessibility-review skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), matching the minor-gaps anchor rather than comprehensive coverage: no action mentions the skill's actual mechanism (track element with kind='descriptions', VTT description files).

4 / 5

Completeness

An explicit 'Use when...' clause covers 'when', and concrete review actions cover 'what', but the 'what' describes generic accessibility-review steps and never states what the skill does for audio descriptions specifically, so it falls short of the clearly-both-explicit anchor.

4 / 5

Trigger Term Quality

Natural phrases like 'audio descriptions for video', 'keyboard behavior', 'focus flow', and 'screen-reader output' give good coverage, but common variations users might say ('described video', 'description track', '.vtt') are missing.

4 / 5

Distinctiveness Conflict Risk

'related to Provide audio descriptions for video' pins the niche, but the surrounding HTML-review boilerplate ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') is shared by sibling accessibility skills, creating real overlap risk with closely related skills.

3 / 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
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.