mcpField
L
lemo-opuscar

lemo-opuscar

github.com/lemomo-aiCreative & media9.1k526 installsUpdated 4d ago
Repository

About lemo-opuscar

A creative-production skill that fetches the Lemo-Opuscar library and directs work through its guides and tools. It is for users creating films with the library's styles, from choosing or defining a style through production and delivery.

Key features

  1. 01Fetch or update the Lemo-Opuscar library
  2. 02Install core tools and optional dependencies
  3. 03Guide style selection or creation
  4. 04Support treatment, production, and delivery

Use cases

  1. 01Starting a film project with a library style
  2. 02Creating a custom style for a film
  3. 03Preparing and delivering a film project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lemomo-ai/lemo-opuscar --skill lemo-opuscar

After installing, type/lemo-opuscarin Claude Code to confirm it loaded.

Bundled filesscripts/setup.sh

Details

From the project README

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.

Comments

Markdown supported