remotion-best-practices
Best practices for Remotion - Video creation in React
Install with Tessl CLI
npx tessl i github:tibelf/ai_project_init --skill remotion-best-practicesOverall
score
59%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too brief and vague to effectively guide skill selection. It identifies the technology (Remotion) but fails to specify concrete capabilities or provide any trigger conditions. The phrase 'best practices' is particularly unhelpful as it doesn't describe actionable functionality.
Suggestions
Add specific concrete actions like 'Create video compositions, render frames, add animations, configure audio tracks, and export videos programmatically'
Include a 'Use when...' clause with trigger terms such as 'Remotion', 'programmatic video', 'React video', 'video rendering', or 'video composition'
Expand trigger terms to include common user phrases like 'generate video', 'video from code', 'animated video', or 'render video'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'best practices' and 'video creation in React' without listing any concrete actions like rendering, composing scenes, adding animations, or exporting videos. | 1 / 3 |
Completeness | Only partially addresses 'what' (best practices for Remotion) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Remotion', 'Video', 'React') that users might naturally say, but misses common variations like 'programmatic video', 'video rendering', 'animation', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | 'Remotion' is a specific technology which helps distinguish it, but 'video creation in React' could overlap with other React media libraries or general video editing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as an index/navigation document for Remotion best practices, with excellent token efficiency and progressive disclosure. However, it lacks any quick-start examples or workflow guidance that would help users know where to begin or how to approach common Remotion tasks.
Suggestions
Add a 'Quick start' section with 1-2 minimal executable code examples showing basic Remotion patterns
Include a 'Common workflows' section that sequences related rules (e.g., 'For video with captions: see videos.md → transcribe-captions.md → display-captions.md')
Group the rule links by category (e.g., 'Media', 'Animation', 'Text', 'Advanced') to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - just a brief 'when to use' statement followed by a well-organized list of references. No unnecessary explanations of what Remotion is or how React works. | 3 / 3 |
Actionability | Provides clear navigation to detailed rule files, but the skill itself contains no executable code or concrete examples. Users must follow links to get actionable guidance. | 2 / 3 |
Workflow Clarity | The list is organized but lacks any guidance on which rules to read first, common workflows, or how different rules relate to each other. No sequencing for typical Remotion development tasks. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure - serves as a clear index/overview with one-level-deep references to specific rule files. Each link has a descriptive summary, making navigation easy. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.