PluginBench
Skill
Pass
Audit score 90

manim-video

affaan-m/ecc

Build animated technical explainers with Manim for graphs, diagrams, and system walkthroughs.

What is manim-video?

Manim Video creates clean, motion-driven animations for technical concepts, system architectures, and product explainers. Use it when you need precise, structured visuals that clarify complex ideas through progressive reveal and state-change animation rather than generic video production.

  • Render technical animations for graphs, workflows, and system diagrams
  • Plan scenes with clear visual thesis and progressive reveal structure
  • Generate 16:9 MP4 output with thumbnail and storyboard
  • Integrate with video-editing and remotion-video-creation for post-processing
  • Use network-graph starter templates for social-graph and optimization explainers

How to install manim-video

npx skills add null --skill manim-video
Prerequisites
  • manim CLI installed
  • ffmpeg for post-processing (optional)
  • video-editing skill for final assembly (optional)
  • remotion-video-creation skill for composited UI or captions (optional)
Claude Code
Cursor
Windsurf
Cline

How to use manim-video

  1. 1.Define the core visual thesis in one sentence
  2. 2.Break the concept into 3–6 scenes, each proving one thing
  3. 3.Write a scene outline before writing Manim code
  4. 4.Render a low-quality smoke test first to validate composition and timing
  5. 5.Tighten typography, spacing, color, and pacing after the render works
  6. 6.Export one clean thumbnail frame for social media
  7. 7.Hand off to video-editing or remotion-video-creation if additional polish is needed

Use cases

Good for
  • Create animated explainers for algorithm or data-structure concepts
  • Visualize system architecture or workflow state changes
  • Build product launch or landing-page explainer videos
  • Animate network graphs showing optimization or clustering
  • Produce technical documentation videos with motion-driven clarity
Who it's for
  • Technical writers and documentation teams
  • Product and engineering teams building explainers
  • Educators creating animated concept tutorials
  • Teams producing launch or marketing videos with technical depth

manim-video FAQ

When should I use Manim Video instead of a talking-head script?

Use Manim when the concept benefits from motion, structure, and visual precision—graphs, workflows, architecture diagrams, and state changes. Skip it if a static diagram or narrated slide deck is clearer.

What's the typical output?

A 16:9 MP4 video, one thumbnail or poster frame, a storyboard, and a scene plan.

Can I use this for network graphs?

Yes. The skill includes a network-graph starter template (assets/network_graph_scene.py) that shows current vs. optimized graphs, highlights warm-path nodes, and distinguishes signal from clutter.

Do I need to hand off to other skills?

Only if it adds value. Use video-editing for final polish or remotion-video-creation for composited UI, captions, or additional motion layers.

What's the recommended workflow?

Define thesis → outline scenes → write Manim code → smoke-test render → refine timing and visuals → export thumbnail → optionally hand off for post-processing.

Full instructions (SKILL.md)

Source of truth, from affaan-m/ecc.


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 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-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