Video Generation

Indexed Reference Map

• @[SKILL.md#L1-L92] Frontmatter, scope, KB notes, trigger rules, SOP, error handling, output contract.
• @[references/INDEX.md#L1-L11] Reading order and file map.
• @[references/QUICK_REFERENCE.md#L1-L20] Trigger boundary, approval split, and stop conditions.
• @[references/CORE_API.md#L1-L40] Prompt package contract, helper/API behavior, polling, and privacy boundary.
• @[references/PATTERNS.md#L1-L13] Prompt-shaping and reference-image handling patterns.
• @[references/EXAMPLES.md#L1-L15] Representative video requests and handling.
• @[references/AI_WORKFLOW.md#L1-L14] Bounded orchestration flow.
• @[scripts/generate.py#L1-L94] Imported external video-generation helper.

Scope

• In-scope:
  • structure video-generation prompts from user intent
  • organize optional reference-image inputs
  • prepare prompt files/specs for later generation
  • execute the imported helper only when external API use is approved
• Out-of-scope:
  • blind execution of upstream helper without review/approval
  • pretending a video was generated when only a prompt draft exists
  • downloading/searching reference media unless separately requested and approved

KB Mode Notes

• Reading order:
  1. references/INDEX.md
  2. references/QUICK_REFERENCE.md
  3. references/CORE_API.md
  4. references/PATTERNS.md
  5. references/EXAMPLES.md
  6. references/AI_WORKFLOW.md
  7. scripts/generate.py
• Coverage Matrix:
  • trigger boundary + approval split -> QUICK_REFERENCE.md
  • prompt package + helper/API/polling contract -> CORE_API.md
  • prompt engineering and reference handling -> PATTERNS.md
  • representative use cases -> EXAMPLES.md
  • orchestration order -> AI_WORKFLOW.md
• Portability note:
  • Local governance treats the helper as an external API adapter with long-running polling; re-check endpoint, auth, timeout, and download policy before porting.

Trigger Rules

• Positive:
  • The user explicitly wants a video clip, short scene, animated sequence, or generation-ready video prompt package.
  • A structured prompt package is needed for later video generation.
• Negative:
  • The task is only ideation without any prompt/package need.
  • The request is primarily about local video editing rather than AI video generation.
  • External API upload/generation is disallowed and prompt-only output would not satisfy the request.
• Escalation:
  • If execution would upload prompt/reference content to an external API or download generated media, obtain approval first.
  • Without approval, return the structured prompt package and execution notes only.

SOP

1. Confirm the user wants AI video generation or a generation-ready prompt package.
2. Extract subject, scene progression, camera, style, lighting, duration cues, and optional reference-image role.
3. Build a structured prompt/package in English unless the target workflow explicitly requires otherwise.
4. Validate that prompt details are traceable to user instructions; do not invent hidden story beats.
5. If approved and prerequisites exist, invoke the helper.
6. Otherwise, return the prompt/spec package and state that execution was deferred.
7. Report actual output artifact path or explicit deferral.

Error Handling

• Missing creative requirements:
  • ask for minimum missing details or provide a bounded prompt draft with assumptions labeled.
• Missing/invalid reference image:
  • exclude it and state the effect on generation.
• Missing API credential/runtime dependency:
  • stop at prompt-package output; do not fake execution.
• API/polling/download failure:
  • report the real failure and keep the prompt package for retry.

Output Contract

• Deliverables:
  • structured prompt/package
  • reference-image usage or deferral note
  • actual output path only if video generation succeeded
• Validation:
  • no fabricated generated artifact
  • no silent external upload/download
  • prompt details remain faithful to user intent
• Compliance Verdict:
  • PASS when prompt structure is sound and execution/deferral is reported truthfully.