Manim Video
Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Manim Video when an AI agent needs a reusable SKILL.md workflow for this job: Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
When not to use it
Skip Manim Video when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/manim-video # Save SKILL.md to ~/.claude/skills/manim-video/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/manim-video/SKILL.md. For a shared project, commit the folder at .claude/skills/manim-video/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Manim Video skill for this task: Define the core visual thesis in one sentence. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Manim Video
Use Manim for technical explainers where motion, structure, and clarity matter more than photorealism.
## When to Activate
- the user wants a technical explainer animation - the concept is a graph, workflow, architecture, metric progression, or system diagram - the user wants a short product or launch explainer for X or a landing page - the visual should feel precise instead of generically cinematic
## Tool Requirements
- `manim` CLI for scene rendering - `ffmpeg` for post-processing if needed - `video-editing` for final assembly or polish - `remotion-video-creation` when the final package needs composited UI, captions, or additional motion layers
## Default Output
- short 16:9 MP4 - one thumbnail or poster frame - storyboard plus scene plan
## Workflow
1. Define the core visual thesis in one sentence. 2. Break the concept into 3 to 6 scenes. 3. Decide what each scene proves. 4. Write the scene outline before writing Manim code. 5. Render the smallest working version first. 6. Tighten typography, spacing, color, and pacing after the render works. 7. Hand off to the wider video stack only if it adds value.
## Scene Planning Rules
- each scene should prove one thing - avoid overstuffed diagrams - prefer progressive reveal over full-screen clutter - use motion to explain state change, not just to keep the screen busy - title cards should be short and loaded with meaning
## Network Graph Default
For social-graph and network-optimization explainers:
- show the current graph before showing the optimized graph - distinguish low-signal follow clutter from high-signal bridges - highlight warm-path nodes and target clusters - if useful, add a final scene showing the self-improvement lineage that informed the skill
## Render Conventions
- default to 16:9 landscape unless the user asks for vertical - start with a low-quality smoke test render - only push to higher quality after composition and timing are stable - export one clean thumbnail frame that reads at social size
## Reusable Starter
Use [assets/network_graph_scene.py](assets/network_graph_scene.py) as a starting point for network-graph explainers.
Example smoke test:
```bash manim -ql assets/network_graph_scene.py NetworkGraphExplainer ```
## Output Format
Return:
- core visual thesis - storyboard - scene outline - render plan - any follow-on polish recommendations
## Related Skills
- `video-editing` for final polish - `remotion-video-creation` for motion-heavy post-processing or compositing - `content-engine` when the animation is part of a broader launch
Intended uses
- Define the core visual thesis in one sentence.
- Break the concept into 3 to 6 scenes.
- Decide what each scene proves.
- Write the scene outline before writing Manim code.
- Render the smallest working version first.
- Tighten typography, spacing, color, and pacing after the render works.
- Hand off to the wider video stack only if it adds value.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.