qiaomu-cut-skill
乔木智能视频导演 Skill:素材治理、双语字幕、品牌包装与可复现渲染 | Agent-native video director with governed sourcing and verifiable rendering
Runssource: GitHubJavaScriptMITcommit 823feff5c1c1
JavaScript, MIT licensed. The project labels itself: agent skill, ai video, ffmpeg, nodejs, subtitles and video editing.
qiaomu-cut-skill runs. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
qiaomu-cut v0.5.0 installs with zero npm dependencies, doctor confirms ffmpeg 6.1.1 with full capability (libass, drawtext, overlay, loudnorm, sidechaincompress, xfade, libx264), all smoke tests and release checks pass, file narration renders to verified h264/AAC video, plan/workflow/list commands produce correct output; listenhub_smoke requires Node 20+ (env has 18.19.1), documented gap.
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
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- scripts/render_project.js had "- /filter_complex" typo (leading slash) and passed file path to -filter_complex instead of -filter_complex_script on two lines, causing ffmpeg to reject the argument15 minutes
- Install time
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm run release-check exited 0 (5/5 stages pass); node scripts/file_narration_smoke.js exited 0, emitted preview MP4 (h264/aac) verified via ffmpeg probe; node scripts/security_smoke.js exited 0 (39 checks); python3 scripts/validate_skill.py exited 0 (0 errors, 0 warnings); python3 scripts/trigger_eval.py exited 0 (16/16 cases pass); doctor --json reports all green
- Model tokens used
- 44,484
- Exact commit tested
- 823feff5c1c1
- 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.
### Error fixed `scripts/render_project.js` had `'-/filter_complex'` (typo with a leading slash) on two lines (1051… ### What was verified - **Doctor** — ffmpeg 6.1.1 with all capabilities (libass, drawtext, loudnorm, xfade, libx264) - **Release check** — 5/5 stages pass (vendor verify, typography, brand templates, sentence boundar… - **File narration smoke** — renders a verified h264/AAC preview video with provenance tracking - **Security smoke** — 39 checks pass - **Validation** — 0 errors, 0 warnings - **Trigger eval** — 16/16 case classifications correct - **Doctor/plan/workflow/list** — all CLI commands produce correct output ### Known gap `listenhub_smoke.js` requires Node.js 20+ (container runs 18.19.1). This is documented upstream and…
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.1 minutes, faster than the median of the 13 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 14 agent-skill projects Argusic has installed and timed, qiaomu-cut-skill was the 1st fastest to reach a running state, and 12 of 14 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.1 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/qiaomu-cut-skill)Questions
- Does qiaomu-cut-skill run?
- Yes. qiaomu-cut-skill runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test qiaomu-cut-skill?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 823feff5c1c1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test qiaomu-cut-skill?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does qiaomu-cut-skill take to install?
- 0.1 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 qiaomu-cut-skill need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing qiaomu-cut-skill?
- 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 qiaomu-cut-skill compare with the alternatives?
- Of the 14 agent-skill projects Argusic has installed and timed, qiaomu-cut-skill was the 1st fastest to reach a running state, and 12 of 14 reached one at all.
- Where is the evidence for qiaomu-cut-skill?
- 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.