asset-approval
Register and approve generated or imported media across reference, voice, dialogue, music, SFX, video, master, trailer, social, artwork, and release groups with one durable primary/alternate/reject st
SKILL.mdskills/asset-approval/SKILL.md
GitHubAsset Approval
Workflow
- Read
../../references/MEDIA_REGISTRY.md, project dependencies, and the relevant source artifact. - Register each concrete media candidate in
00_project/media_registry.jsonlwith a newMEDIA-###ID. - Preserve the domain source ID such as
TAKE-###,VOICE-###,MUS-###,SFX-###,REF-###,TRL-###, orSOC-###. - Use one approval group per decision scope.
- Inspect media and relevant QC before selecting a primary.
- Keep useful alternates. Keep rejected and superseded history. Rejection changes state; it does not physically delete a file.
- Never select a QC-failed candidate without explicit
qc_override: trueand a concrete user-approved reason. - Use
scripts/media_registry.pyfor deterministic state changes when available. Usescripts/media_lifecycle.pyonly after an explicit deletion or runtime-copy-repair request; it may delete only an exact eligible registered path and records the cleanup operation. - If a primary replacement affects downstream timing, identity, content, or continuity, run
project-impact.
Weak-model rule
Never infer approval from filename order, newest timestamp, highest seed, or generation success. Only media_approvals.json determines the current primary.
Done
Every reviewed media group has zero or one primary, explicit alternates, preserved rejected history, and project-relative paths.