marketing-council
Skill6 starsChanged 50 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 content-strategy, product-launch, lead-magnets, cro, or linkedin-ads.
19 other projects use a version of this, 18 of them edited.
Adopted by
Most recently taken up by
- pixelswithbliss/claude-skillsedited, first seen Nov 1, 2026
- GAPZ787/claude-skillsedited, first seen Nov 1, 2026
- TommyBez/skillsboardedited, first seen Oct 25, 2026
- masterpeteworld/claude-skillsedited, first seen Oct 15, 2026
- anis-dr/skillsedited, first seen Oct 15, 2026
- patinaproject/skillsedited, first seen Oct 15, 2026
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.
nilssonrSkillseo
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
VercelSkillremotion-best-practices
Best practices for Remotion - Video creation in React
Also in 3 projects that use this
AnasX7Skilldesign-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
VercelSkillweb-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
StrayDragonSkillui-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
GoogleSkillgrilling
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
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 18
- coreyhaines31/marketingskills★ 61k88% same
- Nexus-JPF/note-companion★ 87491% same
- open-fox/agents★ 5591% same
- TommyBez/skillsboard★ 1091% same
- anis-dr/skills★ 491% same
- agrivisionai/claude-skills★ 191% same
- ngothanhtung/claude-code-skills★ 191% same
- patinaproject/skills★ 191% same
- productionx-in/Core-Skills★ 191% same
- chaakresh/claude-skills★ 091% same
8 more not listed
Wrote their own version · 1
- david-corroy/skills-marketing-fr★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- campaign-reportSkill
- competitor-intelSkill
- content-auditSkill
- content-strategySkill
- croSkill
- customer-researchSkill
- lead-magnetsSkill
- linkedin-adsSkill
- marketing-monthlySkill
- pipeline-analysisSkill
- product-launchSkill
- internal-linkingSkill
- seo-reportSkill
- beautify-github-readmeSkill
- cinemagraphSkill
- frontend-design-anti-slopSkill
- copy-deslopSkill
- copy-longformSkill
- writing-assistantSkill
The file
We split this skill into the rules it gives an agent
8 rules. 2 are common, 5 are distinctive, and 1 is very specific to this project.
2
Common
Most of the 17 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 35
This is persona simulation, not the real people: Every take must be grounded in what the advisor actually wrote or said (see Grounding …
- Common: line 106
When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:
- Very specific: line 111
Otherwise: use built-in web search for [advisor name] + [topic] per seated advisor, preferring primary sources (their own books, blogs, …
- Distinctive: line 175
content-strategy: when Handley's or Godin's direction wins
- Distinctive: line 176
product-launch: when the debate was launch strategy
- Distinctive: line 178
linkedin-ads: when the debate was paid B2B media
- Distinctive: line 179
customer-research: when the council says "you don't know your customer yet"
- Distinctive: line 182
Not in this library (upstream has them): positioning, offers, copywriting, ads, brand-strategy, ab-testing, deep-research.
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing Council
Adapted from marketing-council by Corey Haines (MIT). Same method, with this library's rule that company context is scanned, listed, and confirmed before it's read.
Company context: setup step, every run
This skill has no fixed place for company data and never uses context without the user's say-so. Run this before the questions below.
- Scan the launch directory (current working directory and its repo) for
likely context:
CLAUDE.md,AGENTS.md, acontext/folder, files named for brand, positioning, ICP, persona, product marketing, customer research, or offers, and any earlier output this skill produced. List filenames only; don't read contents yet. - Ask one question. Show what was found (or say nothing relevant turned up) and offer four choices: use these files; point me at a different folder or file; paste the context as text; start with no context. Wait.
- Read only what the user approved. A pasted block is the context for this run. "None" means the answers below are the whole picture.
- Still ask the intake questions. Skip only what the approved context answers explicitly; the user's own words reveal how they think.
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
Then clarify (ask only for what's missing):
- 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)
- The stakes — What happens if this goes well or badly? What's already been tried?
- Session mode — quick take, council session, or full council (see below). Default: council session.
Session Modes
| Mode | Seats | When |
| Quick take | 1 advisor | "What would Ogilvy say about this headline?" — a single named advisor |
| Council session (default) | 3–5 advisors | A real decision that benefits from conflicting lenses |
| Full council | All 12 | Major 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.
| Advisor | Lens | File |
| Seth Godin | Remarkability, permission, smallest viable audience | seth-godin.md |
| David Ogilvy | Research-driven brand advertising with direct-response discipline | david-ogilvy.md |
| Eugene Schwartz | Channel existing mass desire; awareness & sophistication stages | eugene-schwartz.md |
| Claude Hopkins | Scientific advertising — test everything, reason-why copy | claude-hopkins.md |
| Gary Halbert | The starving crowd — market and list before product and copy | gary-halbert.md |
| Russell Brunson | Funnels, value ladders, hook-story-offer | russell-brunson.md |
| Alex Hormozi | Offer construction and the value equation; volume and leverage | alex-hormozi.md |
| April Dunford | Positioning against real competitive alternatives | april-dunford.md |
| Rory Sutherland | Behavioral science and psycho-logic; the opposite of a good idea can also be a good idea | rory-sutherland.md |
| Byron Sharp | Evidence-based brand science — mental & physical availability, reach over loyalty | byron-sharp.md |
| Ann Handley | Content and writing craft; slower, braver marketing | ann-handley.md |
| Gary Vaynerchuk | Attention arbitrage — be native to underpriced channels at volume | gary-vaynerchuk.md |
Seating the Council
For a council session, seat 3–5 advisors:
- 2–3 whose lens directly fits the question type (table below).
- 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.
- Honor explicit requests ("I want Hormozi and Godin on this").
| Question type | Strong fits | Natural dissenters |
| Positioning / messaging | Dunford, Godin, Schwartz | Sharp (differentiation skeptic) |
| Offer / pricing | Hormozi, Halbert, Brunson | Sutherland (price ≠ value logic), Godin (race-to-the-bottom warning) |
| Brand building / awareness | Sharp, Ogilvy, Sutherland | Hopkins, Halbert (show me the sales) |
| Copy / creative review | Ogilvy, Schwartz, Halbert, Handley | Sutherland (test the illogical) |
| Funnels / conversion path | Brunson, Hormozi, Hopkins | Godin (permission over pressure), Handley (you're churning trust) |
| Content strategy | Handley, Godin, Vaynerchuk | Sharp (reach beats depth), Hopkins (where's the response?) |
| Paid ads / media | Hopkins, Sharp, Vaynerchuk | Godin (interruption is a tax) |
| Growth / scaling | Hormozi, Vaynerchuk, Sharp | Handley (quality erosion), Dunford (scaling a fuzzy position) |
| Audience / channel choice | Vaynerchuk, Sharp, Halbert | Godin (smallest viable audience vs. mass reach) |
| Launch strategy | Brunson, Godin, Halbert | Sharp (launches fade; availability compounds) |
Session Protocol
- Load the seated advisors' dossiers from
references/advisors/. - 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.
- 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
- 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.
- 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 it in the user's project (for example advisors/<name>.md, or wherever they say); the context setup step will list it next time.
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
In this library, for executing the winning direction:
- content-strategy: when Handley's or Godin's direction wins
- product-launch: when the debate was launch strategy
- lead-magnets / cro: when Hormozi's or Brunson's funnel direction wins
- linkedin-ads: when the debate was paid B2B media
- customer-research: when the council says "you don't know your customer yet"
- writing-assistant / copy-deslop: when the council reviewed copy
Not in this library (upstream has them): positioning, offers, copywriting, ads, brand-strategy, ab-testing, deep-research.
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
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.

