Index of every page on this site: llms.txt
All skills
Run it yourself

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.

Recorded with Claude Code, Opus 5.5

Prompt

Make a 15-second film in the Chinese Ink Wash style about a lighthouse keeper on Wrenhollow, a fictional island, who rescues a paper boat from a storm. No narration. Render the final film as film.mp4 in this folder.

Recorded on an older version of this Skill.

Use this Skill: https://skilld.dev/gh/lemomo-ai/lemo-opuscar/lemo-opuscar

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈278 tokens for metadata: the name and description. ≈617 when used: this file.

Description uses 12.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈968 characters, or 12.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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), lists any missing system tools (Node, ffmpeg, Python) 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. A style marked ✦ also needs an image generator the user provides ($LIB/AGENTS.md, Workflow, Brief). 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 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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning8d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    The skill fetches and executes a style library from the vendor's GitHub repository. It also relies on instructions found within the downloaded library to guide the agent's behavior, which creates a surface for indirect prompt injection.

  • Socket8d

    No alerts

  • Snyk9d

    Risk: MEDIUM · 1 issue

Signed by skilld at f9e2042. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for lemomo-ai/lemo-opuscar