Frame Extraction

Use When

• The user needs selected still frames, a contact sheet, or a review pack from local video files for persona, product, UI, hook, CTA, before/after, or shot structure work.
• Use video-analysis before or alongside this skill when shot-level understanding already exists or would materially improve frame selection.

Do Not Use When

• The task belongs to ideation, QA, or another released skill listed in the handoff section.
• Required inputs are missing and guessing would change the result.

Selection Boundary

• Do not default to uniform sampling. Choose the smallest extraction mode that matches the task intent.
• Good mode defaults: persona/vibe face-priority, shot/structure scene-change, product visibility object-priority, UI/text text-ui-priority, hook hook-first, CTA/compliance cta-last, broad scan uniform-sample.
• Scope should be explicit: first 3-5 seconds, final 3-5 seconds, full video, or a requested timestamp range.

Source And Path

• Inputs can be one local video, a folder, or a manifest mapping source ids to local files. If only URLs are available, recover/download local files first.
• Preserve source video, timestamp, extraction mode, selection reason, and source basis in the frame manifest.
• Keep internal extraction requests, plan outputs, contact-sheet inputs, and intermediate manifests under .postplus; keep final frames/contact sheets in the user-facing output folder.

Review And Handoff

• Package outputs for the downstream job: persona frames plus contact sheet and vibe notes, shot frames plus timestamp list, product-visible frames plus proof notes, or UI frames plus readable text notes.
• For long videos, start with the bounded first pass, then expand only after the first manifest proves the mode is useful.
• Return final frame folders, contact sheets, and frame manifest paths.

Stop Conditions

• Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result.
• If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.

Public Command Boundary

• Choose the smallest matching command or workflow from the user input and run it directly.
• If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.