chatgpt-video-editing-skills
用 ChatGPT/Codex 安裝 AI 剪輯環境,並依八大步驟完成可驗證的短影音剪輯。
Runs with mockssource: GitHubShellMITcommit dc2f10ac4616
Shell, MIT licensed. The project labels itself: agent skills, elevenlabs, ffmpeg, hyperframes, traditional chinese and video editing.
chatgpt-video-editing-skills runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project installs, builds, and runs. Both skills installed. video-use cloned at ~/Developer/video-use with Python deps synced via uv. Source Han Sans TW Regular+Bold fonts present with valid OTTO magic bytes. video-use test suite passes 26/26. Render pipeline produces decodable preview.mp4 from a test EDL.
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 92 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.
- system Node.js v18 does not meet npx skills requirement (>=22.20.0)2 minutes
- ELEVENLABS_API_KEY not available2 minutes
- uv (Python package manager) not found1 minute
- loudnorm audio normalization failed on silent test video (I=-inf)1 minute
- transcribe refused silent track 0 (peak -inf dBFS)1 minute
- pip install failed due to externally-managed-environment
- Install time
- 3 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npx skills add installed 2 skills to ./.agents/skills/; uv run python3 -m unittest discover -s tests: 26/26 passed; ffmpeg -v error -i /tmp/edit/preview.mp4 -f null -: decode OK; mock Scribe returned 6 word-level timestamps; bash tests/validate_repo.sh: Repository contract checks passed
- Model tokens used
- 78,357
- Exact commit tested
- dc2f10ac4616
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `uv` missing → installed via Astral install script - No ElevenLabs API key → stood up a local mock Scribe v2 API server - EDL format mismatch → used `ranges` instead of `segments` key - Loudnorm failed on silent audio → used `--no-loudnorm` - Transcribe refused silent audio → generated test video with sine tone **Verification**: - `validate_repo.sh`: all repo contract checks passed - video-use unit tests: **26/26 passed** - Render pipeline: produced a decodable `preview.mp4` (h264+aac, 1920x1080) - Transcribe pipeline: successfully uploaded audio to mock, returned word-level timestamps - Fonts: Source Han Sans TW Regular+Bold with valid OTTO magic bytes The ARGUSIC_RESULT line has been printed above.
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
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 3 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 agent-skills projects Argusic has installed and timed, chatgpt-video-editing-skills was the 71st fastest to reach a running state, and 96 of 128 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Topics (from GitHub)
agent-skillselevenlabsffmpeghyperframestraditional-chinesevideo-editing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/chatgpt-video-editing-skills)Questions
- Does chatgpt-video-editing-skills run?
- chatgpt-video-editing-skills runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test chatgpt-video-editing-skills?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc2f10ac4616. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test chatgpt-video-editing-skills?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does chatgpt-video-editing-skills take to install?
- 3 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 chatgpt-video-editing-skills need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing chatgpt-video-editing-skills?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does chatgpt-video-editing-skills compare with the alternatives?
- Of the 128 agent-skills projects Argusic has installed and timed, chatgpt-video-editing-skills was the 71st fastest to reach a running state, and 96 of 128 reached one at all.
- Where is the evidence for chatgpt-video-editing-skills?
- 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.