video-captions

Use when applies to all `<video>` elements and third-party video embeds (YouTube, Vimeo) where the page owner controls the content. Prerecorded videos require `.vtt` caption files via `<track>`. For videos embedded via `<iframe>`, check that the video platform captions are enabled. Audio-only content requires transcripts instead (SC 1.2.1). Video-only content (no audio) requires a text alternative or audio description instead (SC 1.2.3).

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

The body is well-structured and actionable, with a clean sequenced Check/Fix workflow containing explicit verification steps and an appropriately split one-level reference to rule.md. Its main weakness is conciseness: the captions-vs-subtitles distinction is redundant across sections and the intro leans on motivational framing Claude largely already knows.

Suggestions

Collapse the captions-vs-subtitles explanation into one location (keep it in Explain, drop the duplicate line in Quick Reference) to remove redundancy.

Trim the intro's motivational framing (beneficiary list, "essential", "legal compliance failure") to the specific facts Claude does not already know — the 15% statistic and the WCAG/ADA/EN 301 549 citations — leaving persuasion out.

Reword the "Use when applies to all `<video>` elements" trigger into a natural clause such as "Use when the page contains `<video>` elements or embedded YouTube/Vimeo videos."

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the captions-vs-subtitles distinction is restated across Quick Reference and Explain, and the intro paragraph is partly motivational ("essential", "legal compliance failure") covering benefits Claude largely already knows — fitting the "could be tightened" anchor rather than the every-token-earns-its-place level of 3.	2 / 3
Actionability	Provides concrete numbered Fix steps with a copy-paste `<track kind='captions' srclang='en' label='English' src='captions-en.vtt' default>` snippet and specific Check guidance; for an instruction-type skill this is actionable and copy-paste ready, not the vague/pseudocode profile of 2.	3 / 3
Workflow Clarity	The Check section is a sequenced checklist with explicit validation ("Verify the `default` attribute is present", "check that the `.vtt` file exists and is valid (not empty, not just music notes)") and Fix is numbered (1)–(4); checkpoints are explicit rather than the missing/implicit profile of 2.	3 / 3
Progressive Disclosure	Clear overview sections (Quick Reference, Check, Fix, Explain, Code Review) with a well-signaled one-level-deep pointer to `references/rule.md`, which exists and holds the full code examples — matching the clear-overview-with-one-level-references anchor rather than the inline-bloat or poorly-signaled profile of 2.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 is specific, trigger-rich, and distinctive, with an explicit "Use when" clause covering prerecorded, iframe-embedded, audio-only, and video-only cases. Its only weakness is the slightly malformed "Use when applies to all `<video>` elements" phrasing, which reads as a scope condition rather than a clean natural trigger.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to the domain — "require `.vtt` caption files via `<track>`", "check that the video platform captions are enabled", "requires transcripts instead", "requires a text alternative or audio description" — matching the multiple-specific-actions anchor rather than the partial coverage of 2.	3 / 3
Completeness	An explicit "Use when…" clause supplies the trigger and the body states what (caption requirements per scenario), so both what and when are explicit; the guideline caps completeness at 2 only when the trigger clause is missing, which it is not. It is not below 3 because both elements are clearly present, though the "Use when applies to…" phrasing is slightly awkward.	3 / 3
Trigger Term Quality	Covers natural terms a user would actually say — "video", "video embeds", "YouTube", "Vimeo", "captions", "transcripts" — giving good coverage rather than the missing-variations profile of 2.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (video-caption accessibility) with distinct `<video>`/YouTube/Vimeo/captions/transcripts triggers, making conflict with other skills unlikely; it is not the generic or overlapping profile of 2.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/video-captions/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.