CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

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

Quality

Content

72%

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

A compact, well-organized review skill that correctly keeps detail in a single one-level reference, but the SKILL.md body offers checklist-style direction without an explicit validation loop or any in-body executable example. Moving a minimal markup snippet and a validate-fix checkpoint inline would raise actionability and workflow clarity.

Suggestions

Add a small in-body example (e.g. a minimal <video> with <track kind="captions">) so the core fix is copy-paste ready without opening the reference.

Turn the Check/Fix sections into an explicit validate-then-fix loop with a clear checkpoint (e.g. "Verify captions render and spacebar pauses before approving the markup").

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, opening only with a one-line rationale and keeping each section to tight bullet/checklist form with no padding.

3 / 3

Actionability

Guidance is concrete ("Add track elements", "Confirm spacebar pauses video") but the body itself contains no executable code or markup examples, deferring all copy-paste-ready content to the reference.

2 / 3

Workflow Clarity

The Check/Fix/Explain sequence gives a review flow, but it is a flat checklist with no explicit validate-then-fix feedback loop or checkpoint in the body.

2 / 3

Progressive Disclosure

The body is a clean overview with a single clearly-signaled one-level reference to references/rule.md, which exists, keeping detail out of SKILL.md as intended.

3 / 3

Total

10

/

12

Passed

Description

85%

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 and concrete, distinct scope, but its phrasing is grammatically awkward ("related to Make videos accessible with captions") and its trigger terms skew technical. Tightening the wording and adding natural keywords (captions, transcripts, autoplay) would lift it.

Suggestions

Reword the spliced phrase "related to Make videos accessible with captions" so the rule title reads as a natural clause rather than a pasted heading.

Add natural user-facing trigger terms such as "captions", "transcripts", "audio descriptions", or "autoplay" so the description matches how users actually ask for this.

DimensionReasoningScore

Specificity

It names concrete artifacts ("templates, rendered HTML, or shared components") and concrete actions ("reviewing", "Validate the final browser-facing markup"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

An explicit "Use when..." clause supplies the trigger and the second sentence states what to do (validate rendered markup), answering both what and when.

3 / 3

Trigger Term Quality

"templates, rendered HTML, or shared components" are natural-ish terms, but coverage leans technical ("source framework abstraction") and misses common user phrasings like captions, transcripts, or autoplay.

2 / 3

Distinctiveness Conflict Risk

Scoped to video-caption accessibility within templates/rendered HTML/shared components, a clear niche with triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.