mehul0810/agent-skills

Product Video Producer

Turn product truth, approved assets, footage, and references into distinctive, evidence-led video with deterministic outputs and bounded review.

Route

• Reference review, brand translation, storyboard, typography, pacing, composition, motion, or abstract storytelling: read references/reference-to-storyboard.md.
• Cinematic film, instructional walkthrough, or advanced motion execution: use the relevant mode guidance in references/production-modes.md as the single optional support for the current stage, replacing rather than stacking another supporting reference. Keep modes optional and combine only when the brief benefits.
• Editing, real software capture, ingest/conform, sound, color, captions, rendering, manifest, QA, or user-critique iteration: read references/render-review-iteration.md.
• YouTube long-form, Shorts, thumbnails/titles, channel packaging, disclosure, upload profiles, or retention learning: read references/channel-delivery-feedback.md.
• Load the primary reference for the current stage; when needed, the production-mode reference is its one supporting reference. Do not load every stage reference in one context or stack another supporting reference with the mode guide. Handoff compact decisions between stages. Verify changing platform rules at delivery.
• Use Creative Production or imagegen only for supporting visual exploration/assets. Preserve exact logos, product UI, typography, and copy from governed source files; composite them deterministically rather than asking generation to reproduce them.
• Product claims/copy may route to content-writer; WordPress surfaces route to the relevant WP specialist. This skill owns the video artifact and proof.

Workflow

1. Classify the work: enterprise promo/launch, explainer or software demo, long-form, Short, edit, or delivery-only. Confirm audience, one content promise, channel, duration, outcome, deliverables, and review owner.
2. Establish project, source revision/hash, sequence, job and expected output identity. For edit/review/delivery-only work, bind the supplied artifact to its existing contract; never invent missing identity.
3. Confirm approved claims, brand, product evidence, sanitized capture, media/likeness rights, accessibility, synthetic-media needs, and platform constraints.
4. Inspect references and footage; record timestamped observations, intent, reusable principles, and originality boundaries.
5. Preflight assets, rights, and capture. New narrative work needs a brief and shot-level storyboard with acceptance criteria; revisions inherit their contract. Validate a representative style sequence before scaling. Delegated direction permits internal selection/review; ask only for a requested checkpoint or unresolved material brand, claim, or scope decision.
6. Edit non-destructively from an explicit timeline and render contract. Separate product truth from metaphor; never fabricate product UI, customers, metrics, capabilities, or outcomes.
7. Deliver review render, intentional poster, manifest, accessibility assets, and relevant channel package. Validate metadata, narrative, UI truth, typography, logo, motion, audio, rights, claims, accessibility, and output identity.
8. For direct critique, apply the exact bounded change and preserve invariants. For post-publication evidence, record one hypothesis and change only its implicated packaging/edit variable. Rerender only if video changed; report proof gaps without silently changing direction.

Non-Negotiables

• Reference work is analysis, not imitation. Do not reproduce a competitor's sequence, distinctive visual identity, music, copy, or protected assets.
• No white-box logo artifacts: use the approved SVG or alpha asset, validate edges over light and dark frames, and do not redraw a brand mark with generative tools.
• Abstract-product storytelling may explain a verified problem, workflow, control, or outcome, but must not imply unshipped interfaces or unsupported claims.
• Prefer typography, hierarchy, space, timing, editorial rhythm, sound detail, and purposeful transitions over template spectacle. Premium does not mean constant movement, generic AI glow, stock-montage filler, fake customers, or kinetic text that repeats the narration.
• Real UI capture uses an identified build and role, sanitized deterministic fixtures, and consented voice/likeness; it never exposes customer data, secrets, credentials, internal URLs, or notifications.
• A polished edit cannot conceal privacy, consent, rights, accessibility, product-truth, or output-identity gaps.
• Apply the same acceptance criteria regardless of model or reasoning, not a promise of identical creativity. Repair, use permitted escalation, or report incomplete; never lower the bar or invent playback evidence. Current owner allocation overrides historical examples.
• Do not publish, release, upload, change live video metadata, start/stop/apply a public experiment, or overwrite an approved master without explicit owner approval.

Required Handoff

Report direction, project/job/output identity, render profile, paths, provenance, claims, accessibility, validation, changes, gaps, remaining approval.