lemo-opuscar
Skill6 starsChanged 45 days agoMITView on GitHub
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.
6 other projects use a version of this, 2 of them edited; 2 of 2 edited versions we compared changed its rules; 0 new projects in the last 4 weeks, against 2 the 4 before.
How people change it
2 of 2 edited versions changed its rules, and some changes recur.
Of the 2 edited versions we compared: 2 made changes of their own.
Rules people add
- Follow the library. Read
$LIB/AGENTS.mdand do what it says: finding the style, the one round of questions, the treatment, production and delivery.added by 2 of 2
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Cooling: 0 new projects took it in the last 4 weeks, 0× the 4 weeks before.thin data
Most recently taken up by
- ai-made-easy/ai-cartoon-video-skillsword for word, first seen Nov 15, 2026
- afawfawffaf/my-skillsedited, first seen Nov 8, 2026
- hamzzaqureshi/gravidextheir own version, first seen Nov 8, 2026
- F0rger123/claude-video-editing-god-modeword for word, first seen Nov 1, 2026
- Unclecheng-li/AI_Animationtheir own version, first seen Nov 1, 2026
- VisualxIntelligence/motion-tools-and-skillsedited, first seen Oct 11, 2026
Other versions6 projects use a version of this.
Word for word · 2
- ai-made-easy/ai-cartoon-video-skills★ 8100% same
- F0rger123/claude-video-editing-god-mode★ 1100% same
Edited · 2
- VisualxIntelligence/motion-tools-and-skills★ 988% same
- afawfawffaf/my-skills★ 088% same
Wrote their own version · 2
- Unclecheng-li/AI_Animation★ 1.7ksame name
- hamzzaqureshi/gravidex★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- kaizen-conceptSkill
- kaizen-exploreSkill
- kaizen-helpSkill
- kaizenSkill
- kaizen-bookSkill
- kaizen-deckSkill
- kaizen-gameSkill
- kaizen-videoSkill
- disk-cleanupSkill
- kaizen-computerSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Get the library: Run sh "<skill base directory>/scripts/setup.sh".
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.
- 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 printsLIB=<path>on its last line. - Install the core tools early. Start
sh "<skill base directory>/scripts/setup.sh" depsright away, in the background if you can: it takes a few minutes the first time. Adddeps voiceordeps musiclater, 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 (itsSTYLE.mdlists them) you install yourself, into the project folder. - Follow the library. Read
$LIB/AGENTS.mdand 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.
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.

