Skip to content
cccskills
FreePublished on GitHub

review-ugc-render

Checks a rendered UGC video's speech against the approved script using Whisper transcription. It flags changed numbers, brand names, negations, missing phrases, or silence, while allowing equivalent spoken forms such as digits read as words.

OriginalShow the original description

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 keeping the render as the final version (video_review) — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), says a different number or brand name, flips a negation, drops an approved phrase, or comes back silent. Correct speech written differently ("5mg" said "five milligrams", "30%" said "thirty percent", a spoken URL, "don't" said "do not", "larkfieldstraps" said "larkfield straps", a confirmed pronunciation like "TG1" said "T G one") passes. Runnable, gating counterpart to GooseWorks' fuller transcript-integrity review. Every ugc-video-formats recipe runs this after render and BEFORE keeping the final version.

gooseworks-ai/goose-skills1,272 stars(GitHub 1,272 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Check a UGC render before approving its final version
  • Catch spoken numbers or brand names that differ from the script
  • Verify approved dialogue after a video rerender

Files included (4)

  • SKILL.md13.5 KB
  • scripts/review_render.py51.2 KB
  • skill.meta.json197 B
  • tests/test_review_render.py30.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Superseded: the video kit now does this with the check-layer part, version 1.2.0, in the parts folder of this repository. It runs the same speech-against-script rules on every video with speech: numbers, units, negations and brand names must match, and confirmed pronunciations count as the written name. This atom stays, unchanged in behaviour, for skills outside the kit until they move; its scripts still run.

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 keeping the render as the final version (video_review).

In short: it compares what the render actually SAYS with the script the user approved. Correct speech that is only written differently passes (numbers, units, URLs, contractions, fused brand names, confirmed pronunciations). A wrong number, a flipped negation, a mis-voiced word or brand, a dropped phrase or silence fails.

Why this exists

Seedance generates the audio natively. It sometimes mis-voices a word — the approved line human-vetted comes back spoken as human witted; documented siblings: Brume→Brune, Avitu→av-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.

When to run

  • MANDATORY in every remix-ugc-*-from-sample and create-ugc-*-video-from-refs recipe, in the QC phase, after the master render exists and before keeping it as the final version (video_review).
  • Re-run after every fix / re-roll until it PASSES.

Contract

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

When the voice-over used confirmed pronunciations, add them (recommended): --pronunciations working/brand-rules.json — the same file create-vo-elevenlabs read (its --rules brand-rules.json, or the read_pronunciations.py output; both carry a pronunciations: [{term, say_as}] list). Leave the flag out when there is no such file: a missing file is an ERROR (exit 3).

  • exit 0 → PASS — proceed: keep the render as the final version (video_review).
  • exit 2 → FAIL — do NOT keep it. Read the report, fix, re-run.
  • exit 3 → ERROR — the check could not run (see below); fix the environment or the input, do not publish blind.

Transcription backend (in priority order): the GooseWorks whisper-proxy (CLI credentials or the sandbox token) → OPENAI_API_KEY (honors OPENAI_BASE_URL) → local whisper CLI. ffmpeg must be on PATH. With GW_MEDIA_VIA=mcp the CLI credentials are never used: that login can be a different account from the one the agent is connected to, and the paid transcript would bill it. In that mode the check uses OPENAI_API_KEY or the local whisper CLI, or stops and says so.

What counts as the same speech

Both the script and the transcript are put in one canonical spoken form before the diff. The rules are bounded — each is an exact rewrite, never a fuzzy match.

WrittenHeardRule
49, 105, 2,500, 1 millionforty-nine, one hundred and five, two thousand five hundred, a millionnumber words = digits
2.5, 2026, 249, 1st, 2ndtwo point five, twenty twenty six, two forty-nine, first, seconddecimals, years and prices read in pairs (only when spoken as words: written 2 20-minute is never 220), ordinals (second = 2nd only when the script writes 2nd)
No. 1, No.1, #1number onenumber sign, only when written with the dot or # (no 1-star reviews and no one stay negations)
5mg, 30g, 500ml, 12oz, 10 lbs, 30-dayfive milligrams, thirty grams, …, thirty daysunit after a quantity (weights, volumes, %, money, hours/minutes/seconds, days/weeks/months/years, calories, x times)
30%thirty percent / 30 per centpercent
$49, $49.99forty nine dollars, forty nine dollars and ninety nine centsmoney
larkfieldstraps.com, www.example.comlarkfieldstraps dot com, w w w dot example dot com, example dot comURL; www. is optional
don't, can't, it's, you'redo not, cannot / can not, it is, you arecontractions
Larkfieldstraps, Gooseworks, everyone, OneGlowLarkfield Straps, goose works, every one, One Glowfused/split: exact join of 2–3 words
TG1TG1, TG one, T.G. onewritten forms, no alias needed
TG1T G one, T G 1 (letters spaced out)only with a confirmed alias

Guards that keep the rules honest:

  • A unit word not after a quantity is left alone — a brand "MG" never becomes "milligrams".
  • Letters spelled one by one ("T G") are not fused into a word. That needs a confirmed pronunciation.
  • Fusion is exact concatenation. "Larkfeld Straps" is not "Larkfieldstraps".
  • A join never swallows a negation: "no table" is not "notable" ("no thing" is "nothing").
  • A number word joins a word only when every part has 2+ letters: "every one" is "everyone", but "G one" is not "gone".

What still FAILS

Report lineRoot causeFix
[high] said "59" where script has "49" — number differs…Wrong, added or dropped numberRe-roll. A number is never a benign paraphrase.
[high] dropped "5mg" — unit differs…A unit after a number was changed, added or dropped ("5mg" said "five")Re-roll. Only a dropped dollars/euros/pounds alone ("$9.99" said "nine ninety-nine") is not HIGH; dropped cents is.
[high] extra "doesn't" … negation changedA not/never/no/without was added or lost — the claim flipsRe-roll.
[high] said "Brune" where script has "Brume" — brand name not heard as approvedBrand mis-voiced or dropped (--brand-term / confirmed pronunciation)Re-roll; spell it phonetically in the SPOKEN LINE (e.g. Avi-too, never a (pronounced …) parenthetical). See create-video-seedance-2-fal Failure Modes.
[high] said "witted" where script has "vetted" — audio likely mis-voices…Seedance mis-voiced a similar-looking wordRe-roll a new seed.
[medium] dropped "…" / low similaritySeedance dropped an approved phraseRe-roll; if only a tail word, a surgical stitch_replacement.py window fix may recover it.
[low] extra "…" + low similarityExtra speech beyond benign fillerRe-roll. A single filler word ("so", "okay") in a normal-length line is LOW and passes.
⚠ audio is effectively silentWrong render / audio track lost in postRe-render / re-check the mux; never publish a silent take.
ERROR: no transcription backendNo proxy credentials, no OPENAI_API_KEY, no local whisperSign in / set the key / install whisper, then re-run.
ERROR: alias … would change a number, unit or negationA bad --alias or pronunciation entryFix the alias. Aliases may only respell a name.

The verdict passes only when similarity ≥ --min-ratio and there is no HIGH issue. Numbers, units, negations and declared brand names fail on their own (HIGH). Any other dropped or extra word is medium/low: it lowers the similarity, and fails the gate only when the similarity drops below --min-ratio (so one dropped ordinary word in a long line can pass). --expect-music is advisory only; it does not by itself fail the gate.

Brand names and confirmed pronunciations

Brand words are never removed from the diff. (Before 2026-10-06, --brand-term fuzzily stripped brand-like words, which let "Brune" pass for "Brume". That is gone.)

  • --pronunciations PATH (recommended when the voice-over used one) — the confirmed pronunciations file: create-vo-elevenlabs's brand-rules.json or the output of its scripts/read_pronunciations.py ({"brand_id", "basis", "pronunciations": [{"term", "say_as", "fact_id"}]}). Every entry becomes an alias and its term a brand term. An entry that cannot be used (see alias rules) is skipped with a WARNING, never fatal. A missing or unreadable file is an ERROR (exit 3), so pass the flag only when the file exists.
  • --alias "TERM=SPOKEN" (repeatable) — one confirmed spoken form, e.g. --alias "TG1=T G one". The term also becomes a brand term. A bad --alias is an ERROR (exit 3), checked before any transcription is spent.
  • --brand-term TERM (repeatable) — marks a brand name. Exactly:
    1. Where the term's words appear in the script, a substitution or drop there is HIGH (a brand mis-voicing). Its fused/split forms count as equal.
    2. A differing span is accepted as the same brand (reported [low], counted as a match) only when all of these hold: it has no negation, number or unit change; every word on both sides is an alphabetic word of some --brand-term; and the two sides look alike (character similarity ≥ 0.6). This keeps the older calling pattern working: a script written in the spoken form (Try ak-mee today) with --brand-term Acme --brand-term ak --brand-term mee passes when Whisper writes Try Acme today ("ak mee" vs "acme" = 0.67). Everything else still fails HIGH: a heard word that is not a declared term (Brume heard Brune), two different declared names (Hale vs Hart, Brume Body Pod vs Brume Band), a truncation (Acme heard ak), or a number inside a term (Pod 4 vs Pod 5, 7-Eleven: 7 days vs 11 days). Prefer --pronunciations over passing say_as words as --brand-term.

Rules for aliases:

  • Only pass spoken forms the user confirmed (saved brand pronunciations, or a form they confirmed in chat). Never invent one from the transcript to make the gate pass.
  • An alias may respell a name, digits and number-like syllables included ("TG1" = "T G one", "Tenzeal" = "ten-zeal", "Nosha" = "NO-shuh"). It is refused when the written term has a number, unit or negation that the spoken form changes ("TG1" = "T G two"), when the spoken form adds not, never, without, none, nothing or nobody ("Brume" = "never Brume"; no and nor are fine as syllables, "Nomad" = "no-mad"), or when the spoken form is only numbers, units or negations ("Decagon" = "five").
  • If you listened and the audio is right but Whisper spelled a coined brand name in a new way, ask the user to confirm that spelling, save it as a pronunciation, and re-run.

Inputs

  • --video PATH (required) — the rendered master mp4.
  • --script-file PATH or --script "text" — the approved spoken script. Omit both only for a genuinely script-free clip (the drift check is then skipped and the gate is advisory).
  • --brand-term TERM, --alias "TERM=SPOKEN", --pronunciations PATH — see above.
  • --min-ratio FLOAT (default 0.90) — transcript↔script similarity to pass, measured on the canonical spoken form.
  • --captions-srt PATH — optional SRT to check for caption-text defects.
  • --json PATH — write the machine verdict for the app's review panel. Each issue carries the canonical tokens (script_words / heard_words) and the original wording (script_text / heard_text).

Tests

In the goose-skills repo (in the goose-skills repo only; installed copies have no tests/ folder):

python3 tests/test_review_render.py    # or: python3 -m pytest tests/

Pure Python, no audio, network or paid call. Covers the audit fixture table (units, URL, numbers, percent, contractions, fused brands, wrong price, negation, Brume→Brune), number words, units (including added/dropped units in long lines), URLs, negation flips, fused/split words, CLI-style brand terms, confirmed TG1 aliases and saved pronunciations with number-like syllables, omission, extra speech, the report wording, and the CLI exit codes with transcription stubbed out.

Relationship to the fuller review

This is the shipped, single-file, gating slice of the fuller review loop in GooseWorks' studio (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 is not part of this skill.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

<slug>

FreeSummary

The supplied material contains only placeholder text for the skill’s purpose, inputs, steps, and completion criteria. It does not provide enough information to describe a task or result reliably.

  • No use case can be identified from the supplied material
  • Purpose is unspecified
  • Inputs and expected results are unspecified
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

ad-angle-miner

FreeSummary

Research supported advertising angles using buyer context, current product facts, customer language, and observed ads. Turn the evidence into static ad, video, or copy ideas, matching video concepts to available recipes. Scores rank ideas for testing; they do not predict results.

  • Finding evidence-backed angles for a product campaign
  • Developing static ad or video concepts from customer research
  • Writing headline and primary-text options for ads
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

Analyze campaign data from Google, Meta, and LinkedIn to find strong and wasteful spend. The skill checks funnel performance and test results, then recommends which campaigns to pause, scale, or test and how to shift budget across channels.

  • Finding campaigns and ads that waste budget
  • Comparing performance across Google, Meta, and LinkedIn
  • Planning specific budget shifts and follow-up tests
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

Compare ad spend and signups with downstream outcomes to calculate the cost of each qualified lead. The skill checks tracking coverage, accounts for how long leads need to mature, and groups creatives into actionable categories with confidence notes.

  • Compare true qualified-lead costs across creatives
  • Find low-CPA ads that bring poor-quality leads
  • Check whether signups can be linked to downstream outcomes
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

Prepare the intake for a Meta ad campaign by reviewing available brand information first, stating reasonable assumptions, and asking only questions whose answers could affect budget, claims, or legal exposure. It records stable brand facts, a campaign brief, and what was asked versus assumed.

  • Prepare a Meta ad campaign when brand facts are missing
  • Clarify budget and timing before campaign planning
  • Record approved claims and audience restrictions
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

ad-policy-check

FreeSummary

Review ad copy, image text, visuals, and people against platform and brand category rules. It suggests honest fixes and needed disclosures, then flags issues requiring human or legal review, with a separate result for each ad and platform.

  • Checking ad copy and visuals before launch
  • Reviewing creator ads for required disclosures
  • Fixing a platform disapproval and recording the issue
gooseworks-ai/goose-skills1.3KUpdated Oct 27, 2026

See all skills by gooseworks-ai

Report a problem with this skill