product-marketing

A one-off interview about your product — who buys it, what problem it solves, how you talk about it — written up as a single file that the other marketing skills here read first, so you stop explaining yourself over and over.

WHEN TO USE

SCOPE

USE FOR

Have a first draft written for you from your website and existing product docs.
Capture verbatim customer language so copy sounds like real buyers talk.
Document your ideal customer profile, personas, and buying committee for a B2B product.
Record your top three sales objections and how reps should answer them.
Update one section later and keep a dated record of what changed and why.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (6)

Product Marketing Context

You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.

The document is stored at .agents/product-marketing.md.

Workflow

Step 1: Check for Existing Context

First, check if .agents/product-marketing.md already exists. Also check .claude/product-marketing.md and the legacy filename product-marketing-context.md (in either .agents/ or .claude/) for older setups — if found anywhere other than .agents/product-marketing.md, offer to move it to the canonical location.

If it exists:

Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
Ask which sections they want to update
Only gather info for those sections
On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.

If it doesn't exist, offer two options:

Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
Start from scratch: Walk through each section conversationally, gathering info one section at a time.

Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"

Step 2: Gather Information

If auto-drafting:

Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
Draft all sections based on what you find
Present the draft and ask what needs correcting or is missing
Iterate until the user is satisfied

If starting from scratch: Walk through each section below conversationally, one at a time. Don't dump all questions at once.

For each section:

Briefly explain what you're capturing
Ask relevant questions
Confirm accuracy
Move to the next

Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.

Sections to Capture

1. Product Overview

One-line description
What it does (2-3 sentences)
Product category (what "shelf" you sit on—how customers search for you)
Product type (SaaS, marketplace, e-commerce, service, etc.)
Business model and pricing

2. Target Audience

Target company type (industry, size, stage)
Target decision-makers (roles, departments)
Primary use case (the main problem you solve)
Jobs to be done (2-3 things customers "hire" you for)
Specific use cases or scenarios

3. Personas (B2B only)

If multiple stakeholders are involved in buying, capture for each:

User, Champion, Decision Maker, Financial Buyer, Technical Influencer
What each cares about, their challenge, and the value you promise them

4. Problems & Pain Points

Core challenge customers face before finding you
Why current solutions fall short
What it costs them (time, money, opportunities)
Emotional tension (stress, fear, doubt)

5. Competitive Landscape

Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
How each falls short for customers

6. Differentiation

Key differentiators (capabilities alternatives lack)
How you solve it differently
Why that's better (benefits)
Why customers choose you over alternatives

7. Objections & Anti-Personas

Top 3 objections heard in sales and how to address them
Who is NOT a good fit (anti-persona)

8. Switching Dynamics

The JTBD Four Forces:

Push: What frustrations drive them away from current solution
Pull: What attracts them to you
Habit: What keeps them stuck with current approach
Anxiety: What worries them about switching

9. Customer Language

How customers describe the problem (verbatim)
How they describe your solution (verbatim)
Words/phrases to use
Words/phrases to avoid
Glossary of product-specific terms

10. Brand Voice

Tone (professional, casual, playful, etc.)
Communication style (direct, conversational, technical)
Brand personality (3-5 adjectives)

11. Proof Points

Key metrics or results to cite
Notable customers/logos
Testimonial snippets
Main value themes and supporting evidence

12. Goals

Primary business goal
Key conversion action (what you want people to do)
Current metrics (if known)

Step 3: Create the Document

After gathering information, create .agents/product-marketing.md with this structure:

# Product Marketing Context

**Document version:** v1
**Last updated:** [date]

## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**

## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-

## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |

## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**

## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...

## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**

## Objections
| Objection | Response |
|-----------|----------|
| | |

**Anti-persona:**

## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**

## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |

## Brand Voice
**Tone:**
**Style:**
**Personality:**

## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |

## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**

## Changelog
*Newest first. One line per revision: what changed and why.*
- v1 ([date]) — Initial context.

Step 4: Confirm, Version, and Save

Show the completed document
Ask if anything needs adjustment
Set the version and changelog — this is the paper trail for a doc every other skill reads:
- New document: set Document version: v1 and a single Changelog entry — - v1 ([today]) — Initial context.
- Updating an existing document: increment the version (v2 → v3 …), update Last updated to today, and prepend a new Changelog entry at the top of the list (newest first) summarizing what changed and why in one line. Never rewrite or reorder past entries.
- A good entry names the sections touched and the reason, not "updated the doc." Examples:
  - - v3 (2026-07-16) — Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP.
  - - v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.
- Use today's date in ISO form (YYYY-MM-DD) for the entry and Last updated.
- Pure typo-only fix: don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context.
Save to .agents/product-marketing.md
Tell them: "Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run /product-marketing anytime to update it."

Tips

Be specific: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
Capture exact words: Customer language beats polished descriptions
Ask for examples: "Can you give me an example?" unlocks better answers
Validate as you go: Summarize each section and confirm before moving on
Skip what doesn't apply: Not every product needs all sections (e.g., Personas for B2C)

This skill ships inside the Marketing Skills for AI Agents plugin.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add coreyhaines31/marketingskills --skill "product-marketing" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Marketing Skills for AI Agents plugin package selected for your AI tool.

Add the marketplace, then install the plugin

Type both lines inside a Claude Code session, not at your shell prompt. They add Corey's marketplace, which is this repository, and the marketing-skills plugin, with all 50 skills.

/plugin marketplace add coreyhaines31/marketingskills

02
```
/plugin install marketing-skills
```

Installation and loading

The second line opens the plugin's details; Claude Code installs it once you pick one of the install options shown.

Good to know

/plugin does not work in Claude Code on the web, GitHub Actions or other non-interactive setups. For those, Corey gives a shell form: claude plugin marketplace add coreyhaines31/marketingskills, then claude plugin install marketing-skills@marketingskills.

Add the marketplace, then pick the plugin in Codex

Run the first line in your terminal to add Corey's marketplace, which is this repository. Then start a Codex session, type /plugins and select marketing-skills to install all 50 skills. To get new releases later, run codex plugin marketplace upgrade.

codex plugin marketplace add coreyhaines31/marketingskills

02
```
/plugins
```

Open plugin page ↗

What's inside

Files included with this skill.

View on GitHub

Same repository

ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.Read full description
ad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.Read full description
ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' or 'when should I kill an ad.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro.Read full description
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.Read full description
analytics
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.Read full description
aso
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.Read full description