skills/marketing/hormozi-ad-factory/SKILL.md
Generates 150-750+ ad variations using Alex Hormozi's combinatorial Hook x Meat x CTA framework. Triggers on requests to create ads, ad copy, ad scripts, marketing creatives, video ad scripts, ad hooks, CTAs, ad testing, ad scaling, or ad factories. Also triggers on mentions of Hormozi's ad method or combinatorial ad creation. Does not trigger for general copywriting, email marketing, landing pages, or non-advertising content.
npx skillsauth add pedronauck/skills hormozi-ad-factoryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A systematic framework for generating 150-750+ unique ad variations from a single product or offer, based on Alex Hormozi's combinatorial ad creation method.
Ads consist of three modular parts: Hook, Meat, and CTA. Instead of writing one ad at a time, generate each component independently, then combine them:
This approach creates massive variety for testing, which is what wins at scale.
Execute the following four steps in order. Before starting, gather context from the user.
Before generating any ad components, ask the user these questions (skip any the user has already answered):
If the user provides minimal context, infer reasonable defaults and state the assumptions clearly before proceeding.
Hooks are the first 1-3 seconds (video) or first line (text) of the ad. They stop the scroll and earn attention. Use these five sourcing methods to create variety:
Distribute the 50 hooks across awareness levels to cover different audience segments:
| Level | Description | Hook Style | |-------|-------------|------------| | Unaware | Does not know they have a problem | Pattern interrupt, curiosity, shock | | Problem-Aware | Knows the problem, not the solution | Call out the pain, frustration, desire | | Solution-Aware | Knows solutions exist, has not chosen one | Compare approaches, reveal flaws in alternatives | | Product-Aware | Knows the product, has not bought | Overcome objections, social proof, urgency | | Most Aware | Knows the product well, needs a push | Deals, bonuses, scarcity, direct offer |
Default to a balanced spread (~10 hooks per level) unless the user specifies a focus.
For hook formula templates and examples, read references/hook-formulas.md.
The meat is the body of the ad — it educates the audience on the offer, the product, the solution, or the problem. Generate one meat per format:
Each meat must be self-contained and work with any hook and any CTA.
For detailed meat structures and length guidelines, read references/meat-formats.md.
The CTA tells the viewer exactly what to do next. A strong CTA includes up to five elements:
Not every CTA needs all five, but the best ones cover most of them.
For CTA templates and examples, read references/cta-templates.md.
After generating all components, combine them into a matrix. Present the output as:
For the full output format template, read assets/output-template.md.
Adapt the format of each component based on the target platform:
| Platform | Hook | Meat | CTA | |----------|------|------|-----| | Video ads (TikTok, YouTube, Reels) | Opening line/scene (1-3s) | Script section with visual directions (15-45s) | Closing sequence with on-screen text | | Text/copy ads (Facebook, LinkedIn) | Headline or opening line | Body copy paragraphs (3-8 sentences) | Closing paragraph with link | | Carousel ads (Instagram, LinkedIn) | Slide 1 | Slides 2-8 | Last slide | | Short-form (Twitter/X, Stories) | Single punchy line | 1-3 sentences max | Inline CTA |
User: "Generate ads for my project management tool aimed at remote teams."
Process:
User: "Crie anuncios para meu curso de culinaria online para iniciantes."
Process:
User: "I need some ad ideas for my coaching business."
Process:
development
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
tools
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
tools
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.