anbeime/skill / skills/lemo-opuscar/lemo-opuscar
lemo-opuscar
VerifiedDirect 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.
- 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |