JasonColapietro/suede-creator-skills / skills/suede-marketing-council
suede-marketing-council
VerifiedSuede Marketing Council Skills: simulated advisors pressure-test one contested marketing decision. Use when asked "pressure-test this channel bet" or for expert lenses, a skeptical read, or a chair synthesis with disagreements and evidence tests. NOT FOR: impersonating people, primary research (suede-customer-research), writing a full plan (suede-marketing-plan), or channel execution.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.2 KB |
| SKILL.md | skill md | 10.4 KB |
| agents/openai.yaml | config | 550 B |
| evals/evals.json | config | 5.3 KB |
| references/advisor-template.md | markdown | 1.7 KB |
| references/advisors/attention-trader.md | markdown | 2.0 KB |
| references/advisors/audience-builder.md | markdown | 2.1 KB |
| references/advisors/behavioral-contrarian.md | markdown | 2.4 KB |
| references/advisors/brand-reach-scientist.md | markdown | 2.5 KB |
| references/advisors/demand-mapper.md | markdown | 2.6 KB |
| references/advisors/editorial-director.md | markdown | 2.0 KB |
| references/advisors/funnel-architect.md | markdown | 2.5 KB |
| references/advisors/market-hunter.md | markdown | 2.3 KB |
| references/advisors/offer-strategist.md | markdown | 2.8 KB |
| references/advisors/positioning-strategist.md | markdown | 2.8 KB |
| references/advisors/response-scientist.md | markdown | 2.3 KB |
| references/advisors/search-visibility-strategist.md | markdown | 3.1 KB |
| references/worked-contract.md | markdown | 2.0 KB |
references/advisors/response-scientist.md
View on GitHub# Response Scientist
**Lens:** Marketing is selling at scale, and every claim, headline, and dollar should earn its place with measured response. Opinions lose to tests.
## Frameworks
- **Suede Test-First Rule.** Run a small, tracked test before committing budget. Let response data, not taste or committee vote, pick the winner. Tag every variant so results trace to a source.
- **Reason-why claims.** Give a concrete, checkable reason to buy. Specific beats superlative: "ships in 48 hours from 3 warehouses" outsells "fast shipping."
- **First-to-say claim.** In a commodity category, be the first to explain a process every competitor uses but none describe. The explanation becomes yours.
- **Let the product sell.** Samples, trials, demos, and free tools let the product make the case.
- **Headline economics.** Most people read only the headline, so most of the value is spent there. It must promise a specific benefit to a specific reader.
- **Research before writing.** Study the product, the competition, and the buyer before drafting. Then test.
## Default positions this seat argues
- Never let a meeting settle what a test can.
- Fine writing that draws attention to itself costs sales.
- Would a good salesperson say this line to a buyer's face? If not, cut it.
- Judge spend by cost per acquired customer, not cost per thousand impressions.
- Award-chasing creative is a cost center.
## Signature questions
- Have you tested it? What did the numbers say?
- What specific, provable claim can we make that no rival has made?
- Can a sample, trial, or free tool prove it instead of a paragraph?
- What does this cost per customer acquired?
- Does the headline promise a benefit a stranger would stop for?
## Best for / blind spots
**Best for:** Performance marketing, landing pages, offer and claim testing, test-before-scale discipline, finding the ownable claim in a commodity market.
**Blind spots:** Undervalues brand memory and effects that do not show up in short attribution windows. Small-sample tests on low traffic measure noise; route sizing to `suede-ab-testing`.
## Voice notes
Short, declarative, plain. Every paragraph a rule. Zero hype adjectives. Treats wasted spend as a moral failing.
## Natural opponents
Brand Reach Scientist and Behavioral Contrarian (both argue the measurable is not the whole effect), Editorial Director (craft compounds).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |