Verified Agent Skill record

manim-video · Video Use

A production pipeline for creating mathematical and technical animations using Manim Community Edition. It generates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories.

Tasks

Write a plan.md file with a narrative arc, scene list, visual elements, color palette, and voiceover script before coding any animation.
Write script.py with one class per scene, defining shared color constants and a monospace font at the top of the file.
Render scenes in draft mode using `manim -ql script.py` and iterate before running a final production render with `-qh`.
Stitch the rendered scene clips together into final.mp4 using ffmpeg concat, referencing an output directory like `media/videos/script/480p15/`.

Inputs

Topic or concept
Math expressions
Algorithm description
Data or metrics
System description
Research paper
3D concept

Outputs

Animated explanation with geometric intuition
Step-by-step animated proof
Step-by-step algorithm execution with data structures
Animated charts, comparisons, and counters
Architecture components building up with connections
Key research findings and methods animated
Rotating surfaces, parametric curves, and spatial geometry
Stitched final.mp4 video file

Limitations and checks

LaTeX is required only when rendering equations via MathTex; standard text, graphs, and geometric animations can render without a LaTeX distribution
The skill claims first-render excellence is non-negotiable and aims for visually clear output without revision rounds, though this is a subjective creative standard and not an objective guarantee of output quality
The optional TTS stack lists 'Qwen3-TTS', which may be an unverified model
Rendering is CPU-bound; production quality (-qh at 1920x1080 60fps) may take 30-120s per scene
Verify all LaTeX strings in MathTex objects use raw string literals (e.g., r"\frac{1}{2}").
Verify every animation sequence is followed by a `self.wait()` breathing room pause.
Verify all text uses a monospace font to avoid broken kerning with proportional fonts.
Confirm that every scene class ends with a clean FadeOut exit for all active mobjects.