Use when generating or modifying Remotion video code, creating demo videos, or working with the demo-video/ directory
80
Quality
78%
Does it follow best practices?
Impact
80%
1.50xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xaxiom/appfactory/remotion/SKILL.mdQuality
Discovery
57%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 effectively identifies when to use the skill with specific triggers (Remotion, demo-video directory) but fails to explain what the skill actually does. It's structured backwards - leading with 'Use when' without first establishing capabilities. The distinctiveness is strong due to the specific technology and directory references, but the lack of concrete actions limits its usefulness for skill selection.
Suggestions
Add a capabilities statement before the 'Use when' clause, e.g., 'Creates and edits Remotion video compositions, configures animations, and manages video rendering pipelines.'
Expand trigger terms to include natural variations like 'React video', 'programmatic video', 'animation code', or 'video rendering'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Remotion video code, demo videos) and mentions some actions (generating, modifying, creating), but lacks specific concrete actions like 'render compositions', 'add transitions', or 'configure frame rates'. | 2 / 3 |
Completeness | The description is structured as a 'Use when...' clause addressing when to use it, but lacks a clear 'what does this do' component explaining the actual capabilities. It tells when but not what actions the skill performs. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Remotion', 'video code', 'demo videos', and the specific directory path, but misses common variations users might say like 'animation', 'React video', 'video rendering', or 'motion graphics'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Remotion' (a specific framework), 'demo-video/' directory, and the combination of these terms creates a clear niche that is unlikely to conflict with other video or code-related skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It provides concrete, executable code examples without unnecessary explanation, maintains clear workflow sequences with validation steps, and organizes content progressively from project structure through critical rules to common patterns. The error codes table and debugging section add practical value for troubleshooting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Code examples are direct and purposeful, with no padding or unnecessary context about what Remotion is or how React works. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Commands are specific with actual flags and arguments. The props schema, error codes table, and debugging commands are all immediately usable. | 3 / 3 |
Workflow Clarity | The auto-generation flow is clearly sequenced (1-4 steps), manual rendering includes complete command examples, and the debugging section provides explicit validation steps. The pipeline integration section shows clear checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from structure to rules to patterns. References to external docs (Remotion docs, README files) are one level deep and clearly signaled at the end. Content is appropriately split between quick patterns and reference material. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
5342bca
Table of Contents
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.