remotion
Use when generating or modifying Remotion video code, creating demo videos, or working with the demo-video/ directory
75
70%
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
75%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 has a clear 'Use when...' clause and is distinctive enough to avoid conflicts with other skills, which are its main strengths. However, it could benefit from more specific capability listings beyond the generic 'generating or modifying' and from broader trigger term coverage to capture more natural user phrasings related to video creation with Remotion.
Suggestions
Add more specific concrete actions, e.g., 'Generates Remotion compositions, configures video sequences, adds animations and transitions, and renders demo videos'.
Include additional natural trigger terms users might say, such as 'animation', 'render video', 'React video', 'programmatic video', or 'video component'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Remotion video code, demo videos) and some actions (generating, modifying, creating), but doesn't list specific concrete capabilities like 'add animations', 'configure compositions', 'render sequences', etc. | 2 / 3 |
Completeness | Explicitly answers both 'what' (generating/modifying Remotion video code, creating demo videos) and 'when' with a clear 'Use when...' clause that specifies trigger conditions including working with the demo-video/ directory. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Remotion', 'video code', 'demo videos', and the directory path 'demo-video/', but misses common variations users might say such as 'animation', 'render', 'video generation', '.tsx', or 'React video'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Remotion', 'demo-video/ directory', and 'video code' creates a very distinct niche that is unlikely to conflict with other skills. The specific technology and directory reference make it clearly distinguishable. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%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 excellent executable code examples and clear critical rules. Its main weaknesses are the lack of validation checkpoints in the pipeline workflow (especially important since video rendering is a multi-step, potentially destructive process) and moderate verbosity that could be tightened by moving reference material like common patterns and error codes to separate files.
Suggestions
Add explicit validation checkpoints to the Auto-Generation Flow and Manual Rendering sections (e.g., 'Verify output file exists and is non-zero size', 'Preview first frame before full render')
Move the Common Patterns section and Error Codes table to separate reference files (e.g., PATTERNS.md, ERRORS.md) and link from the main skill to improve progressive disclosure
Remove the 'When This Skill Applies' section — the YAML description already covers this, and Claude can infer applicability from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some unnecessary context like the 'When This Skill Applies' section (Claude can infer this) and the project structure listing could be trimmed. The error codes table and some explanatory text add moderate bloat. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples for every pattern (fade in/out, staggered animation, spring), concrete CLI commands for rendering and debugging, a complete props schema, and specific error codes with resolutions. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The auto-generation flow lists clear steps 1-4, and manual rendering commands are specific. However, there are no validation checkpoints or feedback loops — e.g., no step to verify the rendered video is correct, no error recovery guidance in the pipeline flow, and the debugging section is separate from the workflow rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | References to external docs (Remotion docs, demo-video README, Local Run Proof README) are present and clearly signaled. However, the skill itself is quite long (~180 lines) with inline content (common patterns, error codes) that could be split into separate reference files. No bundle files are provided to verify referenced paths exist. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.