CtrlK
BlogDocsLog inGet started
Tessl Logo

demo-video

Use when the user asks to create a demo video, product walkthrough, feature showcase, animated presentation, marketing video, or GIF from screenshots or scene descriptions. Orchestrates playwright, ffmpeg, and edge-tts MCPs to produce polished video content.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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 well-structured, concise skill body with clear sequencing, verification checkpoints, and clean one-level-deep progressive disclosure. The primary gap is actionability: the actual ffmpeg/playwright/edge-tts invocations are described at a high level rather than supplied as executable commands.

Suggestions

Add copy-paste-ready example commands for the build.sh pipeline (e.g. an ffmpeg concat-with-crossfade invocation and an edge-tts generation line) so the core tool orchestration is fully executable.

Tighten the opening motivational lines ('You are a video producer...') and drop the 'When to Use This Skill' section since its triggers already appear in the frontmatter description, reducing redundancy.

Add an explicit validate->fix->re-render feedback loop (e.g. if a Quality Checklist item fails, identify the failing scene, regenerate it, and re-composite) to push workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

Lean and efficient with no basic-concept padding (it never explains what playwright/ffmpeg/edge-tts are) and skill-specific guidance throughout; held just below the top anchor by a stylistic motivational opener and 'When to Use' triggers that partly restate the description.

4 / 5

Actionability

Provides concrete specs — file structure, 1920x1080 viewport, scene timings, voice names, hex colors, and an HTML scene layout in the reference — but the core pipeline steps ('ffmpeg concat with crossfade transitions') are described rather than given as copy-paste commands, leaving minor gaps.

4 / 5

Workflow Clarity

A clear four-step sequence with an explicit tool-availability verification plus fallbacks (step 1) and a Quality Checklist for output verification; falls short of the top anchor because there is no explicit validate->fix->re-render feedback loop.

4 / 5

Progressive Disclosure

Well-organized sections in the overview with a single verified one-level-deep reference (references/scene-design-system.md) that is clearly signaled and described by contents, splitting the detailed design system out of the main file.

5 / 5

Total

17

/

20

Passed

Description

86%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, well-formed description that explicitly covers both what the skill does and when to use it with natural, comprehensive trigger phrases. The main weakness is specificity: the orchestration is described as one composite action rather than a list of concrete steps.

DimensionReasoningScore

Specificity

Names the domain and specific tools ('playwright, ffmpeg, and edge-tts MCPs') but bundles them into a single high-level action ('produce polished video content') rather than enumerating multiple distinct actions, matching the anchor that names domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both: 'when' via a clear 'Use when the user asks to create...' clause with concrete trigger phrases, and 'what' via 'Orchestrates playwright, ffmpeg, and edge-tts MCPs to produce polished video content.'

5 / 5

Trigger Term Quality

Covers comprehensive natural synonyms a user would say — 'demo video, product walkthrough, feature showcase, animated presentation, marketing video, or GIF' plus 'screenshots or scene descriptions' — matching the anchor for full coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear video-production niche with distinct triggers and a specific tool set gives minimal conflict risk, but 'animated presentation' and the screenshot input create minor overlap with presentation/browser-automation skills, so it sits just below the top anchor.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.