CtrlK
BlogDocsLog inGet started
Tessl Logo

video

Use when applies to any page embedding or hosting video content (YouTube, Vimeo, self-hosted). Use when adding video content to a site or auditing structured data coverage.

59

Quality

68%

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/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 well-organized, actionable audit skill: concrete property- and tool-level guidance in the body with full code examples correctly placed one level deep in references/rule.md. The main gaps are minor redundancy in the property lists and an implied rather than explicit validation feedback loop.

Suggestions

State the required properties once (e.g. in Quick Reference) and reference them from Check/Fix to remove the triple repetition.

Make the validation feedback loop explicit, e.g. 'If the Rich Results Test reports errors, fix the flagged properties and re-run until it passes.'

Consider trimming the opening 'why it matters' sentence or moving it to rule.md, since the value of VideoObject rich results is context Claude already has.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the required property list is repeated across Quick Reference, Check, and Fix, and the opening 'why it matters' sentence is mild padding that could be trimmed.

2 / 3

Actionability

Concrete, specific guidance — exact selectors (<video>, YouTube iframes, Vimeo players), the JSON-LD type, named required properties with ISO 8601 format, and a named validation tool — with full code examples appropriately deferred to the reference; for an instruction/audit skill this is actionable without inline code.

3 / 3

Workflow Clarity

A validation checkpoint is present (Google's Rich Results Test in both Check and Fix), but there is no explicit validate→fix→retry feedback loop and the steps are presented as sections rather than a clearly numbered, sequenced workflow with checkpoints.

2 / 3

Progressive Disclosure

The body is a concise overview and signals a single one-level-deep reference (references/rule.md) — verified to exist and to hold the full code examples, property tables, exceptions, and verification steps — so content is appropriately split with easy navigation.

3 / 3

Total

10

/

12

Passed

Description

65%

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 strong, natural trigger terms and explicit 'when' guidance, but it never names the skill's core deliverable (VideoObject schema markup), leaving the 'what' only implied. Specificity and distinctiveness are moderate due to scenario-based phrasing and a broad audit clause.

Suggestions

Lead with the core capability, e.g. 'Adds VideoObject JSON-LD schema to pages embedding video' so the 'what' is explicit rather than implied.

Tighten the broad trigger 'auditing structured data coverage' to a video-specific scope (e.g. 'auditing video structured-data coverage') to reduce overlap with sibling SEO schema skills.

Keep the strong YouTube/Vimeo/self-hosted triggers but pair them with the concrete action verbs (add, validate) rather than only scenarios.

DimensionReasoningScore

Specificity

Names the domain (video, YouTube, Vimeo, self-hosted) and some actions (embedding/hosting, adding, auditing), but never states the core capability — adding VideoObject schema — so the actions read as scenarios rather than a comprehensive concrete capability list.

2 / 3

Completeness

The 'when' is answered explicitly via two 'Use when...' clauses, but the 'what' (the skill adds VideoObject structured-data markup) is never stated and is only implied through applicable scenarios.

2 / 3

Trigger Term Quality

Includes natural terms users would actually say — 'video content', 'YouTube', 'Vimeo', 'self-hosted' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The video-specific triggers are fairly distinct, but 'auditing structured data coverage' is broad and could overlap with sibling SEO / structured-data skills in the same checklist family.

2 / 3

Total

9

/

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.