ugc-flow

Savant verdict: Pending analysis

Imported from the source hub; Savant's analysis is still running.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Security assessment

Scan pending.

Structure

• No license declaredConfirm you may reuse this skill before importing it into your repository.

SKILL.md

---
name: ugc-flow
description: Orchestrate the public UGC creative production line from product or research evidence through creator logic, storyboard, image/video/audio generation handoffs, montage planning, and QA. Use this when the user asks for a repeatable UGC-style ad or creator video workflow rather than one isolated media asset.
metadata:
  postplus:
    familyId: media-production
    familyName: Media and Creative Production
---

# UGC Flow

## Use When
- The user wants a UGC-style product, app, service, testimonial, or creator
  video pipeline.
- The job spans multiple steps: product analysis, creator/persona logic,
  storyboard, image or video clip generation, montage, subtitles, and QA.
- The request needs a standard production line instead of one isolated runner.

## Do Not Use When
- The user only needs one image, voice take, or simple clip. Use
  `image-batch-runner`, `voice-batch-runner`, or `video-batch-runner`.
- The user only needs transcription, subtitles, or video analysis. Use
  `media-router`.
- A provider-ready request already exists. Use the relevant runner.

## Core Boundary
This is a workflow skill. It coordinates creative stages; generation stages go
directly to their runners.

## Standard Pipeline

1. `product_analysis`: collect product facts, core promise, proof points,
   constraints, and claims that must not be invented.
2. `creator_logic`: define creator type, audience fit, native behavior, tone,
   and what the creator is allowed to claim.
3. `board`: use `reference-decode` and `storyboard-grid-writer` when reference
   analysis or panel logic materially helps.
4. `clip`: use `image-batch-runner`, `voice-batch-runner`, and
   `video-batch-runner` to create the media.
5. `montage`: use `editing-decision-engine` for cut logic, B-roll roles, and
   subtitle or beat placement.
6. `qa`: use `creative-qa` on the approved plan or returned media when review is
   actually required.

## Required Checkpoints
- product facts and source basis
- creator/persona rule
- viewer question and hook mechanism
- useful media roles and references stated directly in each generation handoff
- storyboard or beat plan
- image/audio/video controller handoffs
- runner-ready requests only after strategy is locked
- QA verdict and rerun notes

## Routing Table

| Need | Handoff |
| --- | --- |
| Product or market evidence | Instagram/Meta research or strategy skill appropriate to the product |
| Instagram account, content, audience, creator, or campaign research | `instagram-research` |
| Benchmark-to-brief | `benchmark-to-brief` |
| Reference decode or boundary | `reference-decode` |
| Storyboard grid | `storyboard-grid-writer` |
| Image assets | `image-batch-runner` |
| Voice or dub | `voice-batch-runner` |
| Clips or talking-head video | `video-batch-runner` |
| Cut logic and montage | `editing-decision-engine` |
| Final creative review | `creative-qa` |

## Output Shape
Return a workflow packet:

- `productionGoal`
- `sourceBasis`
- `creatorLogic`
- `referencePolicy`
- `storyboardOrBeatPlan`
- `generationHandoffs`
- `montagePlan`
- `qaPlan`
- `openQuestions`

## Stop Conditions
- Stop when required user intent, source evidence, or owned input artifacts are
  missing and guessing would change the result.
- Do not let runners make creative or claim decisions.
- If an owned CLI or script command still fails after any bounded recovery allowed by the executing PostPlus skill, 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 still fails after any bounded recovery allowed by the executing PostPlus skill, 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.
- This public skill is instruction-driven. Produce the workflow packet directly
  from the available evidence.
- Do not call private provider/runtime paths or unpublished local tools.
- If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.