CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

video

When the user wants to create video with AI tools or code, or asks which approach to use (screen recording, AI avatar, generated, or templated) or how to make videos repeatably: product demos, AI generation (Veo, Sora, HeyGen), programmatic video with Remotion. For what to post, see social. For video ads, see ad-creative.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/video/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, highly actionable overview with real reference files and strong executable examples for the programmatic paths. The main weaknesses are missing validation/verification steps in the batch and render workflows (which the rubric caps) and detailed or time-sensitive content inlined in an already long body.

Suggestions

Add explicit validation checkpoints to the render/batch workflows (e.g., after Batch Social Clips rendering, verify aspect ratio, captions, and playback on a sample before scheduling) so batch operations include feedback loops.

Include one concrete HeyGen MCP invocation and one Veo/Runway API call example so the avatar and generation paths match the executable quality of the Remotion/Hyperframes sections.

Move time-sensitive pricing and model-comparison tables into a reference file (keeping the 'check current pricing' pointers inline) to reduce body length and staleness risk.

DimensionReasoningScore

Conciseness

Largely efficient — dense decision tables, copy-paste commands, and tool knowledge Claude doesn't reliably have, with appropriate 'check current pricing/docs' hedges. Not 5 because time-sensitive details (HeyGen plan tiers, '$12-76/mo', the dated October 2026 attribution) sit inline rather than being trimmed or isolated.

4 / 5

Actionability

Executable bash commands ('npx hyperframes init my-video', 'npx create-video@latest'), a complete Remotion component, and a concrete prompting formula with a worked example. Not 5 because the avatar and video-model-API paths give no concrete invocation example, delegating entirely to external links.

4 / 5

Workflow Clarity

Workflows are clearly sequenced (Product Demo 6 steps, Explainer 5 steps, Repurposing pipeline), but validation checkpoints are largely absent — notably the Batch Social Clips render pipeline has no verify step, and the rubric caps batch operations without feedback loops at 3. The per-account pipeline's 'Automated QA' step is the exception, not the pattern.

3 / 5

Progressive Disclosure

All four body references (ai-video-prompting.md, edit-anatomy.md, product-demo-recording.md, code-rendered-product-films.md) resolve to real files, are clearly signaled, and are one level deep. Not 5 because the ~340-line body inlines detailed content (the per-account film pipeline, pricing/model tables) that parallels topics given their own reference files.

4 / 5

Total

15

/

20

Passed

Description

78%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.

A strong description with explicit, natural trigger phrasing, concrete tool and use-case coverage, and unusually good boundary delegation to sibling skills. The main gap is that the 'what' is expressed as a topic list rather than an explicit capability statement, and a few natural trigger synonyms are missing.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'screen recording, AI avatar, generated, or templated', 'product demos, AI generation (Veo, Sora, HeyGen), programmatic video with Remotion' — with only minor gaps. Not 5 because capabilities are named as topics/tools rather than explicit actions, and not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The 'when' is explicit and multi-clause ('When the user wants to create video with AI tools or code, or asks which approach to use... or how to make videos repeatably'), and the 'what' is conveyed via the topic list after the colon. Not 5 because the 'what' is never stated as an explicit capability (e.g., 'Creates/produces...'), and not 3 because the trigger guidance is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage users would actually say: 'create video', 'product demos', 'how to make videos repeatably', plus tool names (Veo, Sora, HeyGen, Remotion). Not 5 because a few common natural phrases like 'explainer', 'social clips', or 'talking head' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (video production) with concrete triggers and explicit boundary delegation — 'For what to post, see social. For video ads, see ad-creative.' — minimizing conflict with adjacent skills. Fits the anchor for clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

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.