Specialist Lenses

Check for product marketing context first: If .agents/marketing-strategy.md exists (or the legacy .agents/product-marketing.md, .claude/product-marketing.md, or product-marketing-context.md filenames), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Also check .agents/marketing-learnings.md if it exists — past entries tagged to this channel capture what already worked or failed; apply that before drafting from scratch (see compound-marketing).

A growing library of narrow-domain marketing specialists — each entry built from what they've genuinely published for free (talks, blog posts, podcasts, free newsletter issues), never their paywalled content. Where marketing-council runs a simulated boardroom of broadly-known "legendary marketer" personas, this skill goes narrower and more tactical: one specialist, one domain, applied directly to the problem in front of you.

Grounding Rules (non-negotiable — stricter than marketing-council's)

Every specialist here is a living person actively selling their expertise (a paid newsletter, a consultancy, a course). That raises the bar above marketing-council's historical-figure entries:

• Public content only. Every framework described must be sourced from something the specialist published for free — a public talk, a free blog post, an interview, a free newsletter issue. Never their paywalled material, even paraphrased.
• Cite the source. Each specialist file ends with a Sources list. If you can't point to where a claim came from, don't include the claim.
• Flag confidence honestly. Where research is thin or a framework name isn't independently confirmed as the specialist's own official terminology, say so explicitly in the file (see adam-posner.md for the pattern) rather than presenting it with false authority.
• No fabricated quotes or opinions about the user's business. Apply the specialist's framework to the situation; never state or imply the real person has reviewed or has an opinion about the user's specific company.
• Time-sensitive fields decay fast. A specific number or stat (a study's percentage, a current framework name) is a snapshot from when it was researched — say so, and point to the live source for anything the user might repeat externally.
• Never treat this as a substitute for the actual subscription. If the user's question needs depth beyond what's here, say so plainly and point them to the specialist's paid work rather than guessing past what's grounded.

How to Use This Skill