08-video-qa-review

Reviews AI-generated video clips against shotlists and character bibles to produce PASS/FAILED QA reports.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill 08-video-qa-review-ntd237
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 08-video-qa-review
Source: https://github.com/ntd237/draft_toolkits_20042026/tree/main/other-skills/video-skills/08-video-qa-review
Command: npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill 08-video-qa-review-ntd237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated video clips often contain defects like face drift, morphing characters, motion glitches, or content mismatches, and teams lack a structured way to catch these errors before final assembly. This Skill provides a standardized QA gate that checks every clip against the shotlist and character bible, classifies defects with a consistent taxonomy, and blocks the pipeline until all shots pass. ## Core Features & Use Cases - Two-Layer Clip Inspection: Verifies content match against the shotlist and bible (subject, action, location, face similarity, camera, dialogue), then scans for AI defects using a standard taxonomy (morphing, face-drift, artifact, motion-glitch, audio-mismatch) with minor/major severity levels. - Two-Phase QA Workflow: Supports keyframe QA on static images before rendering to save credits, and video clip QA after animation or lip-sync, with batch review following the generation order. - Actionable Fix Recommendations: Maps each defect type to concrete fixes such as switching to lip-sync mode with Hedra or LivePortrait, regenerating keyframes with InstantID or Midjourney --cref, or rescuing shots via face swap with FaceFusion or Remaker AI. - Use Case: After generating 12 clips for a short AI film, run this Skill to produce a qa-report.md showing which shots passed, which failed with evidence, and exactly what the prompt engineer should change in the next fix round (up to 3 rounds). ## Quick Start Review the generated clips in my project against the shotlist and character bible, then write a qa-report.md with PASS or FAILED verdicts and fix suggestions for each shot.

Frequently Asked Questions about 08-video-qa-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I QA AI-generated video clips before final assembly?▼

Check each clip against the shotlist and character bible in two layers: content match (subject, action, location, camera, dialogue) and AI defects (morphing, face-drift, artifacts, motion glitches, audio mismatch). Record verdicts in a qa-report.md and block assembly until all shots pass.

How to fix face drift in AI-generated video characters?▼

For dialogue shots, switch to lip-sync generation using tools like Hedra or LivePortrait with the character anchor image. For action shots, generate keyframes with InstantID or Midjourney --cref first, or apply face swap with FaceFusion or Remaker AI to rescue otherwise good clips.

What defects should I check when reviewing AI video output?▼

Check five standard categories: morphing (subject shape changes), face-drift (face differs from the character bible), artifacts (extra limbs, phantom text, watermarks), motion-glitch (stuttering or looping movement), and audio-mismatch (wrong dialogue or doubled sound effects).

Can I check keyframes before rendering AI video to save credits?▼

Yes. Keyframe QA compares static images against the character anchor images before any video rendering happens. This catches face and setting mismatches early, avoiding wasted generation credits and render time on defective shots.

When should a video clip be marked FAILED versus PASS?▼

Any defect rated major, meaning it breaks immersion or contradicts the intended content, results in a FAILED verdict. Minor defects that typical viewers would not notice can still pass. Shots without reviewable evidence are marked NOT-CHECKED rather than judged.