AI TOOLS RADAR
All skills / LEMOMO-AI
lemomo-ai/lemo-opuscar

lemo-opuscar

Direct and produce a short film made entirely in code, in one of the styles of the Lemo-Opuscar library (e.g.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/lemomo-ai/lemo-opuscar --skill lemo-opuscar

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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 toolsfrom $LIB, with the project's absolute path: cd "$LIB" && node core/render/still.mjs "<project>" 1.5 3
Library files in pagesabsolute 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 sourcenot 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.