[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWC1FRTS4431FK3J7Q3NVE":3,"skill-same:01M7CWC1FRTS4431FK3J7Q3NVE":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CWC1FRTS4431FK3J7Q3NVE","marketing-council",null,"When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketing-council\ndescription: \"When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.\"\nmetadata:\n  version: 1.0.3\n---\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,"metadata":24,"description":7},{"version":25},"1.0.3","main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Fmarketing-council","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-council",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-council",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-council","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",5709,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fadvisor-template.md",2112,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisor-template.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fadvisors\u002Falex-hormozi.md",3987,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Falex-hormozi.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fadvisors\u002Fann-handley.md",4064,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fann-handley.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fadvisors\u002Fapril-dunford.md",4410,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fapril-dunford.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fadvisors\u002Fbyron-sharp.md",4790,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fbyron-sharp.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fadvisors\u002Fclaude-hopkins.md",3789,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fclaude-hopkins.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fadvisors\u002Fdavid-ogilvy.md",4096,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fdavid-ogilvy.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fadvisors\u002Feugene-schwartz.md",4184,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Feugene-schwartz.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fadvisors\u002Fgary-halbert.md",3968,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fgary-halbert.md",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fadvisors\u002Fgary-vaynerchuk.md",4399,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fgary-vaynerchuk.md",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fadvisors\u002Frory-sutherland.md",4732,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Frory-sutherland.md",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fadvisors\u002Frussell-brunson.md",4331,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Frussell-brunson.md",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fadvisors\u002Fseth-godin.md",4026,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-council\u002Freferences\u002Fadvisors\u002Fseth-godin.md",[107,114,121,129,136,143],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]