manim-video — Claude Code skill: what it does, how to install
Builds technical explainers in Manim for graphs, system diagrams, and product walkthroughs. Use it when motion should clarify the idea instead of a talking-head script.
npx skills add affaan-m/ECC --skill manim-video -a claude-codeWhat manim-video does
manim-video helps plan and build short technical explainers with Manim. It starts with a one-sentence visual thesis, breaks the concept into 3 to 6 scenes, and defines what each scene should prove. The workflow then moves to a scene outline, a low-quality smoke-test render, and adjustments to typography, spacing, color, and pacing.
The default package includes a 16:9 MP4, one thumbnail or poster frame, a storyboard, and a scene plan. Rendering requires the manim CLI. Use ffmpeg when post-processing is needed. The result can move to video-editing for final assembly or remotion-video-creation for composited UI, captions, and extra motion layers.
Install it when the explanation depends on graphs, motion, or structured diagrams. It is a poor fit for a generic talking-head script.
What it helps with
- build a technical explainer with animated scenes
- show how a graph or metric changes over time
- turn system architecture into a scene-by-scene outline
- prepare a short product or launch explainer for X or a landing page
Example prompts for the agent
- Build a Manim explainer for this service architecture and start with the storyboard.
- Show the current network graph, then the optimized graph, highlighting warm-path nodes and target clusters.
- Run a smoke test with `manim -ql assets/network_graph_scene.py NetworkGraphExplainer`, then suggest changes after the render.
How to install manim-video
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill manim-video -a claude-code2Manually: put the files in place
~/.claude/skills/manim-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/manim-video/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill manim-video -a codex2Manually: put the files in place
.agents/skills/manim-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill manim-video -a cursor2Manually: put the files in place
.cursor/skills/manim-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install affaan-m/ECC manim-video2Manually: put the files in place
.github/skills/manim-video/SKILL.md1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill manim-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/affaan-m/ECC --path skills/manim-videoManually: put the files in place
.devin/skills/manim-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill manim-video -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set146
The whole set →Similar
Questions about manim-video
How do I install manim-video in Claude Code?
Run npx skills add affaan-m/ECC --skill manim-video -a claude-code. The skill file will be placed at ~/.claude/skills/manim-video/SKILL.md.
What does manim-video do?
It plans and builds animated explainers for technical concepts, graphs, system diagrams, and product walkthroughs. Its output includes a visual thesis, storyboard, scene outline, and render plan.
What does manim-video require?
Rendering requires the manim CLI. Use ffmpeg for post-processing when needed; video-editing is available for final assembly.
Source text
SKILL.md · MIT
--- name: manim-video description: 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. metadata: origin: ECC --- # 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
© affaan-m · MIT · affaan-m/ECC