agentleFS
pixelswithblisspixelswithbliss/claude-skills/skills/marketing-council/SKILL.md

marketing-council

Skill0 starsChanged 26 days agoMITView on GitHub

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.

19 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo, remotion-best-practices and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 3 projects that use this

  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 3 projects that use this

  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 4 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    This is persona simulation, not the real people: Every take must be grounded in what the advisor actually wrote or said (see Grounding …

    line 12
  2. Very specific:

    If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md), read it before asking …

    line 17
  3. Distinctive:

    When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:

    line 86
  4. Very specific:

    Otherwise: use built-in web search for [advisor name] + [topic] per seated advisor, preferring primary sources (their own books, blogs, …

    line 91
  5. Distinctive:

    ab-testing: When the disagreement map says "test it" — Hopkins would insist

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing Council

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.

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.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md), read it before asking questions.

Then clarify (ask only for what's missing):

  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)
  2. The stakes — What happens if this goes well or badly? What's already been tried?
  3. Session mode — quick take, council session, or full council (see below). Default: council session.

Session Modes

ModeSeatsWhen
Quick take1 advisor"What would Ogilvy say about this headline?" — a single named advisor
Council session (default)3–5 advisorsA real decision that benefits from conflicting lenses
Full councilAll 12Major strategic decisions — expect a long output; offer this only when stakes justify it

The Bench

Twelve advisors, chosen so their lenses collide. Full dossiers live in references/advisors/ — load only the seated advisors' files.

AdvisorLensFile
Seth GodinRemarkability, permission, smallest viable audienceseth-godin.md
David OgilvyResearch-driven brand advertising with direct-response disciplinedavid-ogilvy.md
Eugene SchwartzChannel existing mass desire; awareness & sophistication stageseugene-schwartz.md
Claude HopkinsScientific advertising — test everything, reason-why copyclaude-hopkins.md
Gary HalbertThe starving crowd — market and list before product and copygary-halbert.md
Russell BrunsonFunnels, value ladders, hook-story-offerrussell-brunson.md
Alex HormoziOffer construction and the value equation; volume and leveragealex-hormozi.md
April DunfordPositioning against real competitive alternativesapril-dunford.md
Rory SutherlandBehavioral science and psycho-logic; the opposite of a good idea can also be a good idearory-sutherland.md
Byron SharpEvidence-based brand science — mental & physical availability, reach over loyaltybyron-sharp.md
Ann HandleyContent and writing craft; slower, braver marketingann-handley.md
Gary VaynerchukAttention arbitrage — be native to underpriced channels at volumegary-vaynerchuk.md

Seating the Council

For a council session, seat 3–5 advisors:

  1. 2–3 whose lens directly fits the question type (table below).
  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.
  3. Honor explicit requests ("I want Hormozi and Godin on this").
Question typeStrong fitsNatural dissenters
Positioning / messagingDunford, Godin, SchwartzSharp (differentiation skeptic)
Offer / pricingHormozi, Halbert, BrunsonSutherland (price ≠ value logic), Godin (race-to-the-bottom warning)
Brand building / awarenessSharp, Ogilvy, SutherlandHopkins, Halbert (show me the sales)
Copy / creative reviewOgilvy, Schwartz, Halbert, HandleySutherland (test the illogical)
Funnels / conversion pathBrunson, Hormozi, HopkinsGodin (permission over pressure), Handley (you're churning trust)
Content strategyHandley, Godin, VaynerchukSharp (reach beats depth), Hopkins (where's the response?)
Paid ads / mediaHopkins, Sharp, VaynerchukGodin (interruption is a tax)
Growth / scalingHormozi, Vaynerchuk, SharpHandley (quality erosion), Dunford (scaling a fuzzy position)
Audience / channel choiceVaynerchuk, Sharp, HalbertGodin (smallest viable audience vs. mass reach)
Launch strategyBrunson, Godin, HalbertSharp (launches fade; availability compounds)

Session Protocol

  1. Load the seated advisors' dossiers from references/advisors/.
  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.
  3. Each advisor's take — 2–4 paragraphs per advisor:
    • Open with the advisor applying their signature questions to the user's case
    • Apply their frameworks to the specifics (their dossier lists them) — not generic advice with a name attached
    • State their recommendation with the conviction they'd actually have
    • Written in their voice per the dossier's voice notes, without fabricated quotes
  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.
  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).

Live Research Pass

When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:

  • 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.
  • If a video-analysis skill is installed (e.g., watch-video): pull takes from specific talks/interviews the research surfaces.
  • If a recency skill is installed (e.g., last30days): check for recent takes when the topic is fast-moving.
  • 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.

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.

Grounding Rules (non-negotiable)

  • 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."
  • 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…"
  • 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.
  • 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.
  • 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.
  • 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…"

Output Format

> Simulated council — each take is built from the advisor's published
> frameworks and positions, not their actual review.

## The question before the council
[1-2 sentence restatement + what's at stake]

## Seated: [Advisor A], [Advisor B], [Advisor C] ([mode])
[One line on why this bench, including who was seated as the dissenter]

---

### [Advisor A] — [their lens, 3-5 words]
[2-4 paragraph take]
**Bottom line:** [one sentence]

### [Advisor B] — …
…

---

## Where the council disagrees
1. **[Conflict]** — [A] says X because [framework]; [B] says Y because
   [framework]. The real trade-off: [underlying tension]. What would
   settle it: [evidence/test].
2. …

## Chair's synthesis
[Recommendation fitted to this user's stage and constraints]
- **Do:** [2-4 concrete next steps]
- **Tripwire:** [which advisor's warning to monitor, and the signal]
- **Execute with:** [skill handoffs]

Adding a Custom Advisor

Users can extend the bench ("add my own advisor"). Create a dossier following the structure in 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.

Anti-Patterns

  • The agreeing council — five takes that all bless the user's existing plan. Re-seat with a real dissenter.
  • 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.
  • Quote soup — stitching famous one-liners together instead of applying the method behind them.
  • 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.
  • Twelve advisors on a headline — match the bench size to the stakes.

Related Skills

  • positioning / product-marketing: When Dunford's take wins — execute the positioning work
  • offers / pricing: When Hormozi/Halbert direction wins — build the offer
  • copywriting / copy-editing: When the council reviewed copy — execute revisions
  • ads / ad-creative: When the debate was media or creative strategy
  • content-strategy / social: When Handley/Vaynerchuk direction wins
  • brand-strategy / marketing-psychology: For Sharp's availability work and Sutherland's behavioral mechanics
  • ab-testing: When the disagreement map says "test it" — Hopkins would insist
  • deep-research: For the live research pass, when installed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.