/higgsfield-content-factory

name: higgsfield-content-factory
description: "Use when the user wants to run a full ad-campaign pipeline on top of Higgsfield Marketing Studio — 'create a campaign', 'build a content plan', 'run the content pipeline', 'generate 100 UGC videos', 'plan and schedule a launch', 'make a batch of ads from my product', or 'how much did this save vs traditional production'. Covers the 5-stage orchestration (Research → Plan → Generate → Publish → Report), the UGC-first 5-format campaign mix (UGC Entertainment, Street Interview, Unboxing, Product Review, ASMR), the even-split allocation math, button-driven onboarding, the per-batch generation gate, and the publish + cost-report tail (satellite). Defers all Marketing Studio API ground-truth (presets, params, hooks, avatars) to higgsfield-marketing-studio."
user-invocable: true
metadata:
  tags: [higgsfield, content-factory, campaign, pipeline, orchestration, ugc, marketing-studio, content-plan, batch-generation, ad-campaign]
  version: 1.0.0
  updated: 2026-06-03
  parent: higgsfield

Higgsfield Content Factory — Campaign Orchestration Pipeline

<!-- CONTENTS — generated by scripts/build_index.py; do not hand-edit --> **Contents**

• [1. Two operating principles](#1-two-operating-principles)
• [Stage banners](#stage-banners)
• [2. Onboarding — one message, all buttons, no pauses](#2-onboarding--one-message-all-buttons-no-pauses)
• [3. The campaign mix — 5 UGC formats (even split)](#3-the-campaign-mix--5-ugc-formats-even-split)
• [Format → preset routing](#format--preset-routing)
• [Concept seeds (vary within each format)](#concept-seeds-vary-within-each-format)
• [ASMR is a style, not a preset](#asmr-is-a-style-not-a-preset)
• [4. Stage 1 — Trend research & viral ideas](#4-stage-1--trend-research--viral-ideas)
• [5. Stage 2 — Video content plan](#5-stage-2--video-content-plan)
• [6. Stage 3 — Generate in Marketing Studio](#6-stage-3--generate-in-marketing-studio)
• [Escape hatch — ideas Marketing Studio can't render](#escape-hatch--ideas-marketing-studio-cant-render)
• [7. Stages 4–5 — Publish & report](#7-stages-45--publish--report)
• [8. Hard rules (consolidated)](#8-hard-rules-consolidated)
• [9. Source acknowledgment](#9-source-acknowledgment)

<!-- /CONTENTS -->

A 5-stage pipeline that runs a full ad campaign on top of Higgsfield Marketing Studio: **Research → Plan → Generate → Publish → Report.** Where `higgsfield-marketing-studio` is the *engine reference* (what the presets, parameters, hooks, and avatars are), Content Factory is the *orchestration layer* that drives a whole campaign turn by turn — researching trends, planning a dated content calendar, generating in batches, scheduling to ads, and reporting cost savings.

Translated from Adil Aliyev's `higgsfield-content-factory` source skill, per the v3.7.13 / v3.7.16 translation precedent. **All Marketing Studio API ground-truth — preset slugs, parameter schema, hook/setting/avatar handling — lives in `../higgsfield-marketing-studio/SKILL.md` and is NOT restated here.** This sub-skill carries the pipeline scaffolding the marketing-studio sub-skill deliberately deferred. The publish + cost-report tail (Stages 4–5) lives in the companion `publish-and-report-workflow.md` satellite.

---

1. Two operating principles

**Content is UGC-first.** Every campaign defaults to a heavy share of UGC-family content — talking-head clips, honest reviews, ASMR close-ups, unboxing reveals. Hyper Motion, TV Spot, and Wild Card stay available but off the default mix. Every video idea must be producible inside one live Marketing Studio preset within its duration cap (see marketing-studio § 3 / § 7 for the canonical preset list and limits).

**The interaction is button-driven.** Every clarifying question is asked as a 2–4 option button choice (one round-trip), never a free-form "type your answer" for navigation, confirmation, or routing. Free-form typing is reserved for content the user must originate — and even then, always offer a smart default they can accept with one click. The only non-button steps are attaching a product image or pasting a product URL (both click-based file actions).

> **User-facing language rule (HARD).** The user is not a developer. Do not > narrate technical mechanics — no MCP tool names, no UUID resolution, no > "running parallel searches," no enhanced-prompt internals. All of that runs > silently. Send one plain-language stage banner when each stage starts, a > brief "Stage N done — [deliverable]" between stages, then the next banner. > The user sees a clean narrative arc, not a tool log. If the user asks "how > does it work under the hood," then explain.

Stage banners

Send one banner per stage, in plain language (no tool names):

| Stage | Banner | |---|---| | 1 | **🔍 Research & ideas — starting now.** Scanning what's trending this week in your niche across Instagram, TikTok, and YouTube, then turning it into 15+ viral video ideas for your brand. | | 2 | **🗂️ Content plan — starting now.** Building your full video content plan as a polished document, every video mapped, dated, and ready to generate. | | 3 | **🎬 Generating videos — starting now.** Producing your videos in Marketing Studio, one preset at a time. I'll ask before each batch fires, so you stay in control. | | 3 (images) | **🖼️ Image asset pack — starting now.** Generating your social posts, hero banners, and product stills via GPT Image 2.0. | | 4 | **📅 Scheduling to ads — starting now.** Setting up campaigns and scheduling across the calendar you approved. | | 5 | **💰 Cost report — starting now.** Compiling what you spent on Higgsfield versus what this volume would cost the traditional way. |

---

2. Onboarding — one message, all buttons, no pauses

Ask the onboarding questions in a **single** button round-trip at the start. Do not ask them sequentially; do not pause between onboarding and the product request.

• **A — Higgsfield connection:** "Yes — connected" · "Not yet — I'll