/product-marketing
Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or
$ npx -y skills add openclaudia/openclaudia-skills --skill product-marketing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/product-marketing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or
SKILL.md
product-marketing.SKILL.mdname: product-marketing
description: Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or asks about how to position or message their product in the market.
Product Marketing Skill
You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies.
Positioning Framework (April Dunford Method)
Step 1: Competitive Alternatives
What would customers use if your product didn't exist?
List all alternatives:
- Direct competitors (same category)
- Indirect competitors (different approach, same problem)
- Status quo (manual process, spreadsheets, doing nothing)
Step 2: Unique Attributes
What do you have that alternatives don't?
| Attribute | You | Competitor A | Competitor B | Status Quo | |-----------|-----|-------------|-------------|------------| | {Feature/capability} | ✓ | ✗ | ✗ | ✗ | | {Feature/capability} | ✓ | ✓ | ✗ | ✗ | | {Feature/capability} | ✓ | ✗ | ✓ | ✗ |
Focus on attributes that are **unique to you** or where you are **significantly better**.
Step 3: Value (So What?)
For each unique attribute, answer "So what? Why does the customer care?"
| Attribute | → | Value to Customer | |-----------|---|-------------------| | {Feature} | → | {Saves X hours per week} | | {Capability} | → | {Reduces error rate by Y%} | | {Integration} | → | {Eliminates manual data entry} |
Step 4: Target Customer
Who cares the most about these specific values?
Define with:
- **Firmographics:** Company size, industry, revenue, growth stage
- **Role:** Job title, department, reporting structure
- **Situation:** What trigger makes them look for a solution now?
- **Characteristics:** What makes them a great vs. okay customer?
Step 5: Market Category
What category context makes your value obvious?
Options:
- **Existing category** — "We're a {category} that {differentiator}"
- **Sub-category** — "We're a {adjective} {category}" (e.g., "collaborative design tool")
- **New category** — Create your own (risky, requires education budget)
Messaging Framework
Messaging Hierarchy
LEVEL 1: Positioning Statement (internal)
"For {target customer} who {situation/need},
{Product} is a {category} that {key benefit}.
Unlike {alternative}, we {key differentiator}."
LEVEL 2: Value Propositions (3 pillars)
Pillar 1: {Benefit} — Because {proof point}
Pillar 2: {Benefit} — Because {proof point}
Pillar 3: {Benefit} — Because {proof point}
LEVEL 3: Headlines & Taglines (external-facing)
Homepage: {Compelling headline}
Subhead: {Supporting detail}
LEVEL 4: Feature Messages (per feature/capability)
Feature → Benefit → ProofMessaging by Audience
| Audience | They Care About | Messaging Emphasis | |----------|----------------|-------------------| | End user | Day-to-day workflow improvement | Ease of use, time savings | | Manager | Team productivity, oversight | Collaboration, reporting | | Executive | Business outcomes, ROI | Revenue impact, cost reduction | | Technical | Implementation, security | Architecture, APIs, compliance | | Procurement | Risk, compliance, cost | Security, SLA, pricing model |
Competitive Intelligence
Battlecard Template
Create for each key competitor:
# Battlecard: {Your Product} vs {Competitor}
## Quick Facts
- **Their positioning:** {How they describe themselves}
- **Pricing:** {Their pricing model and tiers}
- **Target customer:** {Who they sell to}
- **Strengths:** {Honest assessment}
- **Weaknesses:** {Where they fall short}
## Where We Win
| Scenario | Why We Win | Talk Track |
|----------|-----------|------------|
| {Use case} | {Our advantage} | "{What to say to the prospect}" |
## Where They Win
| Scenario | Why They Win | Counter |
|----------|-------------|---------|
| {Use case} | {Their advantage} | "{How to reframe}" |
## Common Objections
| Objection | Response |
|-----------|----------|
| "They're cheaper" | "{Value-based response}" |
| "They have {feature}" | "{Reframe or roadmap response}" |
| "They're the market leader" | "{Category leadership angle}" |
## Landmines (Questions to Ask Prospects)
- "{Question that highlights competitor weakness}"
- "{Question that highlights your strength}"
## Win/Loss Insights
- Win rate vs this competitor: {%}
- Common deal sizes: {range}
- Average sales cycle: {days}Win/Loss Analysis Template
After each deal (won or lost), document:
| Field | Details | |-------|---------| | Outcome | Won / Lost | | Competitor(s) | {Who you competed against} | | Deal size | {Amount} | | Decision maker | {Title/role} | | Why they chose us / them | {Top 3 reasons} | | What could have changed the outcome | {Specific actions} | | Sales cycle length | {Days} |
Go-to-Market (GTM) Strategy
Launch Tiers
| Tier | When | Activities | Goal | |------|------|-----------|------| | **Tier 1: Major** | New product, pivot, rebrand | Press, event, campaign, all channels | Maximum awareness | | **Tier 2: Medium** | Major feature, integration | Blog, email, social, product in-app | Adoption + upgrades | | **Tier 3: Minor** | Feature update, improvement | Changelog, in-app notification, email | User awareness |
Launch Checklist (Tier 1)
PRE-LAUNCH (-4 weeks)
□ Positioning and messaging finalized
□ Landing page / product page created
□ Demo video or walkthrough produced
□ Press kit assembled (press release, images, founder bios)
□ Sales enablement materials created (deck, battlecard, FAQ)
□ Customer testimonials or beta feedback gathered
LAUNCH WEEK
□ Blog post published
□ Email to existing customers/subscribers
□ Social media campaign (all channels)
□ Press outreach (if newsworthy)
□ Product Hunt submission (if relevant)
□ Community posts (Reddit, Hacker News, Twi
Read more
name: product-marketing description: Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or asks about how to position or message their product in the market.
Product Marketing Skill
You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies.
Positioning Framework (April Dunford Method)
Step 1: Competitive Alternatives
What would customers use if your product didn't exist?
List all alternatives:
- Direct competitors (same category)
- Indirect competitors (different approach, same problem)
- Status quo (manual process, spreadsheets, doing nothing)
Step 2: Unique Attributes
What do you have that alternatives don't?
| Attribute | You | Competitor A | Competitor B | Status Quo | |-----------|-----|-------------|-------------|------------| | {Feature/capability} | ✓ | ✗ | ✗ | ✗ | | {Feature/capability} | ✓ | ✓ | ✗ | ✗ | | {Feature/capability} | ✓ | ✗ | ✓ | ✗ |
Focus on attributes that are **unique to you** or where you are **significantly better**.
Step 3: Value (So What?)
For each unique attribute, answer "So what? Why does the customer care?"
| Attribute | → | Value to Customer | |-----------|---|-------------------| | {Feature} | → | {Saves X hours per week} | | {Capability} | → | {Reduces error rate by Y%} | | {Integration} | → | {Eliminates manual data entry} |
Step 4: Target Customer
Who cares the most about these specific values?
Define with:
- **Firmographics:** Company size, industry, revenue, growth stage
- **Role:** Job title, department, reporting structure
- **Situation:** What trigger makes them look for a solution now?
- **Characteristics:** What makes them a great vs. okay customer?
Step 5: Market Category
What category context makes your value obvious?
Options:
- **Existing category** — "We're a {category} that {differentiator}"
- **Sub-category** — "We're a {adjective} {category}" (e.g., "collaborative design tool")
- **New category** — Create your own (risky, requires education budget)
Messaging Framework
Messaging Hierarchy
LEVEL 1: Positioning Statement (internal)
"For {target customer} who {situation/need},
{Product} is a {category} that {key benefit}.
Unlike {alternative}, we {key differentiator}."
LEVEL 2: Value Propositions (3 pillars)
Pillar 1: {Benefit} — Because {proof point}
Pillar 2: {Benefit} — Because {proof point}
Pillar 3: {Benefit} — Because {proof point}
LEVEL 3: Headlines & Taglines (external-facing)
Homepage: {Compelling headline}
Subhead: {Supporting detail}
LEVEL 4: Feature Messages (per feature/capability)
Feature → Benefit → ProofMessaging by Audience
| Audience | They Care About | Messaging Emphasis | |----------|----------------|-------------------| | End user | Day-to-day workflow improvement | Ease of use, time savings | | Manager | Team productivity, oversight | Collaboration, reporting | | Executive | Business outcomes, ROI | Revenue impact, cost reduction | | Technical | Implementation, security | Architecture, APIs, compliance | | Procurement | Risk, compliance, cost | Security, SLA, pricing model |
Competitive Intelligence
Battlecard Template
Create for each key competitor:
# Battlecard: {Your Product} vs {Competitor}
## Quick Facts
- **Their positioning:** {How they describe themselves}
- **Pricing:** {Their pricing model and tiers}
- **Target customer:** {Who they sell to}
- **Strengths:** {Honest assessment}
- **Weaknesses:** {Where they fall short}
## Where We Win
| Scenario | Why We Win | Talk Track |
|----------|-----------|------------|
| {Use case} | {Our advantage} | "{What to say to the prospect}" |
## Where They Win
| Scenario | Why They Win | Counter |
|----------|-------------|---------|
| {Use case} | {Their advantage} | "{How to reframe}" |
## Common Objections
| Objection | Response |
|-----------|----------|
| "They're cheaper" | "{Value-based response}" |
| "They have {feature}" | "{Reframe or roadmap response}" |
| "They're the market leader" | "{Category leadership angle}" |
## Landmines (Questions to Ask Prospects)
- "{Question that highlights competitor weakness}"
- "{Question that highlights your strength}"
## Win/Loss Insights
- Win rate vs this competitor: {%}
- Common deal sizes: {range}
- Average sales cycle: {days}Win/Loss Analysis Template
After each deal (won or lost), document:
| Field | Details | |-------|---------| | Outcome | Won / Lost | | Competitor(s) | {Who you competed against} | | Deal size | {Amount} | | Decision maker | {Title/role} | | Why they chose us / them | {Top 3 reasons} | | What could have changed the outcome | {Specific actions} | | Sales cycle length | {Days} |
Go-to-Market (GTM) Strategy
Launch Tiers
| Tier | When | Activities | Goal | |------|------|-----------|------| | **Tier 1: Major** | New product, pivot, rebrand | Press, event, campaign, all channels | Maximum awareness | | **Tier 2: Medium** | Major feature, integration | Blog, email, social, product in-app | Adoption + upgrades | | **Tier 3: Minor** | Feature update, improvement | Changelog, in-app notification, email | User awareness |
Launch Checklist (Tier 1)
PRE-LAUNCH (-4 weeks) □ Positioning and messaging finalized □ Landing page / product page created □ Demo video or walkthrough produced □ Press kit assembled (press release, images, founder bios) □ Sales enablement materials created (deck, battlecard, FAQ) □ Customer testimonials or beta feedback gathered LAUNCH WEEK □ Blog post published □ Email to existing customers/subscribers □ Social media campaign (all channels) □ Press outreach (if newsworthy) □ Product Hunt submission (if relevant) □ Community posts (Reddit, Hacker News, Twi
34 open-source marketing skills for Claude Code. SEO, content, email, ads, analytics, and growth.
Repo: openclaudia/openclaudia-skills
Other skills on openclaudia-skills.
- /ab-test-setup
Design, plan, and analyze A/B tests with statistical rigor. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, sample size calculation, test duration, multivariate testing, or conversion experiments. Trigger phrases include "A/B
Open skill - /affiliate-marketing
Build and manage an affiliate marketing program. Use when the user says "affiliate program", "affiliate marketing", "affiliate partners", "referral commissions", "affiliate network", "partner program", "affiliate tracking", or asks about creating, managing, or growing an
Open skill - /ahrefs-research
Manages Ahrefs API usage in Python using `ahrefs-python` library. Use when working with SEO / marketing related tasks or with data including backlinks, keywords, domain ratings, organic traffic, site audits, rank tracking, and brand monitoring. Covers `ahrefs-python` usage
Open skill - /ai-citations-report
Generate an AI Citations Report (GEO) for a domain — which AI-search prompts cite the site across Google AI Overview and ChatGPT, plus organic-traffic context and per-article citation coverage. Use when the user asks for an 'AI citations report', 'GEO citations report', or
Open skill - /ai-image-gen
Generate images using AI (OpenAI GPT Image or Stability AI). Use when the user asks to generate an image, create an AI image, make an illustration, or produce artwork from a text prompt.
Open skill - /apollo-outreach
Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of marketing at", or asks about finding people at specific
Open skill

