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.

56

Quality

65%

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

78%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 content is well-structured, actionable, and appropriately splits detail into references/rule.md with a clear overview. Tightening the intro and adding an explicit validate-and-retry loop in Fix would push it higher.

DimensionReasoningScore

Conciseness

The body is mostly lean bullets and concrete property lists, with only the opening motivational paragraph ('Pages with valid VideoObject schema are eligible for video-specific rich results...') adding explanation Claude largely already knows.

4 / 5

Actionability

Check and Fix give concrete, executable guidance (find <video>/iframes, look for the JSON-LD block, populate name/description/thumbnailUrl/uploadDate, run the Rich Results Test), though no inline code example is provided — code is deferred to references/rule.md.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with an explicit validation checkpoint (Google's Rich Results Test) in both Check and Fix, but the Fix step does not spell out the retry-on-failure loop explicitly.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) with a single clearly signaled one-level-deep reference to references/rule.md, which exists as a real file — easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

52%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 strong trigger guidance and reasonable keyword coverage, but it fails to state what the skill actually does, leaving the 'what' entirely implicit. Rewording to lead with the concrete action ('Add VideoObject JSON-LD schema to video pages') would lift both specificity and completeness.

Suggestions

Lead the description with the core action, e.g. 'Add VideoObject JSON-LD schema to pages with embedded video.'

Combine the two repetitive 'Use when' clauses into one and add explicit trigger phrases like 'video schema' or 'rich results for video'.

Drop the grammatically awkward 'Use when applies to' phrasing in favor of third-person voice ('Use when adding...').

DimensionReasoningScore

Specificity

Names the domain ('page embedding or hosting video content (YouTube, Vimeo, self-hosted)') and a couple of concrete actions ('adding video content', 'auditing structured data coverage'), but never states the core action — adding VideoObject schema — so coverage is incomplete.

3 / 5

Completeness

Two explicit 'Use when...' clauses give a clear 'when', but the 'what' is absent — nothing in the description tells Claude the skill adds VideoObject JSON-LD schema, matching the 'only when present without what' anchor.

2 / 5

Trigger Term Quality

Good coverage of natural terms users would say — 'video content', 'YouTube', 'Vimeo', 'self-hosted', 'structured data coverage', 'auditing' — though it misses common phrasings like 'video schema' or 'VideoObject'.

4 / 5

Distinctiveness Conflict Risk

The video + structured-data/SEO niche with named providers (YouTube, Vimeo) is mostly distinct, though the broad 'adding video content to a site' phrasing creates minor overlap with general media-embedding skills.

4 / 5

Total

13

/

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.

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.