video-production

Produce programmable videos with Remotion using scene planning, asset orchestration, and validation gates for automated, brand-consistent video content.

1.04x

Quality

58%

Does it follow best practices?

Impact

98%

1.04x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent-skills/video-production/SKILL.md

Quality

Discovery

40%

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 identifies a specific technology (Remotion) which provides good distinctiveness, but relies on abstract terminology rather than concrete actions users would request. The complete absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the technical jargon may not match natural user language.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Remotion', 'React video', 'programmatic video', 'automated video generation', or 'video rendering'

Replace abstract terms like 'asset orchestration' and 'validation gates' with concrete actions such as 'compose video scenes', 'add transitions', 'render to MP4'

Include natural user phrases and file types users might mention, such as 'video animation', 'motion graphics', or '.mp4 output'

Dimension	Reasoning	Score
Specificity	Names the domain (Remotion video production) and mentions some actions (scene planning, asset orchestration, validation gates), but these are somewhat abstract concepts rather than concrete user-facing actions like 'create video transitions' or 'add audio tracks'.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no trigger guidance at all.	1 / 3
Trigger Term Quality	Includes 'Remotion' and 'video' as relevant keywords, but misses common user terms like 'animation', 'React video', 'render video', 'video editing', or file extensions. 'Asset orchestration' and 'validation gates' are technical jargon users wouldn't naturally say.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Remotion' creates a clear niche that distinguishes this from general video editing or other video tools. Unlikely to conflict with other skills due to the framework-specific focus.	3 / 3
	Total	8 / 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 solid, actionable skill with clear workflows and executable code examples for Remotion video production. The main weaknesses are some unnecessary content (Multi-Agent Workflow section, inline metadata) and the monolithic structure that could benefit from splitting into overview + reference files. The core instructional content is well-organized with good validation checkpoints.

Suggestions

Remove or relocate the 'Multi-Agent Workflow' and 'Metadata' sections - these add little instructional value and belong elsewhere

Consider splitting detailed examples and troubleshooting into separate reference files (e.g., EXAMPLES.md, TROUBLESHOOTING.md) with clear links from the main skill

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary sections like 'Multi-Agent Workflow' with agent roles that add little value, and the metadata section with version/tags that belong in frontmatter. The core content is mostly lean but could be tightened.	2 / 3
Actionability	Provides fully executable code examples including TSX components, bash commands for rendering, and concrete YAML/markdown templates. The Remotion composition example is copy-paste ready with proper imports and structure.	3 / 3
Workflow Clarity	Clear 5-step workflow with explicit sequence (Define Spec → Outline Scenes → Prepare Assets → Implement → Render/QA). Includes validation checkpoints in Step 5 with a QA checklist before final render, and troubleshooting section for error recovery.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is inline in one file. The 'Related Skills' references are good, but the document is quite long (~200 lines) and could benefit from splitting detailed examples or the troubleshooting guide into separate files.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: supercent-io/skills-template
Commit: c033769

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.