本文へ移動
cccskills
無料GitHub で公開

lemo-opuscar

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); or when they ask which film styles there are. Not for editing or converting existing video files.

lemomo-ai/lemo-opuscar
インストール方法を見る

含まれるファイル（6）

  • SKILL.md3.4 KB
  • library-setup.sh3.8 KB
  • opuscar-trophy.png106.5 KB
  • README.md5.2 KB
  • SECURITY.md1.3 KB
  • setup.sh1.4 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 toolsfrom $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 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 filmsnot 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 narrationKokoro'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 downloadsonly 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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

このスキルの問題を報告する