Popiai-skill/content-creation/skill-creator/references/SKILL-TEMPLATE.md

name	description
<skill-name>	<One-sentence summary of what this skill does>. <Elaboration on the workflow: input -> key transformations -> output>. Use whenever the user wants to <trigger phrase 1>, <trigger phrase 2>, or <trigger phrase 3>.

When the user wants to , follow this workflow.

PRE: OBTAIN HILO TOKEN

Before starting the workflow, obtain the Hilo API token via MCP:

1. Call MCP get_token, store the returned access_token.
2. This token will be used in subsequent video generation steps (Hilo/Official).
3. Token lifetime: If the workflow is long-running (>30 min), check token expiry before each API call and refresh if needed.

Why obtain early: Getting the token upfront avoids interrupting the creative flow mid-workflow. If auth fails, the user knows immediately -- rather than after expensive generation steps have already run.

STEP 0: CHECK RESOURCES

1. <Required input 1>: If not provided, ask the user to provide one or .
2. <Required input 2>: Ask the user: "".
3. : If user specifies , do first.
4. Get from the input (e.g., duration, dimensions, format).

STEP 1: ANALYZE INPUT

Analyze the input to understand:

• <Dimension 1> (e.g., mood, style, structure)
• <Dimension 2> (e.g., content breakdown, sections)
• <Dimension 3> (e.g., technical properties)

Use this analysis throughout the workflow:

• Step 2: Guide
• Step 3: Determine

STEP 2: GENERATE PLAN / SCRIPT

Generate a complete <plan/script/storyboard> that includes:

(e.g., Characters, Themes, Sections)

{
  "<id_field>": "<unique_id>",
  "<name_field>": "<display name>",
  "<prompt_field>": "<generation prompt or description>"
}

• <Rule 1>: --
• <Rule 2>: --

(e.g., Scenes, Layouts, Segments)

{
  "<id_field>": "<unique_id>",
  "<timing_fields>": "<start/end or ordering>",
  "<content_field>": "<what happens>",
  "<reference_fields>": "<links to Component A>"
}

Timing / ordering rules:

• : e.g., segments must be continuous, no gaps
• : e.g., each segment 3-15 seconds
• : e.g., 7-10 seconds per segment -- fewer, longer segments produce more coherent results

Type / category rules:

• <type_1>: <when to use, what it means>
• <type_2>: <when to use, what it means>

Ratio / balance rules:

• : e.g., ~60% type_1, ~40% type_2 by total duration
• : e.g., never place two <type_2> segments back-to-back

Validate

After generating the plan, validate it:

• <Validation check 1>
• <Validation check 2>
• Fix all errors and re-validate until passed.

STEP 3: GENERATE ASSETS

Generate all in one batch:

1. <Asset category 1> (e.g., character images): Use each item's <prompt_field>. : <value>.
2. <Asset category 2> (e.g., scene images): Use each item's <prompt_field>. : <value>.

Include ALL prompts in one task to minimize round-trips.

Pitfall: Do NOT -- .

STEP 4: CONFIRM WITH USER

Present all generated assets to the user. Ask if any need adjustments. Regenerate as needed.

STEP 5: MAIN PRODUCTION

Step 5a: Prepare (batch)

For each , prepare its :

• <How to compose/transform the asset>
• : <value> --

Batch: Process ALL items in one call, then proceed to 5b.

Step 5b: Generate (batch)

Generate for all items:

• : from Step 5a
• :

Model selection: <Which model/tool to use and why>.

Duration / size strategy: :

• <Condition 1> ->
• <Condition 2> ->

Step 5c: Adjust / Post-process

Adjust every output to match its target specification:

Case 1: ->

Case 2: ->

Verification: After adjusting all outputs, verify the total matches expectations. If drift exceeds , fix before proceeding.

Step 5d: Generate (different technique)

For , use because .

Sub-step 1: Prepare inputs for this subset. Sub-step 2: Generate in one batch call. Sub-step 3: Post-process to match target specs.

STEP 6: FINAL ASSEMBLY

Assemble the final output:

• <Input 1>: ALL produced outputs in order
• <Input 2>: Original source material (e.g., audio track)
• <Input 3>: Metadata (e.g., credits, annotations)

STEP 7: PRESENT RESULT

Show the final output to the user with a summary:

• (e.g., source info)
• (e.g., asset counts, techniques used)
• <Output path / location>