manim-video
- Use it when:
- You want a short animated explainer of a graph, workflow, architecture or metric, rather than a talking-head video.
- It does:
- Writes a one-sentence visual thesis, splits it into 3 to 6 scenes that each prove one thing, then renders a low-quality test before polishing.
- You get:
- A 16:9 MP4, a thumbnail frame, a storyboard and scene plan, and polish suggestions.
- Needs:
- The manim CLI; FFmpeg only for post-processing.
- Works with:
- ECC's video-editing skill for final assembly or polish, only when it adds something.
Needs the manim CLI installed; FFmpeg too if you post-process. Its SKILL.md also hands compositing to ECC's remotion-video-creation skill, which SkillHub doesn't list.
TL;DR
Manim is a Python library for precise, diagram-style animation, and this skill uses it for explainers where structure and clarity matter more than realism. The agent states the core visual idea in one sentence, breaks it into 3 to 6 scenes, decides what each scene proves, and writes the scene outline before any Manim code. Scenes reveal progressively instead of filling the screen, use motion to show a change of state rather than to keep things busy, and keep title cards short. Rendering starts with a low-quality smoke test and moves to higher quality only once composition and timing hold; after that it tightens typography, spacing, color and pacing. Output defaults to 16:9 landscape unless you ask for vertical, with one thumbnail frame that reads at social-media size. For social-graph explainers it shows the current graph before the optimized one and separates low-signal clutter from high-signal bridges, and it points to a starter scene file in the skill's assets.
Summarizes the skill at d2ef268.
npx skills add https://github.com/affaan-m/ecc --skill manim-video More weekly downloads than 66% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 270 |
| Sep 28 | 166 |
| Oct 5 | 171 |
| Oct 12 | 258 |
| Oct 19 | 440 |
| Oct 26 | 439 |
| Nov 2 | 505 |
| Nov 9 | 499 |
Fewer downloads than 81% of skills
More stars than 97% of repos
Newer than 66% of skills
| Category |
Generate and edit video, images and audio. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics | |
| Stack |
SKILL.md
From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.
Frontmatter
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: ECCManim 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
manimCLI for scene renderingffmpegfor post-processing if neededvideo-editingfor final assembly or polishremotion-video-creationwhen 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
- 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.
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 as a starting point for network-graph explainers.
Example smoke test:
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-editingfor final polishremotion-video-creationfor motion-heavy post-processing or compositingcontent-enginewhen the animation is part of a broader launch