CtrlK
BlogDocsLog inGet started
Tessl Logo

launch-video

Plan and produce video and visual assets for product launches — demo videos, GIFs, screenshots, and programmatic video with Remotion. Use this skill whenever someone asks to create a demo video, record a product walkthrough, make a launch GIF, plan visual assets for a launch, or decide what media to create for an announcement. Also trigger for "what should our demo video show," "how do we record the product," "I need visuals for the launch," "make a video for this launch," or any request about creating non-text media tied to a product release. Covers video scripting, recording, programmatic video (Remotion), GIF creation, screenshot best practices, and per-platform format guidance.

90

Quality

88%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that excels across all dimensions. It provides specific concrete actions, includes abundant natural trigger terms (including quoted example phrases users might say), explicitly addresses both what the skill does and when to use it, and occupies a clear niche around video/visual asset creation for product launches. The description is comprehensive without being padded, and uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: demo videos, GIFs, screenshots, programmatic video with Remotion, video scripting, recording, GIF creation, screenshot best practices, and per-platform format guidance.

3 / 3

Completeness

Clearly answers both 'what' (plan and produce video/visual assets, demo videos, GIFs, screenshots, Remotion, scripting, recording, format guidance) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios and example phrases).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'demo video,' 'product walkthrough,' 'launch GIF,' 'visual assets,' 'what should our demo video show,' 'how do we record the product,' 'I need visuals for the launch,' 'make a video for this launch,' and 'non-text media tied to a product release.'

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to video and visual asset creation specifically for product launches, with distinct triggers like 'demo video,' 'Remotion,' 'launch GIF,' and 'non-text media tied to a product release' that are unlikely to conflict with general writing, design, or coding skills.

3 / 3

Total

12

/

12

Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill with excellent workflow clarity and concrete guidance including executable code, specific platform specs, and structured templates. Its main weakness is length — at ~300 lines with no bundle files for progressive disclosure, it consumes significant context window space. Some editorial tightening could remove unnecessary framing and explanatory text that Claude doesn't need.

Suggestions

Split detailed sections (Remotion patterns, platform video specs table, GIF optimization) into separate reference files and link from the main SKILL.md to reduce token footprint

Remove soft editorial commentary like 'A bad one can actively undermine the launch' and 'The platform hard limits aren't just technical' — Claude doesn't need persuasion, just instructions

DimensionReasoningScore

Conciseness

The skill is well-organized and mostly efficient, but includes some unnecessary explanatory framing (e.g., 'These are the highest-impact assets you'll create' and general advice Claude would already know like 'Bad audio is worse than no audio'). The media hierarchy rationale and voiceover vs. silent discussion could be tightened. However, the tables and checklists are efficient formats.

2 / 3

Actionability

The skill provides concrete, executable guidance throughout: specific bash commands for Remotion setup, copy-paste-ready TSX code patterns, exact platform specs in tables, specific tool recommendations, a scene planning template with defined fields, and a render command. The script structure with precise timing ranges is highly actionable.

3 / 3

Workflow Clarity

The Remotion iteration workflow is clearly sequenced (plan → collect → draft → preview → iterate → render → check specs) with an explicit preview/validation step and iteration loop. The script structure provides a clear beat-by-beat sequence. The asset checklists by tier provide clear completion criteria. The recording tips are well-ordered.

3 / 3

Progressive Disclosure

The content is well-structured with clear headers and sections, but it's a long monolithic document (~300 lines) with no references to external files for detailed content. The Remotion section, platform specs, and GIF optimization could be split into separate reference files. The companion skills section at the end hints at cross-references but no bundle files exist to support them.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
amplitude/builder-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.