gooseworks-ai/review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates set_final_render — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), drops an approved phrase, or comes back silent. Runnable, gating counterpart to content-goose's review-transcript-integrity atom. Every ugc-video-formats recipe runs this after render and BEFORE set_final_render.
npx skills add https://github.com/gooseworks-ai/goose-skills --skill review-ugc-render
> The QC gate every UGC video recipe MUST clear before it publishes. Not an
> eyeball /watch — a deterministic transcript-vs-script diff that exits non-zero
> on a defect so the recipe can hard-stop set_final_render.
Seedance generates the audio natively. It sometimes mis-voices a word — the
approved line human-vetted comes back spoken as human witted; documented
siblings: Hume→Hune, Alitu→al-too. The defect lives in the render's
audio, so an eyeball /watch ("dialogue matches the script") slips it through,
and a downstream caption pass then bakes the wrong word in verbatim. Nothing was
comparing the actual spoken audio against the script the user approved.
This gate does exactly that, deterministically, and refuses to publish on a miss.
remix-ugc-*-from-sample and create-ugc-*-video-from-refsrecipe, in the QC phase, after the master render exists and before
set_final_render.
Before rendering, persist the exact approved spoken lines (the verbatim utterance,
no beat notes) to working/approved-script.txt. Then, after render:
python3 <pack>/review-ugc-render/scripts/review_render.py \
--video working/final.mp4 \
--script-file working/approved-script.txt \
--json working/review-verdict.json
set_final_render).not publish blind.
Transcription backend (in priority order): OPENAI_API_KEY (honors
OPENAI_BASE_URL, so it routes through the gooseworks Whisper proxy when set) →
local whisper CLI. ffmpeg must be on PATH.
| Report line | Root cause | Fix |
|---|---|---|
| [high] said [witted] where script has [vetted] | Seedance mis-voiced the word in the generated audio | Re-roll a new seed. If it is a brand/coined token, spell it phonetically in the SPOKEN LINE (e.g. Ali-too, never a (pronounced …) parenthetical — Seedance reads parentheticals aloud). See create-video-seedance-2-fal Failure Modes. |
| [medium] dropped [...] / low similarity | Seedance dropped an approved phrase | Re-roll; if only a tail word, a surgical stitch_replacement.py window fix may recover it. |
| ⚠ audio is effectively silent | Wrong render / audio track lost in post | Re-render / re-check the mux; never publish a silent take. |
| ERROR: no transcription backend | No OPENAI_API_KEY and no local whisper | Set the key (proxy OPENAI_BASE_URL) or install whisper, then re-run. |
--expect-music is advisory only (warns if a music bed is absent); it does not by
itself fail the gate.
--video PATH (required) — the rendered master mp4.--script-file PATH or --script "text" — the approved spoken script. Omitboth only for a genuinely script-free clip (the drift check is then skipped and
the gate is advisory).
--min-ratio FLOAT (default 0.90) — transcript↔script token similarity to pass.--json PATH — write the machine verdict for the app's review panel.python3 tests/test_review_render.py # pure verdict logic; no audio/network
Covers the canonical vetted→witted mis-voicing, brand-name mis-voicing, dropped
tails, benign filler, and the no-script advisory path.
This is the shipped, single-file, gating slice of the fuller
coworkers/video/molecules/review/review-loop (18-axis rubric). Here we enforce
the one axis that catches audio-vs-script defects at publish time
(review-transcript-integrity / brand_text_accuracy). Deeper multi-axis review
stays in the content-goose lab.
Take gooseworks-ai/review-ugc-render from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.