跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

marketing-council

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.

文档与办公54kskills/marketing-council/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/coreyhaines31/marketingskills/marketing-council/install.md ,按里面的步骤帮我安装这个 Skill。

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

相似的 Skill

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

文档与办公

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

文档与办公

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

文档与办公

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

文档与办公

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

文档与办公

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

文档与办公