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 is functional with a clear 'Use when' clause and distinct triggers tied to Remotion and a specific directory. Its main weakness is the lack of specific concrete actions beyond generic 'generating or modifying' — it would benefit from listing particular capabilities. Trigger term coverage could also be expanded to include more natural user language variations.
Suggestions
Add specific concrete actions such as 'create compositions, add animations, configure rendering settings, manage sequences' to improve specificity.
Expand trigger terms to include natural variations like 'React video', 'programmatic video', 'animation code', 'render video', or file extensions like '.tsx' that users might mention.
| 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/feedback loops in the pipeline workflow (especially important for video rendering which can fail in non-obvious ways) and the somewhat heavy inline content that could benefit from being split into referenced files for patterns and debugging.
Suggestions
Add explicit validation steps after video rendering (e.g., check file exists, verify duration/resolution with ffprobe, handle render failures with retry guidance)
Consider splitting 'Common Patterns' and 'Debugging' into separate referenced files to keep SKILL.md as a leaner overview
| 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 clear props schema, and specific error codes with resolutions. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The auto-generation flow lists steps clearly but lacks validation checkpoints—there's no explicit 'verify the output' step after rendering, no feedback loop for handling render failures, and the manual rendering section doesn't include verification of the output video. | 2 / 3 |
Progressive Disclosure | References external docs (Remotion docs, demo-video README, Local Run Proof README) at the end, but the main file is quite long (~180 lines of content) with patterns and debugging that could be split into separate files. The structure is reasonable but the inline content is heavy for an overview skill. | 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
83d60e9
- 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.