[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NAZCJBKBJVPA68AT8K061":3,"skill-same:01M71NAZCJBKBJVPA68AT8K061":141},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M71NAZCJBKBJVPA68AT8K061","marketing-council",null,"Use when you want several expert takes on a marketing decision from a simulated board of named marketers such as Godin, Ogilvy, Schwartz, Dunford and Hormozi. Persona simulation grounded in their published frameworks, with quick-take, council and full-council modes.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"council","marketing council","marketing","board","https","github","simulation","leadership","with","you","when","use","persona","strategy","modes","decision","frameworks","expert","quick","as","2026-11-10 10:56:23",false,"---\nname: marketing-council\ndescription: \"Use when you want several expert takes on a marketing decision from a simulated board of named marketers such as Godin, Ogilvy, Schwartz, Dunford and Hormozi. Persona simulation grounded in their published frameworks, with quick-take, council and full-council modes.\"\ntags: [\"marketing\",\"leadership\",\"strategy\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Fmarketing-council\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Marketing Council\n\nYou 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.\n\n**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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions.\n\nThen clarify (ask only for what's missing):\n1. **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)\n2. **The stakes** — What happens if this goes well or badly? What's already been tried?\n3. **Session mode** — quick take, council session, or full council (see below). Default: council session.\n\n## Session Modes\n\n| Mode | Seats | When |\n|------|-------|------|\n| **Quick take** | 1 advisor | \"What would Ogilvy say about this headline?\" — a single named advisor |\n| **Council session** (default) | 3–5 advisors | A real decision that benefits from conflicting lenses |\n| **Full council** | All 12 | Major strategic decisions — expect a long output; offer this only when stakes justify it |\n\n## The Bench\n\nTwelve advisors, chosen so their lenses collide. Full dossiers live in `references\u002Fadvisors\u002F` — load only the seated advisors' files.\n\n| Advisor | Lens | File |\n|---------|------|------|\n| **Seth Godin** | Remarkability, permission, smallest viable audience | [seth-godin.md](references\u002Fadvisors\u002Fseth-godin.md) |\n| **David Ogilvy** | Research-driven brand advertising with direct-response discipline | [david-ogilvy.md](references\u002Fadvisors\u002Fdavid-ogilvy.md) |\n| **Eugene Schwartz** | Channel existing mass desire; awareness & sophistication stages | [eugene-schwartz.md](references\u002Fadvisors\u002Feugene-schwartz.md) |\n| **Claude Hopkins** | Scientific advertising — test everything, reason-why copy | [claude-hopkins.md](references\u002Fadvisors\u002Fclaude-hopkins.md) |\n| **Gary Halbert** | The starving crowd — market and list before product and copy | [gary-halbert.md](references\u002Fadvisors\u002Fgary-halbert.md) |\n| **Russell Brunson** | Funnels, value ladders, hook-story-offer | [russell-brunson.md](references\u002Fadvisors\u002Frussell-brunson.md) |\n| **Alex Hormozi** | Offer construction and the value equation; volume and leverage | [alex-hormozi.md](references\u002Fadvisors\u002Falex-hormozi.md) |\n| **April Dunford** | Positioning against real competitive alternatives | [april-dunford.md](references\u002Fadvisors\u002Fapril-dunford.md) |\n| **Rory Sutherland** | Behavioral science and psycho-logic; the opposite of a good idea can also be a good idea | [rory-sutherland.md](references\u002Fadvisors\u002Frory-sutherland.md) |\n| **Byron Sharp** | Evidence-based brand science — mental & physical availability, reach over loyalty | [byron-sharp.md](references\u002Fadvisors\u002Fbyron-sharp.md) |\n| **Ann Handley** | Content and writing craft; slower, braver marketing | [ann-handley.md](references\u002Fadvisors\u002Fann-handley.md) |\n| **Gary Vaynerchuk** | Attention arbitrage — be native to underpriced channels at volume | [gary-vaynerchuk.md](references\u002Fadvisors\u002Fgary-vaynerchuk.md) |\n\n## Seating the Council\n\nFor a council session, seat 3–5 advisors:\n\n1. **2–3 whose lens directly fits the question type** (table below).\n2. **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.\n3. Honor explicit requests (\"I want Hormozi and Godin on this\").\n\n| Question type | Strong fits | Natural dissenters |\n|---------------|-------------|-------------------|\n| Positioning \u002F messaging | Dunford, Godin, Schwartz | Sharp (differentiation skeptic) |\n| Offer \u002F pricing | Hormozi, Halbert, Brunson | Sutherland (price ≠ value logic), Godin (race-to-the-bottom warning) |\n| Brand building \u002F awareness | Sharp, Ogilvy, Sutherland | Hopkins, Halbert (show me the sales) |\n| Copy \u002F creative review | Ogilvy, Schwartz, Halbert, Handley | Sutherland (test the illogical) |\n| Funnels \u002F conversion path | Brunson, Hormozi, Hopkins | Godin (permission over pressure), Handley (you're churning trust) |\n| Content strategy | Handley, Godin, Vaynerchuk | Sharp (reach beats depth), Hopkins (where's the response?) |\n| Paid ads \u002F media | Hopkins, Sharp, Vaynerchuk | Godin (interruption is a tax) |\n| Growth \u002F scaling | Hormozi, Vaynerchuk, Sharp | Handley (quality erosion), Dunford (scaling a fuzzy position) |\n| Audience \u002F channel choice | Vaynerchuk, Sharp, Halbert | Godin (smallest viable audience vs. mass reach) |\n| Launch strategy | Brunson, Godin, Halbert | Sharp (launches fade; availability compounds) |\n\n## Session Protocol\n\n1. **Load the seated advisors' dossiers** from `references\u002Fadvisors\u002F`.\n2. **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.\n3. **Each advisor's take** — 2–4 paragraphs per advisor:\n   - Open with the advisor applying their *signature questions* to the user's case\n   - Apply their frameworks to the specifics (their dossier lists them) — not generic advice with a name attached\n   - State their recommendation with the conviction they'd actually have\n   - Written in their voice per the dossier's voice notes, without fabricated quotes\n4. **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.\n5. **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).\n\n## Live Research Pass\n\nWhen the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:\n\n- **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.\n- **If a video-analysis skill is installed** (e.g., `watch-video`): pull takes from specific talks\u002Finterviews the research surfaces.\n- **If a recency skill is installed** (e.g., `last30days`): check for recent takes when the topic is fast-moving.\n- **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.\n\nFold 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.\n\n## Grounding Rules (non-negotiable)\n\n- **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.\"*\n- **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…\"\n- **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.\n- **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.\n- **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.\n- **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…\"\n\n## Output Format\n\n```\n> Simulated council — each take is built from the advisor's published\n> frameworks and positions, not their actual review.\n\n## The question before the council\n[1-2 sentence restatement + what's at stake]\n\n## Seated: [Advisor A], [Advisor B], [Advisor C] ([mode])\n[One line on why this bench, including who was seated as the dissenter]\n\n---\n\n### [Advisor A] — [their lens, 3-5 words]\n[2-4 paragraph take]\n**Bottom line:** [one sentence]\n\n### [Advisor B] — …\n…\n\n---\n\n## Where the council disagrees\n1. **[Conflict]** — [A] says X because [framework]; [B] says Y because\n   [framework]. The real trade-off: [underlying tension]. What would\n   settle it: [evidence\u002Ftest].\n2. …\n\n## Chair's synthesis\n[Recommendation fitted to this user's stage and constraints]\n- **Do:** [2-4 concrete next steps]\n- **Tripwire:** [which advisor's warning to monitor, and the signal]\n- **Execute with:** [skill handoffs]\n```\n\n## Adding a Custom Advisor\n\nUsers can extend the bench (\"add my own advisor\"). Create a dossier following the structure in [references\u002Fadvisor-template.md](references\u002Fadvisor-template.md) — the same fields as the built-in advisors (lens, frameworks, documented positions with sources, signature questions, best-for\u002Fblind 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\u002Fadvisors\u002F\u003Cname>.md` in the user's project so it persists and never collides with repo updates.\n\n## Anti-Patterns\n\n- **The agreeing council** — five takes that all bless the user's existing plan. Re-seat with a real dissenter.\n- **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.\n- **Quote soup** — stitching famous one-liners together instead of applying the method behind them.\n- **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.\n- **Twelve advisors on a headline** — match the bench size to the stakes.\n\n## Related Skills\n\n- **positioning** \u002F **product-marketing**: When Dunford's take wins — execute the positioning work\n- **offers** \u002F **pricing**: When Hormozi\u002FHalbert direction wins — build the offer\n- **copywriting** \u002F **copy-editing**: When the council reviewed copy — execute revisions\n- **ads** \u002F **ad-creative**: When the debate was media or creative strategy\n- **content-strategy** \u002F **social**: When Handley\u002FVaynerchuk direction wins\n- **brand-strategy** \u002F **marketing-psychology**: For Sharp's availability work and Sutherland's behavioral mechanics\n- **ab-testing**: When the disagreement map says \"test it\" — Hopkins would insist\n- **deep-research**: For the live research pass, when installed\n","# Marketing Council\n\nYou 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.\n\n**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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions.\n\nThen clarify (ask only for what's missing):\n1. **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)\n2. **The stakes** — What happens if this goes well or badly? What's already been tried?\n3. **Session mode** — quick take, council session, or full council (see below). Default: council session.\n\n## Session Modes\n\n| Mode | Seats | When |\n|------|-------|------|\n| **Quick take** | 1 advisor | \"What would Ogilvy say about this headline?\" — a single named advisor |\n| **Council session** (default) | 3–5 advisors | A real decision that benefits from conflicting lenses |\n| **Full council** | All 12 | Major strategic decisions — expect a long output; offer this only when stakes justify it |\n\n## The Bench\n\nTwelve advisors, chosen so their lenses collide. Full dossiers live in `references\u002Fadvisors\u002F` — load only the seated advisors' files.\n\n| Advisor | Lens | File |\n|---------|------|------|\n| **Seth Godin** | Remarkability, permission, smallest viable audience | [seth-godin.md](references\u002Fadvisors\u002Fseth-godin.md) |\n| **David Ogilvy** | Research-driven brand advertising with direct-response discipline | [david-ogilvy.md](references\u002Fadvisors\u002Fdavid-ogilvy.md) |\n| **Eugene Schwartz** | Channel existing mass desire; awareness & sophistication stages | [eugene-schwartz.md](references\u002Fadvisors\u002Feugene-schwartz.md) |\n| **Claude Hopkins** | Scientific advertising — test everything, reason-why copy | [claude-hopkins.md](references\u002Fadvisors\u002Fclaude-hopkins.md) |\n| **Gary Halbert** | The starving crowd — market and list before product and copy | [gary-halbert.md](references\u002Fadvisors\u002Fgary-halbert.md) |\n| **Russell Brunson** | Funnels, value ladders, hook-story-offer | [russell-brunson.md](references\u002Fadvisors\u002Frussell-brunson.md) |\n| **Alex Hormozi** | Offer construction and the value equation; volume and leverage | [alex-hormozi.md](references\u002Fadvisors\u002Falex-hormozi.md) |\n| **April Dunford** | Positioning against real competitive alternatives | [april-dunford.md](references\u002Fadvisors\u002Fapril-dunford.md) |\n| **Rory Sutherland** | Behavioral science and psycho-logic; the opposite of a good idea can also be a good idea | [rory-sutherland.md](references\u002Fadvisors\u002Frory-sutherland.md) |\n| **Byron Sharp** | Evidence-based brand science — mental & physical availability, reach over loyalty | [byron-sharp.md](references\u002Fadvisors\u002Fbyron-sharp.md) |\n| **Ann Handley** | Content and writing craft; slower, braver marketing | [ann-handley.md](references\u002Fadvisors\u002Fann-handley.md) |\n| **Gary Vaynerchuk** | Attention arbitrage — be native to underpriced channels at volume | [gary-vaynerchuk.md](references\u002Fadvisors\u002Fgary-vaynerchuk.md) |\n\n## Seating the Council\n\nFor a council session, seat 3–5 advisors:\n\n1. **2–3 whose lens directly fits the question type** (table below).\n2. **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.\n3. Honor explicit requests (\"I want Hormozi and Godin on this\").\n\n| Question type | Strong fits | Natural dissenters |\n|---------------|-------------|-------------------|\n| Positioning \u002F messaging | Dunford, Godin, Schwartz | Sharp (differentiation skeptic) |\n| Offer \u002F pricing | Hormozi, Halbert, Brunson | Sutherland (price ≠ value logic), Godin (race-to-the-bottom warning) |\n| Brand building \u002F awareness | Sharp, Ogilvy, Sutherland | Hopkins, Halbert (show me the sales) |\n| Copy \u002F creative review | Ogilvy, Schwartz, Halbert, Handley | Sutherland (test the illogical) |\n| Funnels \u002F conversion path | Brunson, Hormozi, Hopkins | Godin (permission over pressure), Handley (you're churning trust) |\n| Content strategy | Handley, Godin, Vaynerchuk | Sharp (reach beats depth), Hopkins (where's the response?) |\n| Paid ads \u002F media | Hopkins, Sharp, Vaynerchuk | Godin (interruption is a tax) |\n| Growth \u002F scaling | Hormozi, Vaynerchuk, Sharp | Handley (quality erosion), Dunford (scaling a fuzzy position) |\n| Audience \u002F channel choice | Vaynerchuk, Sharp, Halbert | Godin (smallest viable audience vs. mass reach) |\n| Launch strategy | Brunson, Godin, Halbert | Sharp (launches fade; availability compounds) |\n\n## Session Protocol\n\n1. **Load the seated advisors' dossiers** from `references\u002Fadvisors\u002F`.\n2. **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.\n3. **Each advisor's take** — 2–4 paragraphs per advisor:\n   - Open with the advisor applying their *signature questions* to the user's case\n   - Apply their frameworks to the specifics (their dossier lists them) — not generic advice with a name attached\n   - State their recommendation with the conviction they'd actually have\n   - Written in their voice per the dossier's voice notes, without fabricated quotes\n4. **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.\n5. **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).\n\n## Live Research Pass\n\nWhen the topic is specific (a niche, a channel shift, a current platform change) or the user wants sources, go beyond the dossiers:\n\n- **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.\n- **If a video-analysis skill is installed** (e.g., `watch-video`): pull takes from specific talks\u002Finterviews the research surfaces.\n- **If a recency skill is installed** (e.g., `last30days`): check for recent takes when the topic is fast-moving.\n- **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.\n\nFold 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.\n\n## Grounding Rules (non-negotiable)\n\n- **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.\"*\n- **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…\"\n- **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.\n- **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.\n- **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.\n- **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…\"\n\n## Output Format\n\n```\n> Simulated council — each take is built from the advisor's published\n> frameworks and positions, not their actual review.\n\n## The question before the council\n[1-2 sentence restatement + what's at stake]\n\n## Seated: [Advisor A], [Advisor B], [Advisor C] ([mode])\n[One line on why this bench, including who was seated as the dissenter]\n\n---\n\n### [Advisor A] — [their lens, 3-5 words]\n[2-4 paragraph take]\n**Bottom line:** [one sentence]\n\n### [Advisor B] — …\n…\n\n---\n\n## Where the council disagrees\n1. **[Conflict]** — [A] says X because [framework]; [B] says Y because\n   [framework]. The real trade-off: [underlying tension]. What would\n   settle it: [evidence\u002Ftest].\n2. …\n\n## Chair's synthesis\n[Recommendation fitted to this user's stage and constraints]\n- **Do:** [2-4 concrete next steps]\n- **Tripwire:** [which advisor's warning to monitor, and the signal]\n- **Execute with:** [skill handoffs]\n```\n\n## Adding a Custom Advisor\n\nUsers can extend the bench (\"add my own advisor\"). Create a dossier following the structure in [references\u002Fadvisor-template.md](references\u002Fadvisor-template.md) — the same fields as the built-in advisors (lens, frameworks, documented positions with sources, signature questions, best-for\u002Fblind 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\u002Fadvisors\u002F\u003Cname>.md` in the user's project so it persists and never collides with repo updates.\n\n## Anti-Patterns\n\n- **The agreeing council** — five takes that all bless the user's existing plan. Re-seat with a real dissenter.\n- **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.\n- **Quote soup** — stitching famous one-liners together instead of applying the method behind them.\n- **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.\n- **Twelve advisors on a headline** — match the bench size to the stakes.\n\n## Related Skills\n\n- **positioning** \u002F **product-marketing**: When Dunford's take wins — execute the positioning work\n- **offers** \u002F **pricing**: When Hormozi\u002FHalbert direction wins — build the offer\n- **copywriting** \u002F **copy-editing**: When the council reviewed copy — execute revisions\n- **ads** \u002F **ad-creative**: When the debate was media or creative strategy\n- **content-strategy** \u002F **social**: When Handley\u002FVaynerchuk direction wins\n- **brand-strategy** \u002F **marketing-psychology**: For Sharp's availability work and Sutherland's behavioral mechanics\n- **ab-testing**: When the disagreement map says \"test it\" — Hopkins would insist\n- **deep-research**: For the live research pass, when installed\n",{"name":5,"tags":54,"tools":55,"source":56,"license":14,"description":7,"source_path":57,"source_commit":58},[31,36,42],[],"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Fmarketing-council","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add monoes\u002Fmonomind --skill marketing-council",{"tool":74,"command":75},"bunx","bunx skills add monoes\u002Fmonomind --skill marketing-council",{"tool":77,"command":78},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill marketing-council","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002FSKILL.md",true,[82,87,93,97,101,105,109,113,117,121,125,129,133,137],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fadvisor-template.md","REFERENCE","参考文档",2112,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisor-template.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fadvisors\u002Falex-hormozi.md",3987,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Falex-hormozi.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fadvisors\u002Fann-handley.md",4064,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fann-handley.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fadvisors\u002Fapril-dunford.md",4410,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fapril-dunford.md",{"path":106,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fadvisors\u002Fbyron-sharp.md",4790,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fbyron-sharp.md",{"path":110,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fadvisors\u002Fclaude-hopkins.md",3789,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fclaude-hopkins.md",{"path":114,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fadvisors\u002Fdavid-ogilvy.md",4096,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fdavid-ogilvy.md",{"path":118,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fadvisors\u002Feugene-schwartz.md",4184,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Feugene-schwartz.md",{"path":122,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fadvisors\u002Fgary-halbert.md",3968,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fgary-halbert.md",{"path":126,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fadvisors\u002Fgary-vaynerchuk.md",4399,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fgary-vaynerchuk.md",{"path":130,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fadvisors\u002Frory-sutherland.md",4732,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Frory-sutherland.md",{"path":134,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fadvisors\u002Frussell-brunson.md",4331,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Frussell-brunson.md",{"path":138,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fadvisors\u002Fseth-godin.md",4026,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fseth-godin.md",[142,171,201,227,249,276],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":170},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":184,"publishedAt":170},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[178,181],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":182,"categoryName":183,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[185,186,187,154,188,189,39,38,159,190,191,192,193,194,195,196,197,198,199,200],"writing","writing plans","plans","superpowers","implementation plan","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":170},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[208],{"categoryNo":209,"categoryName":210,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[194,212,213,214,215,157,216,39,217,218,219,193,220,221,222,223,224,225,40,226],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":237,"publishedAt":170},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[234],{"categoryNo":235,"categoryName":236,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[159,194,238,239,240,241,157,40,39,242,243,37,244,219,34,245,33,246,247,248],"write query","postgres","for","snowflake","best practices","natural-language","multi","sql","syntax","plugins","data",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":261,"publishedAt":170},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[255,258],{"categoryNo":256,"categoryName":257,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[262,263,264,265,240,266,267,268,269,158,270,271,272,159,162,34,273,274,275,33],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":277,"name":278,"nameZh":6,"description":279,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":146,"licenseFileUrl":6,"sourceHtmlUrl":280,"categories":281,"keywords":283,"publishedAt":170},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[282],{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},[264,284,285,286,287,288,289,240,290,291,190,292,293,36,162,34,294,295,33,296],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","recovery","operations","systems"]