manimvox
AGENTS.md2 starsChanged 20 days agoMITView on GitHub
Guide for agents working on this repository. To use manimvox, load the manimvox skill instead. manimvox makes explainer videos with an AI agent doing the work: a person asks for a video, and an agent researches, scripts, animates (Manim), narrates (text-to-speech) and checks it. Agents are the primary users, so keep everything usable without a person present: no prompts without a terminal, one-line errors, consent asked for before any download. It is a Python package (MIT) with a manimvox command,…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- manimvox-animationSkill
- manimvox-blocksSkill
- manimvox-cliSkill
- manimvox-conceptSkill
- manimvox-coreSkill
- manimvox-creativeSkill
- manimvox-paperSkill
- manimvox-playlistSkill
- manimvox-prSkill
- manimvoxSkill
- manimvox-voiceSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 58
Never commit docs/specs or docs/plans.
- Very specific: line 63
Every version in the manifests equals manimvox.__version__.
- Distinctive: line 65
Use Conventional Commits. Run the tests and ruff before committing.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
Guide for agents working on this repository. To use manimvox, load the manimvox skill instead.
manimvox makes explainer videos with an AI agent doing the work: a person asks for a video, and an agent researches, scripts, animates (Manim), narrates (text-to-speech) and checks it. Agents are the primary users, so keep everything usable without a person present: no prompts without a terminal, one-line errors, consent asked for before any download. It is a Python package (MIT) with a manimvox command, and it ships agent skills in skills/.
For people contributing, CONTRIBUTING.md has the same rules; the documentation site is built from docs/ and zensical.toml.
Layout
src/manimvox/
cli.py the manimvox command
tools.py typed tools mirroring the CLI, for agents with no shell
integrations/ adapters for eight agent frameworks
confirm.py when a download may go ahead without asking
playlist.py index page and share packages
project.py series.json loading and validation
scaffold.py manimvox new
runner.py runs Manim in a subprocess
skills.py skill discovery, manifest generation
skills_admin.py manimvox skills install, check, update, remove
templates/ files manimvox new writes
kit/ Episode, components, theme, text (what episodes import)
scenes/ clips from Pillow, Cairo, Matplotlib, Plotly
post/ music bed, captions, cards, join
blocks.py block registry, manimvox add, the preview tool
_cairo.py pycairo helpers shared by scenes and post
checks/ theme, layout, audio, contact sheets
voice/ the voice interface, cache, downloads, HTTP, audio conversion
voice/engines/ one module per text-to-speech engine
examples/agents/ one script per framework
blocks/<name>/ block code, demo, block.json, preview.png
skills/<name>/ agent skills: SKILL.md plus references/
skills-manifest.json generated list of the skills
tests/Commands
uv sync --extra dev --extra kokoro
uv run pytest
uv run ruff check src tests examples
# framework adapters; CrewAI conflicts with the OpenAI Agents SDK, so it runs in its own environment
uv run --extra dev --extra agno --extra langchain --extra pydantic-ai --extra openai-agents --extra llamaindex --extra haystack --extra google-adk pytest tests/test_integrations.py tests/test_integrations_common.py tests/test_frameworks.py -q -rs
uv run --extra dev --extra crewai pytest tests/test_integrations.py tests/test_frameworks.py -q -rs -k "crewai or missing or every_framework"
uv run python -m manimvox.skills manifest --write # after any skill edit
uv run manimvox skills install|check|update|remove # skills in your coding agents
uv run python -m manimvox.blocks preview --write|--check [NAME] # after any block edit
uv run python -m manimvox.blocks docs && uv run --extra docs zensical build --strict # the docs siteTests that render with Manim are marked slow; tests needing real engines are opt-in markers.
Rules
- Never commit
docs/specsordocs/plans. They stay local. - Skills stay harness-neutral: shell commands and reading files only, no harness tool names, no private or competitor names.
tests/test_skills_lint.pyenforces this with its BANNED list. - Where a capability may be missing, a skill gives the plain fallback: helpers one after another; no way to ask means state the choice and continue; no image viewing means
manimvox check layout. - Consent rules live in the skills: ask before installing, downloading a model, fetching from the web or using an online voice; with no way to ask, the answer is no.
- A new CLI command gets a tool in
manimvox.toolswith the same behaviour, an entry inCOMMANDS, and a row in the manimvox-cli Tool column;tests/test_skills_lint.pyandtests/test_tools.pyenforce this. - Every version in the manifests equals
manimvox.__version__. npxinstalls run the pinnedSKILLS_CLIinskills_admin.py; bump it deliberately.- Use Conventional Commits. Run the tests and ruff before committing.
Skills
| Skill | Kind | For |
manimvox | router | picks the workflow, checks the setup |
manimvox-paper | workflow | one document into one video |
manimvox-playlist | workflow | a codebase or spec into a beginner-to-advanced series |
manimvox-concept | workflow | a concept with no source into one video |
manimvox-pr | workflow | a pull request into a short walkthrough |
manimvox-core | domain | the authoring contract for episode files |
manimvox-creative | domain | theme, story, narration, facts |
manimvox-animation | domain | motion patterns |
manimvox-voice | domain | engines, voices, pronunciation, cloning consent |
manimvox-cli | domain | commands and their output |
manimvox-blocks | domain | finding, copying and writing blocks |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

