القائمة
Infer frame-to-frame transitions from storyboard image diffs and OCR deltas, then write an evidence-backed transition manifest.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Assemble a grounded review prompt from a local artifact bundle so Codex or Claude Code can inspect the right files and ask the right questions.
Check a local video against layout annotations, safe zones, OCR text boxes, and frame samples so agents can catch cropped content, caption overlap, unreadable overlays, and platform-unsafe composition before shipping.
Collect first-pass source media facts, audio silence/energy, shot estimates, representative frame status, and persistent text/caption risk evidence.
Review a rendered video for technical defects such as resolution mismatch, missing or near-silent audio, black or white frames, edge gutters, low motion, sparse caption bands, and layout issue pass-through.
Fuse video shot segments with storyboard frames, OCR, transitions, and timeline artifacts into one per-segment evidence map for grounded video review.
Extract at least one storyboard frame per video shot segment so later OCR and segment evidence fusion can cover gaps missed by global sampling.
| name | storyboard-transitions |
| description | Infer frame-to-frame transitions from storyboard image diffs and OCR deltas, then write an evidence-backed transition manifest. |
Use this after storyboard-ocr when an agent needs sequence-level
change evidence instead of isolated sampled frames.
This skill owns:
screen-change or state-changestoryboard.transitions.jsonProvide either storyboardDir or ocrPath:
{
"storyboardDir": "./output/storyboard",
"threshold": 0.02
}
threshold is the normalized visual-diff sensitivity and defaults to 0.02.
The skill writes storyboard.transitions.json with adjacent-frame transitions.
Each transition includes frame indices, timestamps, visual diff percentage, OCR
overlap, shared line count, added/removed lines, transition kind, confidence,
and evidence notes.
Run after storyboard-ocr. It benefits from hybrid extraction because
same-screen sampling metadata can support state-change interpretation. Run
storyboard-understand after this when you want a higher-level flow summary
that can incorporate transition evidence.
screen-change suggests a broader view change. state-change suggests the
same shell with changed content. scroll-change and dialog-change depend on
stable anchors, OCR regions, and visual deltas. uncertain is expected when
OCR was rejected or adjacent frames have too little shared evidence. Confidence
is heuristic, not a probability.
Do not infer user intent or causal actions from transitions alone. Abstain from precise workflow claims when transition confidence is low, OCR quality is rejected, or frame sampling skips the moments between two states.
The runner needs existing OCR output and accessible frame images. Missing OCR,
missing images, or ffmpeg failures during diff preprocessing will fail the
run. Very small threshold values can over-label visual noise; high values can
hide subtle UI changes.
Repo-side runner:
node --import tsx scripts/harness/storyboard-transitions.ts
Installed-pack runner:
node ./.video-evaluator/agent/run-tool.mjs storyboard-transitions