本文へ移動
cccskills
無料GitHub で公開日本語紹介

review-ugc-render

UGC動画の音声を承認済み台本と照合し、数字やブランド名、否定表現などの読み違いを公開前に検出するレビュー工程です。

原文原文の説明を見る

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-skillsスター 1,272(GitHub 1,272 + cccskills 0)
連携ツールOpenAIElevenLabs

実行スコア 未検証

インストール方法を見る

こんなときに便利

  • UGC動画を公開前に確認したいとき
  • 数字やブランド名の読み違いを検出したいとき
  • 修正後の動画を再チェックしたいとき

日本語での紹介

できること

完成したUGC動画の音声をWhisperで文字起こしし、承認済みの台本と照合します。数字や単位、ブランド名、否定表現の違い、承認済みの語句の抜け、音声の無音状態などを検出し、動画を最終版として採用できるか判定します。「5mg」を「five milligrams」と読むような表記上の違いは、同じ発話として扱います。問題がある場合はレポートを確認して修正し、再チェックします。

こんなときに便利

生成した動画の音声が台本どおりか、公開前に確認したいときに使います。映像を目視するだけでは見逃す読み違いや、数字・ブランド名の変化をチェックできます。UGC動画のレシピでは、レンダリング後、最終版を確定する前に実行するレビュー工程です。

使い方の例

  • 「この動画の音声を承認済み台本と照合してください」
  • 「再レンダリングした動画をもう一度レビューしてください」

注意点

実行には動画ファイル、承認済み台本、ffmpegが必要です。文字起こしにはwhisper-proxy、OPENAI_API_KEY、またはローカルのwhisper CLIのいずれかを使います。確認済みの読み方を使った場合は、発音情報ファイルを指定できます。台本のない動画では差分チェックは省略され、判定は参考扱いになります。

この紹介文は、公開されている SKILL.md をもとに AI(OpenAI Codex)が作成しました。正確な仕様は下の原文を確認してください。

含まれるファイル(4)

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

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

<slug>

無料概要あり

資料には具体的なスキルの内容や手順が記載されていないため、用途や得られる結果を特定できません。

  • 用途を確認したいとき
  • 入力や手順を確認したいとき
  • 期待する結果を確認したいとき
gooseworks-ai/goose-skills1,2722026年10月27日 更新

ad-angle-miner

無料概要あり

顧客の課題や商品情報、広告事例を調べ、根拠のある広告訴求と静止画・動画・コピー案にまとめます。動画案は実際の制作フォーマットとの相性も確認し、商品単位の角度集として整理します。

  • 商品の根拠に沿った広告の切り口を探したいとき
  • 静止画広告や動画広告の案を作りたいとき
  • 顧客の言葉から見出しや広告文を考えたいとき
gooseworks-ai/goose-skills1,2722026年10月27日 更新

ad-campaign-analyzer

無料概要あり

Google、Meta、LinkedInなどの広告実績を分析し、成果の出た広告や予算の無駄を特定します。停止・拡大・テスト案や、具体的な予算配分を提案します。

  • 広告予算の無駄を見つけたいとき
  • 複数媒体の成果を比較したいとき
  • 広告の停止・拡大候補を決めたいとき
gooseworks-ai/goose-skills1,2722026年10月27日 更新

ad-lead-quality-analyzer

無料概要あり

広告費と登録後の成果を照合し、質の高いリード獲得にかかった実コストを算出します。広告素材ごとに拡大・維持・調査・停止の判断材料を整理するスキルです。

  • 広告素材ごとの実質獲得コストを比べたいとき
  • 低CPAでも質の低い広告を見つけたいとき
  • 登録後の成果データとの照合状況を調べたいとき
gooseworks-ai/goose-skills1,2722026年10月27日 更新

ad-management-intake

無料概要あり

Meta広告を始める前にブランド情報を調べ、予算や広告表現に関わる不明点だけを質問して準備を整えます。確認事項と仮定を記録し、ブランド情報とキャンペーン概要を作成します。

  • ブランド情報が未記録の状態で広告を始めたいとき
  • 予算や広告期間の前提を整理したいとき
  • 広告で使う主張や制約を記録したいとき
gooseworks-ai/goose-skills1,2722026年10月27日 更新

ad-policy-check

無料概要あり

広告文や画像内の表現を配信先と商品カテゴリのルールに照らして確認し、直せる箇所を修正しながら、法務や人の判断が必要なリスクを広告ごとに整理します。

  • 広告の配信前チェック
  • 広告画像や動画の表現確認
  • クリエイター広告の表示確認
gooseworks-ai/goose-skills1,2722026年10月27日 更新

gooseworks-ai のスキルをすべて見る

このスキルの問題を報告する