manim
Create and edit programmatic explanatory animations, videos, and GIFs with Manim Community Edition. Use for mathematical animation, algorithm animation, animated technical diagrams, or an explicit Manim request. Static diagrams, ordinary charts, and interactive web UI do not need this skill unless the user chooses Manim.
How do I install this agent skill?
npx skills add https://github.com/awesome-skills/manim-skill --skill manimIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The Manim skill is a well-documented and safe tool for creating programmatic animations. It includes comprehensive examples, research documentation, and utility scripts for rendering and verifying video output. A low-severity finding is noted for the inherent indirect prompt injection surface common to coding agents that process user-supplied descriptions into executable scripts.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Manim animations
Use Manim Community Edition (CE), not manimgl / manimlib, unless the user explicitly requests that engine. Preserve an existing project's engine and dependency constraints; migration is a separate choice.
This edition targets ManimCE 0.22.x, Python 3.11+. Check python --version and python -m manim --version in the project's environment before writing version-sensitive code. For an older project, read the matching official docs rather than silently upgrading it. See setup and migration for installation, optional math backends, output changes, and troubleshooting.
Workflow
- Establish the explanation: what changes over time, what the viewer should understand, and the requested output (video/GIF/still, duration, aspect ratio, language). Infer sensible defaults for unspecified presentation choices; ask only when the answer changes the work materially.
- Before coding a new animation or improving its appearance, read visual direction. Choose a focal object and sketch a short shot list: question, visible action, insight, timing. Make the changing geometry carry the explanation; use captions to support it. Use explicit labels as well as color to convey state. For object transfers, continuous plots, causal flows, timing choices or portrait composition, read the matching animation craft recipe. Choose palette/type and motion rules for this subject; keep a stable identity for each tracked item.
- Write a runnable scene in the user's project, keeping output media separate from source. Use public scene APIs. Configure resolution, renderer, and output before constructing a scene; use CLI flags or
tempconfigrather than changing global config aftersuper().__init__(). - Render a low-quality video first. Inspect opening, intermediate, and final frames, and review transitions for pacing and semantic correctness. Check essential labels at the intended display width, not only in enlarged frames. A last-frame PNG or a successful command alone does not verify an animation. Fix clipping, unreadable labels, overlaps, wrong states, and unexpected jumps before increasing quality.
- Render the requested artifact and verify it exists, decodes, and has the intended dimensions, duration, and format. Deliver the source path, artifact path, exact render command, environment version, and any verification limits. Do not claim visual acceptance when only syntax or rendering was checked.
For a blog embed, a short 16:9 MP4 is a reasonable starting point; GIF is useful when required but can be larger and less efficient. Follow the user's duration and style rather than imposing a fixed length or banning titles.
Small starting point
from manim import BLUE, Circle, Create, Scene, Text, VGroup, DOWN
class Explain(Scene):
def construct(self):
circle = Circle(color=BLUE)
label = Text("Input", font_size=32).next_to(circle, DOWN)
group = VGroup(circle, label)
self.play(Create(group))
self.wait(1)
Run from the environment containing Manim:
python -m manim render -ql scene.py Explain
python -m manim render -qh --format mp4 scene.py Explain
python -m manim render -qm --format gif scene.py Explain
python -m manim render -ql --format png scene.py Explain
-p opens the completed artifact; omit it in headless runs. --format png writes only the last frame. For all frames use png-sequence; --format none evaluates without producing media. --dry_run remains supported, but is not visual verification. Standard presets: -ql 480p15, -qm 720p30, -qh 1080p60, -qk 2160p60. See setup and migration for 0.22 output semantics.
Read only what the scene needs
| Need | Reference / runnable starting point |
|---|---|
| Composition, visual storytelling, choreography, appearance review | visual direction; examples/visual_story.py: VectorStory |
| Refined / beautiful / premium appearance | aesthetic refinement; examples/interference_study.py, examples/area_scale_story.py |
| Visual language, item transfers, continuous state, causal timing, portrait | animation recipes; merge_step.py, wave_superposition.py, packet_journey.py in examples/ |
| Labels, formulas, code, axes, graphs, layout | mobjects; examples/basic_scene.py |
| Easing choices and equal-time motion comparison | motion clock; examples/motion_timing.py |
| Transforms, timing, live values, object identity | animations |
| Camera-led focus, local/global comparison | camera-led explanation; examples/local_linearity.py |
| Continuous handoff between representations | visual anchor; examples/circle_to_wave.py |
| Multi-beat physical explanation | aesthetic refinement; examples/damping_story.py |
| Bézier construction, curve parameters and path speed | continuous state; examples/bezier_construction.py |
| Explanatory 3D, exploded views and camera-safe labels | 3D; examples/exploded_layers.py |
| Camera, 3D, updaters, programmatic rendering | advanced; examples/advanced_scene.py |
| Formula without a TeX installation, including labeled derivations | mobjects: math backends; examples/typst_scene.py, examples/typst_derivation.py |
| Records becoming counts / visible aggregation | animation recipes; examples/data_to_decision.py |
| Process, state, comparison, algorithm explanation | storytelling patterns; examples/flowchart.py, examples/state_diagram.py, examples/quicksort.py |
| Installation or older Manim code | setup and migration |
Reliability notes
- Text uses Pango and installed fonts. Check glyph coverage for the requested language; inspect rendered text for missing characters.
Textdoes not require TeX. Some convenience objects (including default numeric labels) do; chooseTextlabels when avoiding TeX. - In 0.22, formulas can use
Tex/MathTex(external TeX tools) orTypst/MathTypst(optionalmanim[typst]dependency). Typst math uses its own syntax, not LaTeX syntax. - Use
Code(code_string=..., language=..., formatter_style=...). Syntax and line-number colors come from Pygments, notparagraph_config["color"]. Transform(source, target)changes the source; keep animating the source variable.ReplacementTransformreplaces it with the target. Avoid two simultaneous animations mutating the same mobject.- Frame dimensions are scene units, distinct from output pixels. Fit the complete composition inside
config.frame_width/frame_heightwith margins, including arrowheads, labels, and motion extrema. Inspect portrait layouts separately. - Use Cairo for a portable starting point. OpenGL requires a functioning display/graphics environment and has different camera APIs; test it explicitly when requested.
Repository checks
For changes to this skill or its examples, follow the contributing checks. The smoke runner renders examples, probes media, and extracts contact sheets. Its report distinguishes skipped optional backends and rendering success from human visual review.
Official references: versioned 0.22 docs, changelog, source.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/awesome-skills/manim-skill/manim">View manim on skillZs</a>