Skip to content
Back to skills

Lemo Opuscar

ASecurity

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 产品拆解, Microscope Story 显微叙事). Use when the user asks for a video, film, short, promo, explainer or animation (视频、短片、动画、宣传片) in a named style, including data, science and product explainers built from real material such as satellite imagery, laser scans, CAD files or archive scans ...

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentpythonnodegit

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Wanfeng1028/muse --skill lemo-opuscar --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lemo Opuscar?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lemo Opuscar
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wanfeng1028-lemo-opuscar-muse/badge)](https://www.skillsdirectory.com/skills/wanfeng1028-lemo-opuscar-muse)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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 产品拆解, Microscope Story 显微叙事). Use when the user asks for a video, film, short, promo, explainer or animation (视频、短片、动画、宣传片) in a named style, including data, science and product explainers built from real material such as satellite imagery, laser scans, CAD files or archive scans (数据解说、科普、产品拆解); when they want a film made about their own topic and haven't chosen a style (help them choose); when they want to change a style and keep it as their own (改风格、做自己的风格); or when they ask which film styles there are. Not for editing or converting existing video files.
---

# Lemo-Opuscar

The styles, guides and tools ship with this plugin, in `library/` next to this file. Nothing is downloaded to tell you what to do.

1. **Get the library ready.** Run `sh "<skill base directory>/scripts/setup.sh"`. It copies the bundled library to its working folder (default `~/.lemo-opuscar`, so installed packages survive plugin updates) 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: finding the style, 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`. `sh tools/setup.sh` and `sh tools/fetch.sh` also run from `$LIB` |
| 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 films | not in this edition: no `demo/` source and no `poster.jpg`. Each style's `DEMO.md` (how its demo was made) is there; read it only after your `TREATMENT.md` is written, as the guides say. The films are on the gallery, https://lemomo-ai.github.io/lemo-opuscar/, if the user wants to watch one |
| Chinese narration | Kokoro's Chinese voices (offline) by default. edge-tts (`core/tts/tts_zh.py`) sounds better but sends the narration text to Microsoft's speech service: offer it in your one round of questions and use it only if the user agrees |
| Big downloads | only what the film needs, from the sources `$LIB/TECHNIQUE.md` §1 lists (npm, PyPI, Playwright's browser, this library's GitHub Releases, Hugging Face for the speech check). Name them in your one round of questions the first time |

Deliver what `$LIB/DIRECTOR.md` §11 lists, in the project folder, and tell the user where it is.

Files in this skill

  • LICENSE1 KB
  • README.md26.4 KB
  • SKILL.md3.5 KB
  • library/AGENTS.md7.4 KB
  • library/DIRECTOR.md10.4 KB
  • library/MY-STYLES.md5.9 KB
  • library/TECHNIQUE.md12.8 KB
  • library/styles/_template/DEMO.md1.6 KB
  • library/styles/_template/STYLE.md4.7 KB
  • library/styles/archive-lighttable/DEMO.md10.9 KB
  • library/styles/archive-lighttable/STYLE.md13 KB
  • library/styles/art-deco/DEMO.md13.3 KB
  • library/styles/art-deco/STYLE.md11.9 KB
  • library/styles/ascii-crt/DEMO.md10.7 KB
  • library/styles/ascii-crt/STYLE.md11.9 KB
  • library/styles/backrooms/DEMO.md14.6 KB
  • library/styles/backrooms/STYLE.md12.3 KB
  • library/styles/blueprint/DEMO.md15.5 KB
  • library/styles/blueprint/STYLE.md12 KB
  • library/styles/brick-toy/DEMO.md6.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.