Plan educational math and science videos scene-by-scene before implementing with Manim.
Works with
Conducts topic research and asks clarifying questions about audience, video length, depth, and style preferences to shape the narrative
Outputs a comprehensive scenes.md file specifying each scene's purpose, visual elements, animations, narration, and technical implementation notes
Applies 3Blue1Brown principles including progressive revelation, visual continuity, pacing variation, and mathematica
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmanim-composerExecute the skills CLI command in your project's root directory to begin installation:
Fetches manim-composer from adithya-s-k/manim_skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate manim-composer. Access via /manim-composer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
3
total installs
3
this week
724
GitHub stars
0
upvotes
Run in your terminal
3
installs
3
this week
724
stars
Research the topic deeply before asking questions
Identify the narrative hook
Ask targeted questions (not all at once - adapt based on responses):
Audience & Scope
Focus & Depth
Style Preferences
Output a comprehensive scenes.md file with this structure:
# [Video Title]
## Overview
- **Topic**: [Core concept]
- **Hook**: [Opening question/mystery]
- **Target Audience**: [Prerequisites]
- **Estimated Length**: [X minutes]
- **Key Insight**: [The "aha moment"]
## Narrative Arc
[2-3 sentences describing the journey from confusion to understanding]
---
## Scene 1: [Scene Name]
**Duration**: ~X seconds
**Purpose**: [What this scene accomplishes]
### Visual Elements
- [List of mobjects needed]
- [Animations to use]
- [Camera movements]
### Content
[Detailed description of what happens, what's shown, what's explained]
### Narration Notes
[Key points to convey, tone, pacing notes]
### Technical Notes
- [Specific Manim classes/methods to use]
- [Any tricky implementations to note]
---
## Scene 2: [Scene Name]
...
---
## Transitions & Flow
[Notes on how scenes connect, recurring visual motifs]
## Color Palette
- Primary: [color] - used for [purpose]
- Secondary: [color] - used for [purpose]
- Accent: [color] - used for [purpose]
- Background: [color]
## Mathematical Content
[List of equations, formulas, or mathematical objects that need to be rendered]
## Implementation Order
[Suggested order for implementing scenes, noting dependencies]
Apply these principles when composing scenes:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend manim-composer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: manim-composer is the kind of skill you can hand to a new teammate without a long onboarding doc.
manim-composer has been reliable in day-to-day use. Documentation quality is above average for community skills.
manim-composer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: manim-composer is focused, and the summary matches what you get after install.
manim-composer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: manim-composer is focused, and the summary matches what you get after install.
I recommend manim-composer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend manim-composer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: manim-composer is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 39