The argument in one line.
By connecting Higgsfield's AI media generation to Claude via CLI and building reusable skills, you can automate a complete creative production pipeline that ideates, generates, and tracks hundreds of ad variants weekly without manual work.
Read if. Skip if.
- A solopreneur or small agency owner with basic Claude experience who wants to automate product photography, ad variants, and video generation without hiring a production team.
- A marketer or founder running 2-5 brand launches per year who's comfortable with CLI tools and wants to compress weeks of creative work into hours using AI.
- Someone already using Claude regularly who has a Higgsfield account and wants to see a concrete workflow for scaling from chat-based prompts to scheduled, autonomous content production.
- You need photorealistic human talent, complex narrative storytelling, or brand work that requires client feedback loops — this focuses on product-forward, motion-driven outputs.
- You're not comfortable with command line interfaces or don't have time to set up custom Claude connectors and Google Sheet integrations.
- You work in highly regulated industries (pharma, finance, legal) where AI-generated creative carries compliance risk or requires human approval before deployment.
The full version, fast.
Higgsfield's CLI plus Claude turns one operator into a creative agency that researches a brand, builds a product catalog, and ships image and video ads on a schedule. The mechanism is a three-layer stack: connect Higgsfield to Claude via a custom connector for quick one-prompt generation, then graduate to Claude Code with the Higgsfield CLI, the Google Workspace CLI, and a research markdown file that injects copywriting expertise the model lacks. Inside that project, a Google Sheet logs every generation, a creative slate matrix mixes variables across angles and platforms, and reusable skills lock in winning recipes like hypermotion product videos. Scheduled routines then ideate on Sundays and generate overnight, so you wake to hundreds of ready ad variants for testing.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open + promise wall
Promise stated (Claude + Higgsfield = scale-up creative agency) and proven by walling up five-minute outputs: Murmur headphone ads, Sleep Support bottle ads, hyper-motion videos. Sets the bait: 'all of this from one prompt.'

02 · Connect Higgsfield to Claude.ai (custom connector / MCP)
Walks through claude.ai → Settings → Connectors → Add custom connector. Paste the Higgsfield MCP URL, OAuth in, set permissions. Demonstrates the connector is live and ready to prompt against.

03 · One-prompt brand generation in Claude.ai
Single prompt: 'Build me a headphone brand from scratch — do research, branding, catalog, and for each product generate a product photo, IG ad, and UGC video via Higgsfield MCP.' Claude returns a brand called Murmur with positioning, target buyer, voice, visual identity, and three SKUs (over-ear Halo, wireless earbuds Drift, open-back wired).

04 · Review the auto-generated catalog + iterate inline
Walks the Halo / Drift / open-back outputs: product photos, Instagram ads, UGC videos. Shows how to fix mistakes by replying in-thread ('two headers — remove one'), how 'Animate' takes the same prompt graph into a video, and what the video model gets right (realism) vs wrong (duplicated text).

05 · Marketing Studio: hyper-motion launch video
Asks Claude to use Higgsfield's Marketing Studio to make a launch video for the Halo. First pass is too quiet/intimate; second pass with 'hyper-motion variant, 16x9, more engaging' lands the cinematic ad seen in the intro. Brief detour about a 'sensitive content' block and how to debug the prompt with Claude.

06 · Second product run: Sleep Support from a reference image
Drops in an existing product photo (blue Sleep Support bottle), asks for Instagram-ready ads. First pass loses the on-bottle text — lesson surfaced: 'be more specific about telling it not to change the reference image.' Iterates to ads with headlines like 'Asleep in 12 minutes' and 'Stop counting sheep — start sleeping through the night.'

07 · Pivot to Claude Code (desktop) for power features
Why move off claude.ai: more control, reusable skills, true automations. Important nuance — not the CLI terminal, the Claude Code desktop app: still has chat + project, with skills/files/routines layered on top. Sets the scene for the Claude Code build-out.
08 · Install the Higgsfield CLI + agent skills
Open a blank folder ('Higgsfield Studio'). Grab three commands from Higgsfield > MCP & CLI: install CLI, run hf auth (browser OAuth), install Higgsfield agent skills. Paste all three into Claude Code in one prompt, let it run. Side-explainer: CLI > MCP for token cost and agent efficiency.
09 · Bring in outside expertise as a research markdown
Pre-built advertising_masterclass.md (617 lines) via a deep-research prompt: best organic ad strategies for 2026 across TikTok / Meta / X, what captures attention, what converts, platform differences. Lives in the project so agents reference it when ideating. Joe-relevant: 'utilize other people's expertise' — swipe-file thinking.
10 · Master Sheet: log every Higgsfield generation via GWS CLI
Asks Claude to read all 45 assets from the Higgsfield account and write them into a Google Sheet (tabs: generations, by product, by style, planning). Builds a creative-ops database — product, style, image/video, model, prompt, status, result URL, job ID. GWS CLI is the unlock: lets the agent move across Sheets/Docs/Gmail/Calendar/Drive without MCP overhead.
11 · Test matrix: 30+ variants ideated from masterclass + data
@-tags advertising_masterclass.md and the existing generations, asks Claude to mix-and-match variables (header, style, content type) into testable variants. Sheet gets a new 'creative slate' tab with priority-ranked ideas across products. Frames the philosophy: 'we’re not the bottleneck on creativity or production anymore.'
12 · Generate rows 3–7 + add status tracking
'Create prompts for rows 3-7, add a status column, generate them in Higgsfield, then mark them complete on the sheet.' Sponsor break for Glido (Nate is joining the Glido team, switched from Whisper). When the batch returns, the Sleep Support bottle drifts off-brand because the reference wasn’t locked.
13 · Lock the brand asset + regenerate
Drags the canonical Sleep Support product image directly into Claude Code: 'every advertisement must show the product exactly like this — same color, same text, don’t change anything.' Regenerates. New batch comes back consistent and on-brand, mixing nano-banana-2 and gpt-image-2 across angles (curiosity, contrarian, pattern interrupt, stat flash).
14 · Skills: reverse-engineer a recipe from a winning prompt
Definition: a skill is a recipe for an agent (the pancake analogy). Workflow: find a generation you love, copy its exact prompt back into Claude, say 'turn this prompt into a skill that lives in .claude/skills so anytime I ask for a hyper-motion video you use this.' Highlights the meta-loop: bake learned constraints (e.g. words that get flagged for sensitive content) into the skill so the agent improves over time.
15 · Invoke the new skill on the locked reference
@-tags the saved Sleep Support reference plus tries /hypermotion. First run uses the wrong skill (default higgsfield_generate). Restarts the Claude Code session; new run reads the .claude/skills/HyperMotion-Video file, asks the right clarifying question ('model in the ad, UGC, or product only?'), and produces the cinematic hyper-motion clip he wanted.
16 · Output review + honest critique
Output is strong — cinematic feel, real-looking product — but the label text is mangled in image-to-video. Nate names the limitation directly: 'this is the worst AI video generation will ever be,' suggests a workaround (simpler label for hero shots), and pushes back on knee-jerk 'AI slop' framing.
17 · Routines: schedule the agency to run while you sleep
Claude Code Routines inject prompts on a cadence. The proposed pipeline: Sunday night routine — analyze the Sheet + platform data, add 50 new generation ideas. Monday morning routine — pick 30 blank-status rows, generate, mark complete. Scale to twice-weekly planning + generation. Optional final step: pipe winners into Potato or Meta Ads Manager for full auto-posting. CTA: like + watch the routines deep-dive.
Lines worth screenshotting.
- Connecting Higgsfield to Claude via MCP turns a brand brief like 'build me a headphone brand' into a full product catalog with photos, Instagram ads, and UGC videos from one prompt.
- The difference between using Higgsfield manually and routing it through Claude is the difference between one-off content and a consistent, repeatable, automated creative pipeline.
- Claude Code with a Google Sheets ad-test matrix and a Higgsfield skill can ideate and generate ad variants while you sleep — turning what used to be a creative agency's week into an overnight routine.
- Iterating on a generated image inside Claude by saying 'remove the duplicate header' is faster than reopening the design tool because the agent already knows the exact reference image.
- Higgsfield's Marketing Studio hypermotion format produces AI video ads that would have required a studio, a paid actress, and days of editing to achieve with traditional production.
- Adding the Higgsfield CLI to a Claude Code project means every future agent in that project inherits the ability to generate images and videos without additional configuration.
- The one-prompt creative agency pattern — research brand, build catalog, generate all assets — is a replicable template that scales to any product category without changing the underlying workflow.
One prompt, a CLI, and a scheduled creative agency
Connecting an image-and-video generation tool to an AI coding environment via a command-line interface — rather than a browser MCP — unlocks reusable skills, a tracking spreadsheet, and overnight generation routines that run without you.
- A single prompt can trigger a full brand build — research, branding, catalog, and visual assets — when the AI tool has an image-generation connector attached.
- Adding a custom connector through the AI tool's settings and completing an OAuth flow is the entire setup required to enable image and video generation from chat.
- Connector permissions can be scoped after setup — either allow all actions or restrict to specific operations depending on how much trust you want to extend.
- A single high-level prompt — 'build me a brand, generate the catalog, produce assets for each product' — can delegate an entire creative production run when the tool has the right connectors.
- The model will make creative decisions (naming, positioning, target buyer, SKUs) from minimal input — the value is in the iteration, not the initial specification.
- Iterating on generated assets is done inline by replying to the same thread, not by starting over — fixing a duplicated header or changing an aspect ratio is a one-sentence follow-up.
- The Animate button in the tool takes a static image prompt graph and extends it into a video using the same prompt — no separate video prompt is needed for a basic animation.
- When a generation is flagged for sensitive content, asking the agent to surface the exact prompt, identify the problematic phrases, and regenerate without them is faster than guessing what triggered the block.
- Emotional, high-level terms like 'hyper-motion,' 'engaging,' and 'fast-paced' translate effectively into technical prompts when the underlying model has been trained on those aesthetic patterns.
- Being explicit about preserving a reference image is required; without that instruction, the model will interpret the image loosely and alter product labels, colors, and text.
- Moving from a browser chat to a desktop coding environment adds project files, reusable skills, and scheduled routines — the chat interface is still present, but the agent gains persistent memory and automation support.
- A browser-based MCP connector is quick to set up but costs more tokens and is less efficient for agents; a CLI integration is faster, cheaper, and better suited for automated workflows.
- Installing the CLI, authenticating, and loading agent skills can all be done in a single prompt by pasting the three required commands and letting the agent execute them.
- A subject-matter research document pulled from deep AI research and stored in the project gives every agent access to advertising best practices without requiring the agent to rediscover them from scratch.
- Using proven external expertise — Twitter threads, YouTube videos, research tools — embedded as a project file is the fastest way to raise the floor on AI-generated output quality.
- Logging all generated assets into a structured spreadsheet — product, style, model, prompt, status, result URL — creates a creative-ops database that agents can query and build on.
- A spreadsheet CLI that gives agents read-write access to Sheets, Docs, Gmail, and Drive is more token-efficient than a stack of separate API integrations.
- A test matrix of 30 or more variants, generated from mixed variables (headline, style, content type, avatar), means the bottleneck on both creativity and production has been removed.
- Referencing both the research document and the existing generation history in the same prompt lets the agent mix data-backed best practices with what you have already tested.
- A status column on the spreadsheet prevents duplicate generation by letting the agent filter for blank rows before starting a new batch.
- Without a locked reference image, the agent will use whatever description it infers from context — which drifts from the actual product with each generation.
- Locking a canonical product image as a project asset and referencing it explicitly in every prompt is what keeps brand consistency across a large batch of generated outputs.
- Different model choices (nano-banana-2 vs. gpt-image-2) within the same batch produce different aesthetic results — letting the agent vary the model is a way to test outputs without additional prompting.
- A skill is a reusable recipe for an agent — built by reverse-engineering a prompt that produced a winning output, then saving it so future runs always start from that baseline.
- Skills improve over time by feeding the agent feedback after each run: 'I liked A and C, I did not like B — update the skill accordingly.'
- Sessions must sometimes be restarted after a new skill is created before the agent will recognize and invoke it correctly.
- A well-written skill asks a clarifying question before generating — 'product only, UGC, or model in the ad?' — rather than making that decision silently.
- Current image-to-video models reliably produce cinematic feel and realistic motion, but consistently mangle text overlays — simplifying the label on hero shots is a practical workaround until models improve.
- A Sunday planning routine adds 50 new ideated rows to the spreadsheet; a Monday generation routine picks 30 blank-status rows and produces them — together they create a self-refilling creative pipeline.
- Connecting the generation pipeline to an ad-buying platform as a final step enables fully autonomous posting once you trust the outputs enough to let them run without review.
Terms worth knowing.
- Higgsfield
- An AI-powered platform for generating and animating product images and videos — offering multiple generation styles including HyperMotion, UGC, and cinematic formats — accessible via a web interface, MCP connector, or command-line interface (CLI).
- MCP connector
- A standardized integration that allows an AI assistant like Claude to communicate directly with an external application — enabling the AI to trigger actions, retrieve data, and control the app as part of a conversation or automated workflow.
- CLI (command-line interface)
- A text-based tool installed on a computer that allows software to be controlled by typing commands into a terminal — preferred over MCP connectors for AI agents because it is faster, uses fewer tokens, and is more efficient for automation.
- HyperMotion (Higgsfield)
- A Higgsfield generation style that produces fast-paced, high-energy product videos with rapid cuts, slow-motion inserts, and cinematic close-ups — designed to capture attention quickly in social media ad placements.
- marketing studio (Higgsfield)
- A Higgsfield feature that accepts a product image or URL and converts it into a formatted ad video — offering styles like HyperMotion, UGC, and unboxing — without requiring the user to assemble individual shots or transitions manually.
- GWS CLI
- A command-line interface for Google Workspace that lets AI agents read and write Google Sheets, Docs, Gmail, Drive, and Calendar — enabling automated workflows that create, update, and query Google documents without browser-based interaction.
- ad test matrix
- A structured grid of advertisement variants — each combining different value propositions, headlines, audience angles, visual styles, and formats — designed to systematically test which combinations produce the highest conversion rates.
- skill (Claude Code context)
- A reusable, project-specific markdown file that gives an AI agent a precise recipe for completing a recurring task — ensuring consistent outputs by defining what to do, what to ask, what models to use, and what rules to follow every time the task is invoked.
- routine (Claude Code context)
- A scheduled, time-triggered prompt that automatically starts a Claude Code agent workflow at a set cadence — used to automate repeating tasks like weekly creative generation or data analysis without manual intervention.
- reference image
- A source photo or graphic provided to an AI image or video generation model to anchor the visual output — instructing the model to preserve specific product colors, shapes, text, and branding elements rather than generating them from scratch.
- UGC (user-generated content) ad style
- An advertisement format designed to look like organic content created by a real user rather than a professional studio — typically featuring a person casually reviewing or using a product, intended to feel authentic and reduce viewer skepticism.
- Gliddo (Glido)
- An AI-powered voice dictation tool that converts speech to text in real time — positioned as a faster, more private alternative to Whisper-based tools, used here for hands-free narration during screen recordings.
Things they pointed at.
Lines you could clip.
“We can ideate and we can generate a hundred times faster than the average human could.”
“We're pulling the lever on the slot machine, which is AI. If we don't have guidelines, if we don't have recipes — skills — then they're not gonna be super consistent.”
“A skill is essentially a recipe for an AI agent.”
“This is the worst that AI video generation models will ever be. Every day, every month, they're going to get better.”
“I could set an agent off to generate all this stuff, and then I could go to bed, and I could wake up with a 100 different ad copies and creatives ready to go.”
“We're not the bottleneck on creativity, and we're also not the bottleneck on production.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Nate Herk opens with the promise stated as a fait accompli: Higgsfield has every state-of-the-art image and video model, Claude knows how to talk to it, and together they ideate and generate 'a 100 times faster than the average human could.' Then he immediately cuts to a wall of finished ads — headphone halos, sleep-supplement bottles, hyper-motion launch videos — generated 'in literally five minutes with one prompt.' Promise + proof, in the first thirty seconds.
Named ideas worth stealing.
MCP vs CLI for Agents
MCP exposes every tool by default — token-heavy. The CLI is the lean alternative: same capabilities, faster, cheaper, better for agents that loop. Default to CLI when wiring tools into Claude Code; reserve MCP for ad-hoc claude.ai exploration.
Skill = Recipe (pancake analogy)
A skill is to an AI agent what a recipe is to a cook: lock the inputs, ordering, and constraints so output stays consistent run-over-run. Bake in negative constraints too (words that triggered moderation flags, brand assets that must lock).
Reverse-engineer a skill from a winning prompt
- Generate 5+ variants of a creative
- Pick the 1–3 outputs you actually love
- Copy the exact prompt that produced them
- Paste back into a fresh chat and say: 'turn this into a skill in .claude/skills so anytime I ask for X, use this'
- Iterate the skill every run — tell it what you liked/didn't and have it self-update
Don’t write skills from scratch — mine them from outputs that already worked. Outputs first, recipes second.
Bring outside expertise into the project as Markdown
Don’t expect the base model to be a master copywriter. Run a deep-research prompt against Twitter threads / YouTube / Perplexity / books, save the result as `advertising_masterclass.md` in the project, then @-tag it whenever you ideate. The model now has subject-matter expertise on tap.
Master Sheet + status column = creative ops database
- Tabs: generations, by-product, by-style, planning, creative slate
- Columns: product, style, image/video, model, prompt, status, result URL, job ID
- Status drives which rows the next routine picks up
- Sheet is queryable by the agent for analysis later
One source of truth makes the rest of the automation possible. The status column is the glue — it’s what stops agents from duplicating work across routine runs.
Routines: ideate Sunday → generate Monday
- Sunday 9pm — 'analyze sheet + platform data, add 50 new generation ideas with empty status'
- Monday 8am — 'pick 30 blank-status rows, generate prompts + assets, mark complete'
- Add Thursday/Friday as a second cycle to double throughput
- Optional: pipe completed assets to Potato or Meta Ads Manager for posting
Two cron-style prompts and you have an autonomous ad-generation loop. The cadence (Sun plan / Mon execute) prevents the agent from generating against stale ideas.
How they asked for the click.
“If you guys wanna dive a little bit deeper into routines, I'll tag a full video right here where I dive into how you set them up… if you guys enjoyed, please give it a like.”
Soft CTA — anchors on the next-video tag for routines and a like ask. No newsletter push, no product (other than the embedded Glido sponsor at 20:33). Trade-off: zero conversion pressure, but also no lead capture from a 35-min watch.









































































