CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

69%

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.

A tight, well-structured audit-and-fix skill: concrete property lists, detection patterns, and an explicit validation tool in both the Check and Fix phases, with implementation detail correctly pushed to a single real reference file. Minor deductions for a duplicated benefit statement, no inline JSON-LD example, and no validation-failure recovery guidance.

DimensionReasoningScore

Conciseness

The body stays lean and assumes Claude's competence (no explanations of what JSON-LD or rich results are), but the rich-results benefit is stated twice — 'eligible for video-specific rich results and carousels in Google Search' in the intro and again as the Quick Reference bullet 'Valid VideoObject schema can earn video carousels and rich results' — a minor redundancy that could be trimmed.

4 / 5

Actionability

Guidance is concrete: exact properties ('name, description, thumbnailUrl, uploadDate'), formats ('ISO 8601 format', 'absolute URL to thumbnail image'), detection patterns ("<script type='application/ld+json'>" containing '"@type": "VideoObject"'), and a named validation tool ('Run through Google's Rich Results Test') — though no copy-paste JSON-LD example appears in the body itself (deferred to references/rule.md).

4 / 5

Workflow Clarity

The Check → Fix sequence is clear and validation is explicit in both phases ('Run through Google's Rich Results Test' / 'Validate with the Rich Results Test'), but there is no error-recovery guidance for failed validation, so it falls short of anchor 5's feedback loops.

4 / 5

Progressive Disclosure

The 45-line body is well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) and defers implementation detail to a clearly signaled, real, one-level-deep reference ('see references/rule.md' — verified to exist with no nested references inside it), an appropriate split for a skill this size.

5 / 5

Total

17

/

20

Passed

Description

47%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 gives explicit, multi-scenario trigger guidance with natural platform keywords, but omits any statement of what the skill does — the core action (adding VideoObject JSON-LD schema) appears nowhere, and the opener 'Use when applies to' is ungrammatical. It reads as half a description: strong 'when', missing 'what'.

Suggestions

Lead with the core action so the 'what' is explicit, e.g. 'Adds VideoObject JSON-LD structured data to pages with embedded video (YouTube, Vimeo, self-hosted) so they qualify for video rich results and carousels in Google Search.'

Add natural trigger synonyms users would actually say — 'video schema', 'VideoObject', 'rich results', 'JSON-LD' — to broaden keyword coverage.

Fix the ungrammatical opener 'Use when applies to any page...' by rewriting it as 'Use when a page embeds or hosts video content'.

DimensionReasoningScore

Specificity

The description names the domain concretely ('any page embedding or hosting video content (YouTube, Vimeo, self-hosted)') but lists zero actions — what the skill actually does (add VideoObject schema) never appears. It sits between anchor 1 (pure abstraction) and anchor 3 (1-2 concrete actions), best matching anchor 2's 'names the domain but actions are minimal'.

2 / 5

Completeness

Only the 'when' is present ('Use when applies to any page embedding or hosting video content... Use when adding video content to a site or auditing structured data coverage'); the 'what' — that the skill adds VideoObject JSON-LD schema — is entirely absent, exactly matching anchor 2's 'only when is present without what'. It is not 1 because the 'when' is explicit and multi-scenario, and not 3 because that anchor describes the opposite profile (a clear 'what' with a missing 'when').

2 / 5

Trigger Term Quality

Natural terms users would say are present — 'video content', 'YouTube', 'Vimeo', 'structured data' — but common variations such as 'video schema', 'VideoObject', or 'rich results' are missing, matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Video-specific triggers (YouTube, Vimeo, self-hosted video) form a clear niche with minimal conflict risk, but the broad clause 'auditing structured data coverage' overlaps with other schema/SEO audit skills — minor overlap risk that keeps it below anchor 5.

4 / 5

Total

12

/

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/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.