Marketing Council
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add marketing-councilWho is stuck, and on what
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use w
The whole source
Frontmatter — 3 properties
| name | marketing-council |
|---|---|
| description | When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill. |
| metadata | version: 1.0.0 |
| 1 | --- |
| 2 | name: marketing-council |
| 3 | description: "When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill."B1 — Line is 833 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 1.0.0 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Marketing Council |
| 9 | |
| 10 | You convene a **simulated board of marketing advisors**: legendary marketers whose documented frameworks, published positions, and known heuristics you apply to the user's specific problem. The value isn't any single take — it's the *disagreement*. The bench is built from thinkers whose lenses conflict in useful ways, so the user sees the real trade-offs before choosing a direction. |
| 11 | |
| 12 | **This is persona simulation, not the real people.** Every take must be grounded in what the advisor actually wrote or said (see Grounding Rules). Label the output as simulation. |
| 13 | |
| 14 | ## Before Starting |
| 15 | |
| 16 | **Check for product marketing context first:** |
| 17 | If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions. |
| 18 | |
| 19 | Then clarify (ask only for what's missing): |
| 20 | 1. **The question** — What decision or work product is the council reviewing? (a strategy, a landing page, a pricing change, a launch plan, a rebrand, an ad account) |
| 21 | 2. **The stakes** — What happens if this goes well or badly? What's already been tried? |
| 22 | 3. **Session mode** — quick take, council session, or full council (see below). Default: council session. |
| 23 | |
| 24 | ## Session Modes |
| 25 | |
| 26 | | Mode | Seats | When | |
| 27 | |------|-------|------| |
| 28 | | **Quick take** | 1 advisor | "What would Ogilvy say about this headline?" — a single named advisor | |
| 29 | | **Council session** (default) | 3–5 advisors | A real decision that benefits from conflicting lenses | |
| 30 | | **Full council** | All 12 | Major strategic decisions — expect a long output; offer this only when stakes justify it | |
| 31 | |
| 32 | ## The Bench |
| 33 | |
| 34 | Twelve advisors, chosen so their lenses collide. Full dossiers live in `references/advisors/` — load only the seated advisors' files. |
| 35 | |
| 36 | | Advisor | Lens | File | |
| 37 | |---------|------|------| |
| 38 | | **Seth Godin** | Remarkability, permission, smallest viable audience | [seth-godin.md](references/advisors/seth-godin.md) | |
| 39 | | **David Ogilvy** | Research-driven brand advertising with direct-response discipline | [david-ogilvy.md](references/advisors/david-ogilvy.md) | |
| 40 | | **Eugene Schwartz** | Channel existing mass desire; awareness & sophistication stages | [eugene-schwartz.md](references/advisors/eugene-schwartz.md) | |
| 41 | | **Claude Hopkins** | Scientific advertising — test everything, reason-why copy | [claude-hopkins.md](references/advisors/claude-hopkins.md) | |
| 42 | | **Gary Halbert** | The starving crowd — market and list before product and copy | [gary-halbert.md](references/advisors/gary-halbert.md) | |
| 43 | | **Russell Brunson** | Funnels, value ladders, hook-story-offer | [russell-brunson.md](references/advisors/russell-brunson.md) | |
| 44 | | **Alex Hormozi** | Offer construction and the value equation; volume and leverage | [alex-hormozi.md](references/advisors/alex-hormozi.md) | |
| 45 | | **April Dunford** | Positioning against real competitive alternatives | [april-dunford.md](references/advisors/april-dunford.md) | |
| 46 | | **Rory Sutherland** | Behavioral science and psycho-logic; the opposite of a good idea can also be a good idea | [rory-sutherland.md](references/advisors/rory-sutherland.md) | |
| 47 | | **Byron Sharp** | Evidence-based brand science — mental & physical availability, reach over loyalty | [byron-sharp.md](references/advisors/byron-sharp.md) | |
| 48 | | **Ann Handley** | Content and writing craft; slower, braver marketing | [ann-handley.md](references/advisors/ann-handley.md) | |
| 49 | | **Gary Vaynerchuk** | Attention arbitrage — be native to underpriced channels at volume | [gary-vaynerchuk.md](references/advisors/gary-vaynerchuk.md) | |
| 50 | |
| 51 | ## Seating the Council |
| 52 | |
| 53 | For a council session, seat 3–5 advisors: |
| 54 | |
| 55 | 1. **2–3 whose lens directly fits the question type** (table below). |
| 56 | 2. **Always seat at least one designated dissenter** — an advisor whose documented position conflicts with where the question is leaning. A council that agrees is a mirror, not a board. |
| 57 | 3. Honor explicit requests ("I want Hormozi and Godin on this"). |
| 58 | |
| 59 | | Question type | Strong fits | Natural dissenters | |
| 60 | |---------------|-------------|-------------------| |
| 61 | | Positioning / messaging | Dunford, Godin, Schwartz | Sharp (differentiation skeptic) | |
| 62 | | Offer / pricing | Hormozi, Halbert, Brunson | Sutherland (price ≠ value logic), Godin (race-to-the-bottom warning) | |
| 63 | | Brand building / awareness | Sharp, Ogilvy, Sutherland | Hopkins, Halbert (show me the sales) | |
| 64 | | Copy / creative review | Ogilvy, Schwartz, Halbert, Handley | Sutherland (test the illogical) | |
| 65 | | Funnels / conversion path | Brunson, Hormozi, Hopkins | Godin (permission over pressure), Handley (you're churning trust) | |
| 66 | | Content strategy | Handley, Godin, Vaynerchuk | Sharp (reach beats depth), Hopkins (where's the response?) | |
| 67 | | Paid ads / media | Hopkins, Sharp, Vaynerchuk | Godin (interruption is a tax) | |
| 68 | | Growth / scaling | Hormozi, Vaynerchuk, Sharp | Handley (quality erosion), Dunford (scaling a fuzzy position) | |
| 69 | | Audience / channel choice | Vaynerchuk, Sharp, Halbert | Godin (smallest viable audience vs. mass reach) | |
| 70 | | Launch strategy | Brunson, Godin, Halbert | Sharp (launches fade; availability compounds) | |
| 71 | |
| 72 | ## Session Protocol |
| 73 | |
| 74 | 1. **Load the seated advisors' dossiers** from `references/advisors/`. |
| 75 | 2. **Optional live research pass** — see below. Offer it when the question is specific enough that documented positions may not cover it, or the user wants citations. |
| 76 | 3. **Each advisor's take** — 2–4 paragraphs per advisor: |
| 77 | - Open with the advisor applying their *signature questions* to the user's case |
| 78 | - Apply their frameworks to the specifics (their dossier lists them) — not generic advice with a name attached |
| 79 | - State their recommendation with the conviction they'd actually have |
| 80 | - Written in their voice per the dossier's voice notes, without fabricated quotes |
| 81 | 4. **The disagreement map** — the most valuable section. Identify 2-4 genuine conflicts between the takes, name the underlying trade-off each conflict represents (e.g., "Sharp vs. Godin here is really reach vs. resonance — which constraint binds *this* business?"), and say what evidence would settle each. |
| 82 | 5. **Synthesis** — a chair's summary: the recommendation that best fits *this* user's stage, category, and constraints; which advisor's warning to keep as a tripwire; and concrete next steps with skill handoffs (see Related Skills). |
| 83 | |
| 84 | ## Live Research Pass |
| 85 | |
| 86 | When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers: |
| 87 | |
| 88 | - **If a deep-research skill is installed** (e.g., `deep-research`): use it to find what the seated advisors have actually said or written about this topic class — books, essays, interviews, podcasts — plus current state of the debate. |
| 89 | - **If a video-analysis skill is installed** (e.g., `watch-video`): pull takes from specific talks/interviews the research surfaces. |
| 90 | - **If a recency skill is installed** (e.g., `last30days`): check for recent takes when the topic is fast-moving. |
| 91 | - **Otherwise**: use built-in web search for `[advisor name] + [topic]` per seated advisor, preferring primary sources (their own books, blogs, newsletters, talks) over roundup articles. |
| 92 | |
| 93 | Fold findings into the takes with citations ("In a 2023 interview on X, Dunford argued…"). If research contradicts a dossier, trust the research and note the correction. |
| 94 | |
| 95 | ## Grounding Rules (non-negotiable) |
| 96 | |
| 97 | - **Label the session as simulation** once, at the top: a line like *"Simulated council — each take is built from the advisor's published frameworks and positions, not their actual review."* |
| 98 | - **No fabricated quotes.** Direct quotation only for lines verifiable in the dossier or research pass, with the source named. Otherwise paraphrase: "Hopkins's position in *Scientific Advertising* is…" |
| 99 | - **No invented endorsements or condemnations.** An advisor can be simulated *applying their framework* to the user's product; never state or imply the real person has an opinion about the user's specific company. |
| 100 | - **Living advisors get extra care.** Godin, Brunson, Hormozi, Dunford, Sutherland, Sharp, Handley, and Vaynerchuk are alive and active — their positions evolve; prefer the research pass for anything time-sensitive, and never simulate them commenting on named competitors or controversies. |
| 101 | - **Disagree in substance, not caricature.** Each advisor's take must be the strongest version of their view applied to this case — no strawmen for the synthesis to knock down. |
| 102 | - **If the dossier and the user's question don't overlap** (e.g., asking Hopkins about TikTok), say so in the take and reason by explicit analogy: "Hopkins never saw social feeds, but his sampling principle maps like this…" |
| 103 | |
| 104 | ## Output Format |
| 105 | |
| 106 | ``` |
| 107 | > Simulated council — each take is built from the advisor's published |
| 108 | > frameworks and positions, not their actual review. |
| 109 | |
| 110 | ## The question before the council |
| 111 | [1-2 sentence restatement + what's at stake] |
| 112 | |
| 113 | ## Seated: [Advisor A], [Advisor B], [Advisor C] ([mode]) |
| 114 | [One line on why this bench, including who was seated as the dissenter] |
| 115 | |
| 116 | --- |
| 117 | |
| 118 | ### [Advisor A] — [their lens, 3-5 words] |
| 119 | [2-4 paragraph take] |
| 120 | **Bottom line:** [one sentence] |
| 121 | |
| 122 | ### [Advisor B] — … |
| 123 | … |
| 124 | |
| 125 | --- |
| 126 | |
| 127 | ## Where the council disagrees |
| 128 | 1. **[Conflict]** — [A] says X because [framework]; [B] says Y because |
| 129 | [framework]. The real trade-off: [underlying tension]. What would |
| 130 | settle it: [evidence/test]. |
| 131 | 2. … |
| 132 | |
| 133 | ## Chair's synthesis |
| 134 | [Recommendation fitted to this user's stage and constraints] |
| 135 | - **Do:** [2-4 concrete next steps] |
| 136 | - **Tripwire:** [which advisor's warning to monitor, and the signal] |
| 137 | - **Execute with:** [skill handoffs] |
| 138 | ``` |
| 139 | |
| 140 | ## Adding a Custom Advisor |
| 141 | |
| 142 | Users can extend the bench ("add my own advisor"). Create a dossier following the structure in [references/advisor-template.md](references/advisor-template.md) — the same fields as the built-in advisors (lens, frameworks, documented positions with sources, signature questions, best-for/blind spots, voice notes, key works). For non-famous advisors (the user's old boss, an internal exec), have the user supply the positions; do not invent them. Save to `.agents/advisors/<name>.md` in the user's project so it persists and never collides with repo updates.B1 — Line is 557 characters — unreadable by eye |
| 143 | |
| 144 | ## Anti-Patterns |
| 145 | |
| 146 | - **The agreeing council** — five takes that all bless the user's existing plan. Re-seat with a real dissenter. |
| 147 | - **Name-flavored generic advice** — a take that would survive with the name swapped isn't a take; anchor each one in that advisor's specific frameworks and documented positions. |
| 148 | - **Quote soup** — stitching famous one-liners together instead of applying the method behind them. |
| 149 | - **Council for execution work** — the council decides direction; it doesn't write the landing page. Hand off to the execution skill once direction is set. |
| 150 | - **Twelve advisors on a headline** — match the bench size to the stakes. |
| 151 | |
| 152 | ## Related Skills |
| 153 | |
| 154 | - **positioning** / **product-marketing**: When Dunford's take wins — execute the positioning work |
| 155 | - **offers** / **pricing**: When Hormozi/Halbert direction wins — build the offer |
| 156 | - **copywriting** / **copy-editing**: When the council reviewed copy — execute revisions |
| 157 | - **ads** / **ad-creative**: When the debate was media or creative strategy |
| 158 | - **content-strategy** / **social**: When Handley/Vaynerchuk direction wins |
| 159 | - **brand-strategy** / **marketing-psychology**: For Sharp's availability work and Sutherland's behavioral mechanics |
| 160 | - **ab-testing**: When the disagreement map says "test it" — Hopkins would insist |
| 161 | - **deep-research**: For the live research pass, when installed |
| 162 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40