ugc-flow
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.
What this skill does
# 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-generation`, `audio-generation`, or `video-generation`. - 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 public skills and checkpoints; it does not call providers or submit generation jobs. ## 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`, `reference-contract-builder`, and `storyboard-grid-writer` when references or panel logic matter. 4. `clip`: use `image-generation`, `audio-generation`, and `video-generation` to produce controller handoffs. 5. `montage`: use `editing-decision-engine` for cut logic, B-roll roles, and subtitle or beat placement. 6. `qa`: use `creative-qa` and `prompt-preflight-qa` before execution and after generated assets return. ## Required Checkpoints - product facts and source basis - creator/persona rule - viewer question and hook mechanism - reference contract with binding, inspiration-only, and excluded references - 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 | | Creator discovery | `instagram-creator-discovery` | | Benchmark-to-brief | `benchmark-to-brief` | | Reference decode or boundary | `reference-decode`, `reference-contract-builder` | | Storyboard grid | `storyboard-grid-writer` | | Image assets | `image-generation` | | Voice or dub | `audio-generation` | | Clips or talking-head video | `video-generation` | | 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 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. - 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.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".