lemo-opuscar

Claude Code skill for short films with no video model: 43 film styles, each a style prompt plus a demo film made entirely in code by Claude Opus 5.5 (incl. OPUSCAR 98). By Lemomo. · Opus5.5 x 43 种影片风格:风格提示词 + 纯代码样片 + 导演与技术指南

Runssource: GitHubhomepageJavaScriptMITcommit e3cb16f63768

JavaScript, MIT licensed. The project labels itself: agent skills, ai agents, ai short film, ai video, animation, canvas, claude and claude code.

lemo-opuscar runs. An Argusic agent installed it in 0.8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Lemo-Opuscar film library installs and builds: npm packages (playwright-core, three), Python core venv (numpy, scipy, soundfile, soxr, pillow), Playwright chromium-headless-shell, Kokoro TTS voice model, and faster-whisper are installed. The pixel-rpg demo renders frames and full video, exports events, generates TTS voices passing ASR check, produces SRT subtitles and contact sheets.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.16 (measured)
recorded runs
1
last tested
stars
2,330
forks
247
open issues
0
watchers
2
size
120 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing lemo-opuscar, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • System Node.js is v18.19.1, project requires >=20. npm install fails without upgrade.0.5 minutes
Install time
under a minute
Cold machine to finish
32 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
node core/render/still.mjs produced 1920x1080 JPEG frames; node core/render/video.mjs produced 1308-frame H.264 24fps video (ffprobe confirms 1920x1080, 54.5s); ffmpeg -v error -f null - decode clean; node core/render/events.mjs exported 151 events; tts.py generated 5 voice WAVs; asr_check.py passed with 0 mismatches; srt.py generated valid subtitles; sheet.py produced contact sheet; sfx and sampler Python modules loaded and functioned
Model tokens used
389,446
Exact commit tested
e3cb16f63768
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    {
      "msg": "System Node.js is v18.19.1, project requires >=20. npm install fails without upgrade.…
      "fix": "Downloaded Node 20.18.3 to /tmp/node20 and added to PATH.",
      "minutes": 0.5
    }
  ],
  "test_depth": "tier1_real",
  "verified_how": "node core/render/still.mjs produced 1920x1080 JPEG frames; node core/render/vide…
  "final_state": "The Lemo-Opuscar film library installs and builds: npm packages (playwright-core,…
}
tokens used
389,446

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.8 minutes, faster than the median of the 59 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 60 agent-skills projects Argusic has installed and timed, lemo-opuscar was the 14th fastest to reach a running state, and 45 of 60 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.8 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.16

Topics (from GitHub)

agent-skillsai-agentsai-short-filmai-videoanimationcanvasclaudeclaude-codeclaude-code-pluginclaude-code-skillcreative-codingffmpegfilmmakingmotion-graphicsopus-5-5prompt-librarytext-to-speechthreejsvideo-productionwebgl

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/lemo-opuscar.svg)](https://argusic.com/subject/lemo-opuscar)

Questions

Does lemo-opuscar run?
Yes. lemo-opuscar runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test lemo-opuscar?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e3cb16f63768. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test lemo-opuscar?
The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does lemo-opuscar take to install?
0.8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does lemo-opuscar need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing lemo-opuscar?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does lemo-opuscar compare with the alternatives?
Of the 60 agent-skills projects Argusic has installed and timed, lemo-opuscar was the 14th fastest to reach a running state, and 45 of 60 reached one at all.
Where is the evidence for lemo-opuscar?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion