Video Qa logo

Video Qa

Community
mrpaidsocial
video-qa

Four-layer QA for a rendered video edit — run it on any .mp4/.mov you or a pipeline just produced. Use when asked to QA / check / verify / audit a render or export, hunt clipped words, duplicate dialogue at cuts, dead air, splice clicks, black / frozen / flash frames, loudness (LUFS) or clipping problems, confirm a fix after a re-render, or build an inspection packet (contact sheet + waveform + transcript) for a suspect timestamp. L1 = ffmpeg/ffprobe technical checks, L2 = transcript edit-boundary checks mapped through the EDL, LF = optional per-frame rule checks (text in the platform-UI zones of a vertical video, a graphic covering a face, likeness against a reference photo for AI clones), L3 = optional Gemini watch+listen pass on a 480p proxy, L4 = targeted inspection packets. Needs only ffmpeg/ffprobe; whisper, TYPESAFE_API_KEY and GEMINI_API_KEY unlock the deeper layers.

Overview

Publishermrpaidsocial
Repositorymrpaidsocial-video-editor-agent
Skill namevideo-qa
Stars
114
Forks
34
Bundled files
7
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mrpaidsocial on GitHub. Read the source before you install it.

Installation

Install the Video Qa AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mrpaidsocial/mrpaidsocial-video-editor-agent/tree/main/.claude/skills/video-qa
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mrpaidsocial/mrpaidsocial-video-editor-agent.git /tmp/mrpaidsocial-video-editor-agent
mkdir -p .claude/skills
cp -r /tmp/mrpaidsocial-video-editor-agent/.claude/skills/video-qa .claude/skills/video-qa
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Video Qa in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Video Qa on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Video Qa is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

video-qa — 4-layer QA for rendered video edits

A finished render is an audio + video artifact — roughly half of real editing mistakes are audible, not visible (a live post-mortem on a shipped branded edit found 6 audible seam flubs that stills-only QA missed). This skill QAs an edit without screenshot sweeps by spending compute cheap → expensive:

CHEAP    L1  ffprobe/ffmpeg technical (blackdetect, freezedetect, flash frames,
             decode errors, duration-vs-intent, silencedetect + RMS envelope,
             LUFS via ebur128, clipping)
         L2  transcript edit-boundary checks on EVERY dialogue cut
             (clipped words, duplicate phrases, seam dead-air, caption coverage,
             butt-splice clicks) + isolated seam re-probes
         LF  per-frame rule checks with a typed-judgment model (TypeSafe Jev):
             1 fps + every caption/graphic midpoint, ~0.1 s and ~$0.0001 a frame —
             overlay text in the top 14% / bottom 26% of a vertical frame (the Reels
             UI), a pasted graphic over a visible face, optional likeness drift
         L3  a multimodal model watches AND listens to a 480p proxy (audio intact),
             5fps sampling, enforced JSON — tells you WHERE to look (optional)
EXPENSIVE L4 inspection packets: contact sheet + marked waveform + word-level
             transcript + audio stats for one window — verify before changing an edit

Run the engine first (tools/video-qa)

The procedure below is implemented as a standalone node package. Install once (npm --prefix tools/video-qa install), then:

bash
# reel-recut lane — the manifest build_reel.py dumps next to the spec, + SOURCE-time words
npm --prefix tools/video-qa run qa:video -- --manifest <p>/spec.qa-manifest.json --words <p>/transcript.json

# hyperframes lane — the picture-lock EDL + OUTPUT-time words (+ optional placement manifest)
npm --prefix tools/video-qa run qa:video -- --lane hyperframes --video <p>/out.mp4 \
    --edl <p>/edl.json --words <p>/words-master.json --words-are-output [--placement <p>/preview/manifest.json]

# any mp4, no edit intent — L1 + L3 only
npm --prefix tools/video-qa run qa:video -- --video <p>/out.mp4

# a Layer-4 inspection packet for one window
npm --prefix tools/video-qa run qa:inspect -- --manifest <p>/spec.qa-manifest.json --start 31.5 --end 33.0

# check every planned graphic, then collect actual-render evidence
npm --prefix tools/video-qa run qa:storyboard -- --storyboard <p>/storyboard.json \
    --html <p>/composition.html --video <p>/out.mp4

# an AI-clone edit: also check every sampled face against a reference photo
npm --prefix tools/video-qa run qa:video -- --video <p>/out.mp4 --likeness-ref <reference.jpg>

# enforce completed technical + transcript checks before delivery
npm --prefix tools/video-qa run qa:video -- --manifest <p>/spec.qa-manifest.json \
    --require-layers technical,transcript

Flags: --skip-semantic (no Gemini), --fps N, --instructions file.txt (the original brief, given to Gemini), --no-cache, --out dir, --json. Frame checks: --skip-frames, --frames-fps N, --frames-max N, --safe-zone TOP,BOTTOM (fractions; off disables), --no-face-check, --likeness-ref photo.jpg, --likeness-threshold P. Exit 0 PASS · 1 PASS_WITH_WARNINGS · 2 FAIL. Reports land in <video dir>/_qa/<stem>/qa-report.{md,json} with packets under inspect/<issue-id>/. Relative paths resolve from the directory you ran the command in; .env is read from there first, then from this pack's root. Full flag and environment reference: tools/video-qa/README.md.

Coverage is explicit in the JSON/Markdown report. Missing or degraded optional layers produce PASS_WITH_WARNINGS; unavailable required layers produce FAIL. Technical is required by default. --skip-semantic is supported and its unavailable coverage is shown. Layer failures preserve the completed layers in a partial report. Cache fingerprints include effective instructions, semantic FPS, thresholds, transcript configuration and source-file identity; degraded/skipped layers are retried, not cached.

Storyboard completeness

Save storyboard.json from the accepted plan before authoring HTML:

json
{"version":1,"elements":[{"id":"proof-card","start":4,"end":8},{"id":"cta","selector":"#closing-cta","start":12,"end":15}]}

Each id is stable and unique. selector is optional and supports a single HTML #id; it defaults to the storyboard ID. Targets or their timed ancestors use absolute output-time data-start plus data-duration or data-end. The checker reports omitted/duplicate IDs, missing schedules, zero/reversed windows, and schedules that do not cover their planned windows. The JSON schema is tools/video-qa/schemas/storyboard.schema.json.

Run once against HTML before rendering and again with --video afterward. The latter extracts three frames from the actual MP4 for every planned element (10%, 50%, 90% of its window), writes indexed contact sheets and records the render hash and timestamps. Read the samples for what should be present. A static schedule pass does not prove rendered visibility: JS/GSAP, CSS/occlusion, external HTML, and nested composition offsets are not evaluated. The report keeps renderedVisibility: "not_verified"; visually review the real samples before saying a graphic appears. A missing/unreadable evidence window fails the CLI.

When the engine cannot run (no node, a lane it has no adapter for), do the layers by hand:

You (the agent) ARE the orchestrator: run the commands, parse the logs, apply the calibration gates, write the report. Each layer is a documented procedure, not a black box.

The three iron rules (learned the hard way)

  1. Never re-whisper the whole render and diff it. Whisper hallucinates connective phrases at jump cuts and fuses words differently every run. L2 maps SOURCE-side word times through the EDL; suspect seams get an isolated 5.5s window re-probe of the render, arbitrated by word presence — never by whisper's duration numbers (word ends are routinely padded into pauses).
  2. The manifest comes from edit INTENT, never from analyzing the output. Use the cut list / EDL / placement data the build itself produced. A manifest derived from the render would inherit the exact bugs QA exists to catch.
  3. Measure the FILE, never the log. Duration, streams, loudness all come from ffprobe/ffmpeg on the actual output file. Render logs lie.

Inputs

inputrequired?gives you
rendered video fileyesL1 always runs
edit-intent manifest (EDL / cut list / placements)strongly recommendedL2 boundary checks, intentional-region gating, stable issue anchors
source-time word timings (whisper of the SOURCE)recommendedclipped-word + duplicate + caption checks
source footageoptionallets you transcribe the source yourself
TYPESAFE_API_KEY in .envoptionalLF frame checks — skipped without it and then not counted as missing coverage
GEMINI_API_KEY in .env at repo rootoptionalL3 — skip gracefully without it, never crash

Manifest format, EDL adaptation, and the source→output word-mapping algorithm: references/manifest-and-edl.md. No manifest at all → run L1 + L3 only ("generic lane") and say so in the report.

Procedure

Work in a scratch dir next to the video: <video dir>/_qa/<video stem>/.

  1. L1 — technical. Follow references/layer1-technical.md. Three ffmpeg/ffprobe passes + the RMS-envelope lull scan (scripts/rms_scan.py). Timestamps from this layer are EXACT — downstream windows can be tight.
  2. L2 — transcript boundaries. Follow references/layer2-transcript.md. Runs on every dialogue cut; escalate marginal calls to isolated seam re-probes. Degrades (click checks only) when no word timings exist — never blocks.
  3. LF — frame checks. Runs inside qa:video when TYPESAFE_API_KEY is set (the engine's runQa() only runs it when asked). One request per sampled frame; runs of flagged frames become one issue each with the frame files as evidence under _qa/<stem>/frames/. text_in_unsafe_zone, face_covered and identity_drift are MEDIUM, caption_over_face is LOW. Text counts only when two yes/no answers AND a text box reaching more than 2% into a zone agree; a covered face needs p ≥ 0.75 (faces inside screen recordings scored 0.56–0.69 in calibration, pasted pictures over the speaker 0.77+). These are pointers, like L3: open the evidence frames before changing an edit. A full-screen takeover has no visible face, so it is not flagged as a cover.
  4. L3 — semantic watch+listen. Follow references/layer3-semantic.md. Build a 480p proxy with audio intact, upload to Gemini, get schema-enforced JSON. Skip cleanly if no key. Its timestamps are ±2s — its job is to tell you WHERE to look, never to be trusted blindly.
  5. Aggregate. Merge issues; a semantic finding overlapping a deterministic finding (compatible defect categories plus the same event anchor, or overlapping time windows within 1s) is corroborated — raise confidence on both. Gemini-only issues never exceed HIGH.
  6. L4 — inspect before you touch anything. For every CRITICAL/HIGH issue (top ~4), build an inspection packet per references/layer4-inspection.md, look at it, and only then decide. Deterministic windows: pad ±0.5s. Gemini windows: pad ±1.5s.
  7. Report. Write qa-report.md (+ .json if scripting) in the _qa dir: verdict, per-layer status, issues sorted severity-then-time, each with its stable anchor, evidence, and suggested fix. Packets live under inspect/<issue-id>/.

Issue anchoring

Anchor issues to stable manifest event ids (cut:src48.8, caption:12 — keys derived from the edit's own identifiers), not timestamps. A fix that shifts the timeline moves every timestamp but keeps the anchors, so comparing anchored issues across re-renders tells you reliably whether something was actually fixed.

Severity and verdict

  • CRITICAL — corrupt/unreadable render, missing expected audio stream, hard clipping at 0 dBFS, >1s duration mismatch. Never ship.
  • HIGH — probe-confirmed clipped word, duplicate dialogue, unexpected black or frozen frames, flash frames at a seam. FAIL until fixed or explicitly overridden.
  • MEDIUM — dead air, splice click, loudness off target, caption mismatch, SFX masking VO. Warn — reviewable, not blocking.
  • LOW — informational (hot-but-unclipped master, paraphrased captions by design, unconfirmed suspicions). Never blocks; never auto-"fix".

Verdict: any CRITICAL/HIGH → FAIL · any MEDIUM → PASS_WITH_WARNINGS · else PASS when all layers completed. Unavailable optional coverage → PASS_WITH_WARNINGS; unavailable required coverage → FAIL. Use exit codes 0 / 1 / 2 in that order. Never call partial checks a clean pass.

Fix loop + auto-fix whitelist

run QA → FAIL? → read packet → fix → re-render → re-run. You may apply these repairs without asking:

actionlimit
nudge a cut point≤ 500ms
retime a captionto its spoken window
gain/level adjustment≤ 3dB
extend/trim a clip≤ 500ms
remove an accidental duplicate segmentexact duplicate only
add an edge fade at a splice click25–30ms

Anything else — restructuring the edit, dropping content, creative changes — goes to the user with the inspection packet (2–3s subclips beat scrubbing). Max 3 fix→re-render rounds, then stop and escalate. Never loop on LOW or subjective issues.

Calibration notes (from live runs)

  • A static full-frame takeover is a frozen_frames HIGH, and it reads dead to a viewer too. A dark layer with two still cards passed while karaoke captions animated under it and failed the moment the captions were removed; a video takeover that holds on a chat bubble for ~1 s failed the same way. Give every takeover motion (a slow scale/translate drift, 1 → 1.03–1.12 over its window) and confirm with freezedetect=n=0.003:d=0.5 on the whole rendered file before the engine runs (2026-09-28).

  • L3 (Gemini at 5 fps) reports a 0.18 s pop-in as a "corrupted title card". Frame-check the first 15 frames of the render at 1:1 before treating an L3 visual_glitch inside the first 0.3 s as real.

  • Downscaled contact tiles lie about glyphs. A 300 px tile showed "The?"; the full-resolution frame read "The". Confirm any text defect at 1:1.

  • Second-model audit before delivery (2026-09-28). The four layers passed a master with a real blown take (three ~60 ms false starts; see reel-recut workflow § 5c). A pro-tier model that hears the audio at full rate (the video through the Files API, not the 5 fps 480p proxy) caught it; a second model given frame sheets + transcript caught a semantic mismatch instead (B-roll of a different task under a first-person claim). Run both as an audit pass on the master with a prompt that states the deliberate choices (no text, 30 ms joins, allowed face cover) so they critique the execution, not the brief; cross-check every finding in pixels or in the envelope before acting.

  • A shipped-clean reel with 49 silence-derived cuts must come back PASS with zero HIGH — keep a known-clean video as your false-positive canary.

  • A known-dirty pre-fix edit: the L3 pass heard both documented seam flubs (a false-start "Because…" fragment and a re-take clip) that stills-based QA had missed.

  • A repaired edit came back PASS_WITH_WARNINGS for a quiet −21 LUFS master + one splice click — both real observations, neither blocking. That is the system working.

  • Silence QA needs BOTH silencedetect AND an RMS-envelope pass: breathy −28..−36dB lulls read as gaps to humans but sail under −38/−40dB silencedetect. Two real dead-air gaps in a shipped edit were only found by the envelope scan. See L1 reference.

  • Silence-derived cuts (a cut whose removed region was measured silence) cannot clip audible speech — word "overlap" there is whisper end-padding. 40 of 49 cuts false-flagged on a live reel before this gate existed. Only probe-confirmed misses flag.

  • L3 API 503s: retry ×3 with backoff, then mark the layer skipped with the reason in the report — never a crash.

Dependencies

Offline regression suite: npm --prefix tools/video-qa test; typecheck: npm --prefix tools/video-qa run typecheck. The default tests use fixed seam probes and generated local media, including the production cut assembler's 128-span render. They do not call an inference API, install a model, or use TTS. Live macOS TTS/transcriber integration is a separate opt-in: npm --prefix tools/video-qa run test:live.

  • node >= 20 + npm --prefix tools/video-qa install for the engine (tsx, zod, dotenv).
  • ffmpeg / ffprobe on PATH (or FFMPEG_PATH / FFPROBE_PATH env vars; the engine also looks in /opt/homebrew/bin and /usr/local/bin). Note: many builds lack drawtext — text on images goes through PIL (scripts/draw_markers.py).
  • whisper, either via npx hyperframes transcribe (whisper.cpp under the hood; install with npx hyperframes) or a local whisper-cli + ggml model. Only needed for L2 transcription/probes when no word timings were provided.
  • python3 for the helper scripts; PIL (Pillow) optional, only for waveform markers.
  • GEMINI_API_KEY in a .env at repo root for L3 (GEMINI_QA_MODEL optional, default gemini-flash-latest). Missing key = L3 skipped, everything else runs.
  • OPENAI_API_KEY (optional) — cloud whisper-1 fallback when whisper.cpp is unavailable (VIDEO_QA_TRANSCRIBER=auto|whispercpp|openai|none).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Video Qa AI skill do?

Four-layer QA for a rendered video edit — run it on any .mp4/.mov you or a pipeline just produced. Use when asked to QA / check / verify / audit a render or export, hunt clipped words, duplicate dialogue at cuts, dead air, splice clicks, black / frozen / flash frames, loudness (LUFS) or clipping problems, confirm a fix after a re-render, or build an inspection packet (contact sheet + waveform + transcript) for a suspect timestamp. L1 = ffmpeg/ffprobe technical checks, L2 = transcript edit-boundary checks mapped through the EDL, LF = optional per-frame rule checks (text in the platform-UI zo...

Why use Video Qa on TypingMind?

Because you install it once and use it with any model. Video Qa is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Video Qa in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mrpaidsocial/mrpaidsocial-video-editor-agent/tree/main/.claude/skills/video-qa. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Video Qa?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Video Qa?

As many as you like. As long as a model supports skills, you can use Video Qa with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Video Qa AI skill free?

It is published on GitHub by mrpaidsocial. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇