- name
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
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill marketing-council -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill marketing-council -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill marketing-council -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill marketing-council -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/coreyhaines31/marketingskills/tree/HEAD/skills/marketing-councilFrom the publisher
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.
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):
Twelve advisors, chosen so their lenses collide. Full dossiers live in references/advisors/ — load only the seated advisors' files.
For a council session, seat 3–5 advisors:
references/advisors/.When the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:
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.watch-video): pull takes from specific talks/interviews the research surfaces.last30days): check for recent takes when the topic is fast-moving.[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.
> 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]
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.
© 2026 Skills Rack.
---name: marketing-councildescription: When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors…---# skills/marketing-council/SKILL.mdOverview
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.
FAQ
Download skills/marketing-council/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/coreyhaines31/marketingskills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
| 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 |