agentleFS
svenkatreddysvenkatreddy/universal-video-skills/skills/video-qa/SKILL.md

video-qa

Skill8 starsChanged 28 days agoMITView on GitHub

Review AI-generated clips like a QC department: per-shot checklists, frame evidence, continuity across joins, and honest verdicts. Use when deciding whether a clip ships, gets fixed, or gets cut.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every AI clip gets reviewed before it ships.

    line 8
  2. Distinctive:

    Two strikes, then replan: If a clip fails twice, the problem is the shot, not the prompt: simplify it, shorten it, switch to …

    line 38

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Video QA

Every AI clip gets reviewed before it ships. Not watched, but reviewed: against its brief, frame by frame where it matters, with a written verdict. The review is short, but it's written down, because "looked fine" is how bad shots survive into the final cut.

The workflow

  1. Check against the brief. The shot-brief is the spec (references/qa-checklist.md). The clip either does its story job or it doesn't. Everything else is secondary. Name failures from the taxonomy (references/failure-taxonomy.md) so each defect maps to its fix.
  2. Pull frame evidence. Contact sheets at clip boundaries and key beats (references/frame-evidence.md, scripts/contact_sheet.py). For volume, run the embedding triage first (references/automated-identity-qa.md, scripts/identity_score.py). Humans review the failures plus a sample of passes. Eyes miss drift that stills catch.
  3. Check the joins. Continuity across every cut (references/continuity.md): geography, light, wardrobe, screen direction.
  4. Write the verdict. Ship, fix (with the one variable to change), or cut. No fourth option, no "maybe it'll work in the edit."

Rules that don't bend

  • The brief is the spec. "It's a nice clip" is not a pass. Does it do what the shot list row says? That's the only question.
  • Check the tails. AI clips degrade toward their ends. The last two seconds get the hardest look, not the first two.
  • One variable per fix. A failed clip goes back with exactly one slot changed. Two failures with two different changes teach you nothing.
  • Two strikes, then replan. If a clip fails twice, the problem is the shot, not the prompt: simplify it, shorten it, switch to image-to-video, or cut it.
  • Write it down. Clip ID, verdict, what was wrong, what changed. This log becomes your project's failure-mode list. The most valuable document you own by the end.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.