lemo-opuscar — Claude Code skill: what it does, how to install
This Claude Code skill creates short films and animations in styles from the Lemo-Opuscar library. It handles films on a chosen topic, projects built from archival material, or requests to pick or create a style.
MIT 4,400 installs ★ 19,534 updated 2026-11-12
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a claude-codeWhat lemo-opuscar does
lemo-opuscar guides an agent through making a short film in code with the Lemo-Opuscar library. The agent can use a library style, adapt one, or develop a new style. Projects can draw on satellite imagery, laser scans, CAD files, and archival material.
The setup.sh script fetches the library and installs its core tools. Node, ffmpeg, and Python are required; the first dependency install takes a few minutes. Voice and music dependencies are added separately when a film calls for them. Styles marked ✦ also require an image generator supplied by the user. Packages listed in a style’s STYLE.md go into the project folder.
The agent reads $LIB/AGENTS.md, prepares a treatment, then produces and delivers the project files. This skill does not handle routine trimming, conversion, or editing of existing videos.
What it helps with
- create a short film about a chosen topic
- make a film from archival footage and documents
- choose a film style or develop a custom one
Example prompts for the agent
- Create a short film about a satellite launch in the Satellite Briefing style.
- Make a film from these archive scans and documents.
- Help me choose a style, then make a film about my project.
How to install lemo-opuscar
1Skills CLI (Vercel)
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a claude-code2Manually: put the files in place
~/.claude/skills/lemo-opuscar/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lemo-opuscar/
1Skills CLI (Vercel)
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a codex2Manually: put the files in place
.agents/skills/lemo-opuscar/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a cursor2Manually: put the files in place
.cursor/skills/lemo-opuscar/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lemomo-ai/lemo-opuscar plugin/skills/lemo-opuscar2Manually: put the files in place
.github/skills/lemo-opuscar/SKILL.md1Skills CLI (Vercel)
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a gemini-cli2Platform CLI
gemini skills install https://github.com/lemomo-ai/lemo-opuscar --path plugin/skills/lemo-opuscarManually: put the files in place
.devin/skills/lemo-opuscar/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about lemo-opuscar
How do I install lemo-opuscar in Claude Code?
Run npx skills add lemomo-ai/lemo-opuscar --skill lemo-opuscar -a claude-code. The skill file is placed at ~/.claude/skills/lemo-opuscar/SKILL.md.
What does lemo-opuscar do?
It guides an agent through producing a short film with the Lemo-Opuscar library. The workflow can use a library style, a custom variation, or real source material.
What does lemo-opuscar need to run?
It requires Node, ffmpeg, and Python. Styles marked ✦ need an image generator supplied by the user; voice and music dependencies are added when a film needs them.
Source text
SKILL.md · MIT
--- name: lemo-opuscar description: Direct and produce a short film made entirely in code, in one of the styles of the Lemo-Opuscar library (e.g. Impasto Oil Painting 油画厚涂, Watercolor Brush 水彩笔刷, Ukiyo-e 浮世绘, Satellite Briefing 卫星简报, Exploded Teardown 产品拆解). Use when the user asks for a video, film, short, promo, explainer or animation (视频、短片、动画、宣传片) in a named style, including explainers built from real material such as satellite imagery, laser scans, CAD files or archive scans (数据解说、科普、产品拆解), and new films cut from real archive footage and documents (剪辑纪实, e.g. 用档案影像剪一支新闻片); when they want a film about their own topic and haven't chosen a style (help them choose); when they want to change a style into their own, make their own style from a blank page, or use a style they saved (改风格、从空白开始、我的风格); when they start the skill without saying what they want; or when they ask which film styles there are. Not for plain editing, trimming or converting the user's existing video files. --- # Lemo-Opuscar The styles, guides and tools live in the Lemo-Opuscar library (github.com/lemomo-ai/lemo-opuscar). This skill fetches it and hands you over to it. 1. **Get the library.** Run `sh "<skill base directory>/scripts/setup.sh"`. It clones or updates the library (default `~/lemo-opuscar`; a clone the user is standing in is used as it is), lists any missing system tools (Node, ffmpeg, Python) and prints `LIB=<path>` on its last line. 2. **Install the core tools early.** Start `sh "<skill base directory>/scripts/setup.sh" deps` right away, in the background if you can: it takes a few minutes the first time. Add `deps voice` or `deps music` later, only if the film needs them (`$LIB/TECHNIQUE.md` §1). Report missing system tools (Node, ffmpeg, Python) in your one round of questions; don't install system software yourself. A style marked ✦ also needs an image generator the user provides (`$LIB/AGENTS.md`, Workflow, Brief). Packages a style needs (its `STYLE.md` lists them) you install yourself, into the project folder. 3. **Follow the library.** Read `$LIB/AGENTS.md` and do what it says, starting with **Start** (the user's own styles in `~/lemo-my-styles/`; when they started the skill without writing anything, the language question first, then the ways in): finding the style or making their own, the one round of questions, the treatment, production and delivery. What changes in skill mode: | | | |---|---| | Project folder | `<name>/` in the folder the user started from (lowercase letters, digits, hyphens; avoid `#` and `?` in the path). Wherever the guides say `films/<name>/`, read this folder | | Running tools | from `$LIB`, with the project's absolute path: `cd "$LIB" && node core/render/still.mjs "<project>" 1.5 3` | | Library files in pages | absolute URLs: `/core/lib.js`, `/node_modules/three/…` (the project is served at `/@film/`) | | Library files in scripts and `build.sh` | `$LIB/…`, with `LIB=<path>` at the top of `build.sh`; never `../..` | | Demo source | not downloaded. `sh "<skill base directory>/scripts/setup.sh" demo <slug>`, only after your `TREATMENT.md` is written, to read its techniques; it is not meant to be rendered. An Edit & Documentary style is the exception: fetch it before the treatment to use the material tools its `STYLE.md` names in `demo/tools/` (`$LIB/AGENTS.md`, "Treatment first") | Deliver what `$LIB/DIRECTOR.md` §11 lists, in the project folder, and tell the user where it is.
© lemomo-ai · MIT · lemomo-ai/lemo-opuscar