CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

video-accessibility

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

Quality

75%

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

Quality

Content

71%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 well-structured, appropriately deferred body: the single reference is real and one level deep, and the Check/Fix guidance is concrete for an instruction-only skill. The main costs are token redundancy — the intro, 'Explain' section, and 'Quick Reference' repeat accessibility rationale and checks Claude already knows — and the absence of any inline markup example.

Suggestions

Cut or drastically shorten the intro sentence and 'Explain' section — the rationale for captions and audio descriptions is knowledge Claude already has and costs tokens twice (intro + Explain).

De-duplicate 'Quick Reference' against the 'Check' and 'Fix' sections, or merge it into a single checklist to remove the repeated bullets about captions, audio descriptions, transcripts, and autoplay.

Add a minimal inline HTML snippet (e.g. a video element with a track element for captions) so the most common fix is executable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is lean overall, but the intro sentence ('Videos without captions exclude deaf and hard-of-hearing users...') and the 'Explain' section restate accessibility concepts Claude already knows, and 'Quick Reference' largely duplicates the 'Check' and 'Fix' sections. This is more than 'minor instances' of over-explanation (anchor 4) but far from heavily padded (anchor 2), matching anchor 3.

3 / 5

Actionability

The 'Fix' section names specific HTML mechanisms ('Add track elements for captions and audio descriptions... disable autoplay, and ensure media controls are keyboard accessible with proper focus management') and the 'Check' section includes a concrete verification ('Confirm spacebar pauses video without scrolling the page'). As an instruction-only skill this guidance is mostly executable with minor gaps — no inline markup snippet — matching anchor 4 rather than 5's copy-paste-ready examples.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure gives a clear, simple-skill sequence, with the 'Check' list serving as a validation checkpoint before fixing. It matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5, since there is no explicit re-verify step after applying fixes.

4 / 5

Progressive Disclosure

The body is under 50 lines, organized into clear sections (Quick Reference, Check, Fix, Explain, Code Review), and defers full implementation details via a single, clearly signaled one-level-deep reference to 'references/rule.md' — verified to exist and to contain the complete HTML example. This matches the simple-skill case for anchor 5.

5 / 5

Total

16

/

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 solid description with an explicit 'Use when...' trigger, a clear validation focus, and mostly natural trigger terms. Its main weaknesses are limited action specificity and the awkwardly embedded rule title, which slightly muddies the 'what' and omits natural synonyms like 'subtitles' and 'transcripts'.

Suggestions

Rewrite 'related to Make videos accessible with captions' into a natural clause, e.g. 'related to video accessibility — captions, transcripts, and autoplay behavior', and enumerate concrete validation actions to lift specificity.

Add natural synonyms and file-type triggers users might say, such as 'subtitles', 'transcripts', 'track elements', or '.vtt files', to broaden trigger-term coverage.

Sharpen the 'what' with concrete capabilities, e.g. 'Validate that videos have accurate captions, audio descriptions, transcripts, keyboard-accessible pause controls, and no autoplay.'

DimensionReasoningScore

Specificity

The description names the domain (video accessibility in rendered markup) and two concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' — but coverage is not comprehensive. It matches anchor 3 (domain plus 1-2 concrete actions) rather than 4, since the reviewing targets are variations of one action rather than several distinct specific actions.

3 / 5

Completeness

Both parts are explicitly present: an explicit trigger clause ('Use when reviewing templates, rendered HTML, or shared components...') and a clear what ('Validate the final browser-facing markup, not just the source framework abstraction'). Not anchor 5 because the 'what' is blurred by the awkwardly inlined rule title 'related to Make videos accessible with captions' and lacks concrete, enumerated capability phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say: 'templates', 'rendered HTML', 'shared components', 'captions', and 'browser-facing markup'. Good keyword coverage, but missing common variations such as 'subtitles', 'transcripts', 'a11y', or file types like '.vtt', so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Video captions/accessibility markup validation is a clear niche with distinct triggers, giving minimal conflict risk. Minor overlap remains with sibling HTML-review skills that share the generic 'reviewing templates, rendered HTML, or shared components' phrasing, which matches anchor 4 rather than 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/video-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.