本文へ移動
cccskills
無料GitHub で公開

suede-marketing-council

Suede-affiliated marketing deliberation that applies documented public frameworks through clearly labeled simulated advisors, surfaces disagreements, and synthesizes a decision. Use when the user wants multiple expert lenses on one bounded marketing question. NOT FOR: factual claims about a living person's private views, primary research (use suede-customer-research), or executing the selected tactic (route to the relevant public Suede skill).

インストール方法を見る

含まれるファイル(17)

  • SKILL.md12.0 KB
  • agents/openai.yaml659 B
  • CARD.md4.3 KB
  • evals/evals.json5.5 KB
  • references/advisor-template.md2.0 KB
  • references/advisors/alex-hormozi.md3.8 KB
  • references/advisors/ann-handley.md3.9 KB
  • references/advisors/april-dunford.md4.3 KB
  • references/advisors/byron-sharp.md4.6 KB
  • references/advisors/claude-hopkins.md3.7 KB
  • references/advisors/david-ogilvy.md4.0 KB
  • references/advisors/eugene-schwartz.md4.0 KB
  • references/advisors/gary-halbert.md3.8 KB
  • references/advisors/gary-vaynerchuk.md4.2 KB
  • references/advisors/rory-sutherland.md4.6 KB
  • references/advisors/russell-brunson.md4.2 KB
  • references/advisors/seth-godin.md3.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Suede Marketing Council

Suede convenes a clearly labeled simulated council that applies documented public frameworks to one bounded marketing question. Its value is disciplined disagreement: conflicting lenses expose the trade-offs, evidence gaps, and tests the user should consider 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

Read .agents/product-marketing.md first if it exists and ask only for what it does not cover; see suede-product-marketing for path fallbacks.

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 12Expect a long output. Offer this only when the decision is irreversible, commits spend or headcount the user has named as material, or the user says they cannot revisit it for at least a quarter

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: research what each seated advisor has actually said or written about this topic class, using whatever research surface is callable: an installed research or video-analysis skill, otherwise built-in web search for [advisor name] + [topic]. Prefer 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…" That path is for a channel or era gap where the underlying mechanism still transfers.
  • "Outside my documented record on this" is a first-class verdict. When the dossier holds no documented position on the mechanism at issue (not merely an unfamiliar channel or era) the take says exactly that as its Bottom line rather than extrapolating. The chair then either runs the Live Research Pass for that advisor or re-seats the chair (the same re-seat move as the agreeing-council anti-pattern). Never fill the gap by inference and never let a re-seat go unmentioned in the "Seated" line.

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.

Boundaries

  • Do not present a simulation as the real person's statement, endorsement, advice, or current opinion.
  • Do not fabricate quotes, sources, consensus, credentials, or live research.
  • Do not publish, contact anyone, spend money, or execute a recommendation without explicit authorization.
  • Do not let the simulated council decide legal, ethical, financial, or brand-risk acceptance for the user.

Routing

  • Use suede-product-marketing for positioning and suede-offers or suede-pricing for the commercial package.
  • Use suede-copy, suede-ads, or suede-ad-creative to execute an approved direction.
  • Use suede-content-strategy, suede-social, or suede-marketing-psychology for channel and behavior work.
  • Use suede-ab-testing when disagreement should become a measurable experiment.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Design, review, and visually QA web and app interfaces against explicit design laws so shipped screens look intentional instead of generic AI output.

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

JasonColapietro のスキルをすべて見る

このスキルの問題を報告する