video-quality-control

Review AI-generated video for visual, technical, and rights defects before publication.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill video-quality-control-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: video-quality-control
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/video-quality-control
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill video-quality-control-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated video often contains subtle defects like identity drift, flicker, pseudo-text, or watermarks that slip past casual review and reach production. This Skill provides a structured quality-control gate that inspects every candidate against the approved brief, storyboard, and rights report before post-production or publication. ## Core Features & Use Cases - Evidence-Based Inspection: Extracts metadata with ffprobe, pulls opening/closing/storyboard keyframes, builds contact sheets, and tests desktop and mobile crops. - Blocking Defect Detection: Rejects candidates for subject drift, deformed anatomy, flicker, unintended cuts, lost text-safe zones, visible watermarks, or unsafe content. - Structured Review Output: Produces a YAML review result with blocking and non-blocking findings, technical measurements, and responsible-stage routing to the correct upstream role. - Use Case: After generating a looping product video, run this Skill to verify the loop seam, confirm no watermark appears, check the mobile crop preserves the text-safe zone, and route any timing defect back to the scriptwriter. ## Quick Start Review the candidate video file against the approved storyboard and rights report, then return a structured approval or rejection with findings.

Frequently Asked Questions about video-quality-control

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

FAQPage Schema
How do I quality-check AI-generated video before publishing?▼

Inspect the video's metadata with ffprobe, extract opening, closing, and storyboard keyframes, and build a contact sheet at regular intervals. Then review at normal speed and frame-by-frame around transitions and the loop seam, comparing frames against the approved storyboard and source references.

What visual defects should reject an AI-generated video?▼

Reject for subject identity or geometry drift, deformed hands or faces, added pseudo-text or logos, flicker, texture crawling, exposure pumping, unintended scene cuts, camera motion conflicting with the storyboard, lost text-safe zones, visible watermarks, or unsafe content.

Can ffprobe check video codec, duration, and frame rate?▼

Yes, ffprobe reports codec, container, dimensions, aspect ratio, duration, frame rate, audio presence, and decode errors. Record these alongside file size, first-frame suitability, loop-seam difference, and desktop and mobile crop tests.

Why should OCR not be the primary video review method?▼

OCR only reads text layers and misses visual defects like identity drift, deformed anatomy, flicker, and composition problems. Direct frame inspection against storyboard keyframes and source references is required for reliable visual review.

When can a human override a video quality rejection?▼

Human aesthetic preference may select among technically approved candidates, but it cannot waive rights or safety blocks. Approval is only allowed when there are zero blocking findings in the review result.