remotion
Use when generating or modifying Remotion video code, creating demo videos, or working with the demo-video/ directory
77
73%
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 terms could also be expanded to cover more natural user phrasings.
Suggestions
Add specific concrete actions such as 'create compositions, add animations, configure sequences, render video previews' to improve specificity.
Expand trigger terms to include natural variations like 'React video', 'programmatic video', 'animation code', 'render', or '.tsx video components'.
| 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
72%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 slightly verbose structure (the 'When This Skill Applies' section is unnecessary) and missing validation checkpoints in the pipeline workflow. The common patterns section and error codes table add genuine value.
Suggestions
Add explicit validation checkpoints to the Auto-Generation Flow (e.g., 'Verify RUN_CERTIFICATE.json exists and status is PASS before proceeding to render')
Remove the 'When This Skill Applies' section — this is metadata that belongs in frontmatter or can be inferred by Claude from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some unnecessary context like explaining when the skill applies (Claude can infer this) and the project structure listing could be more compact. The common patterns section is useful but adds length. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples throughout, 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 is listed as steps but lacks validation checkpoints between steps. Manual rendering commands are clear, but there's no explicit 'validate then proceed' feedback loop for the rendering pipeline. Debugging is listed separately rather than integrated as verification steps. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from rules to integration to debugging to patterns. References to external docs (Remotion docs, README files) are one level deep and clearly signaled. Content is appropriately organized for a skill of this complexity. | 3 / 3 |
Total | 10 / 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
f772de4
- 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.