Manim video
Skill goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/manim-video
23-agent AI development team for Claude Code, Cursor, and Gemini CLI. Multi-agent orchestration framework with strict TDD, sprint planning, 420+ skills, and automated QA/security/SEO audits. Stop vibe-coding — start shipping production-grade software.
npx -y skills add goharabbas321/zeoel-framework --skill manim-videoAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.8 KB, 571 tokens by cl100k_base, as published. Nobody here has run it
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
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
What ships with it: 1 file
2.8 KB alongside SKILL.md, 1 of them executable
assets/
- network_graph_scene.pyruns2.8 KB