Lemo-Opuscar skill
Skill for Claude Code: the agent makes a short film entirely in code in a chosen style, with no video model or stock footage
- 15,152 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skill runs `setup.sh`: it clones the library from GitHub and installs dependencies on your machine
- The agent writes project files and runs frame-by-frame rendering locally
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/lemo-opuscarDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skill runs `setup.sh`: it clones the library from GitHub and installs dependencies on your machine
- The agent writes project files and runs frame-by-frame rendering locally
This is third-party code. Review the repository files before installing.
What it does
Lemo-Opuscar is a skill and a library of styles that let Claude Code make a short film entirely in code. You name a style, a topic and a tone ("a 45-second watercolor film about my family's coffee farm, warm female narrator"), and the agent works as director: writes the story, draws frames as canvas and WebGL pages, renders them frame by frame, scores music from free sample libraries and narrates with text-to-speech. The library covers many genres, including films built from real material: satellite imagery, laser scans, CAD files, archive footage and documents. Any style can be changed to your colors, logo and characters, or you can start from a blank page and save the result. The agent follows three guides: `DIRECTOR.md` for direction, `TECHNIQUE.md` for building, and `styles/<style>/STYLE.md` for look and sound.
Who it is for. For video makers, marketers and developers who want a short film in a recognizable style without manual editing.
Good fit when
- You want a short film in a chosen style, such as watercolor or ukiyo-e, about your project or family
- You want to explain data visually: turn satellite imagery, a laser scan or a CAD model into a film with sources named
- You want to cut a news piece from archive footage and documents
- You want your own style with brand colors, logo and characters
Not a fit when
- You need to edit, trim or convert existing video files: the skill is not for that
- You need photorealistic footage from a video model: everything here is drawn in code
- Node, ffmpeg and Python are missing and you will not install them yourself
Example request
Make a 45-second film in the watercolor style about the coffee farm my family runs, warm female narratorLimitations
The styles are tuned for Claude Opus 5.5, and other models may render them worse. On first run the skill clones the library to `~/lemo-opuscar` and installs core dependencies, which takes a few minutes. The agent does not install Node, ffmpeg or Python. For other agents, copy `plugin/skills/lemo-opuscar/` into their skills folder by hand. Last commit in October 2026.
How to disable. Remove the plugin with `claude plugin uninstall lemo-opuscar@lemolab`. The library in `~/lemo-opuscar` and the film folders stay on disk; delete them by hand.
FAQ
How do I install Lemo-Opuscar in Claude Code?
Run `claude plugin marketplace add lemomo-ai/lemo-opuscar`, then `claude plugin install lemo-opuscar@lemolab`. The skill is then available from any folder.
What will the skill ask before starting?
Once: anything unclear about the topic, whether you have your own voice, music or material, and whether you want a storyboard. With a storyboard the agent stops and shows key shots in the chosen style; without one it goes straight to the film.
How do I make my own style?
Run `/lemo-opuscar:lemo-opuscar` with no text and pick changing a library style or a blank page. You can also say it in one line, such as "I want to change the Ukiyo-e style into my own version".
Where do the project files go?
Each film goes in a `<name>/` folder where you started the agent. The library, guides and styles live in `~/lemo-opuscar`.
Does every film need voice and music?
No. They are separate steps, `deps voice` and `deps music`, only if the film needs them.
Discussion
No questions or reviews yet.
Related
SkillsA skill with 341 ready styles that Claude Code and Codex pick by code to turn an idea into code-driven animation and video
A Claude Code skill that builds motion graphics in code: 21 ready looks, five questions, three approval stills and an MP4 render.
A Claude Code skill for code-made video: it splits a clip into scenes and picks an engine for each, from Paper.js to Manim.
The Video by Reference skill learns style from a sample clip and builds an animated short from code with an original soundtrack
Two Claude Code skills for videos made entirely in code: hand-painted watercolour animation and kinetic typography reels
A skill for Claude Code and Codex: the agent writes animation scenes, a browser player shows them, export to MP4 and Lottie.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Lemo-Opuscar (this card) | no | 15,152 | |
| HyperFrames | no | 83,283 | builds videos from HTML compositions, while Lemo-Opuscar adds a library of directing styles and draws frames in code |
| Remotion Agent Skills | no | 6,903 | teaches the agent to make video in React, while this brings ready styles and directing guides |
README in short
A style library under MIT by the author Lemomo. The repository has a gallery and demo films, and the showcase project OPUSCAR 98 retells all 98 Best Picture winners in different styles.
README badge
Original SKILL.md
--- 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) 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. 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.