product-marketing
This skill helps agents develop product positioning, messaging frameworks, and go-to-market strategies using the April Dunford method.
Community author
- Agents
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
- License
- MIT (permissive)
- Pin
- 28bf209pinned Oct 9, 2026
- Context cost
- about 1,900 tokenswhen the skill loads
- GitHub stars
- 711on openclaudia/openclaudia-skills
- Scripts
- None found
What it does
“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.”
Generated summary from the skill's own text
This skill helps agents develop product positioning, messaging frameworks, and go-to-market strategies using the April Dunford method. It provides templates for competitive analysis, battlecards, sales enablement materials, and launch planning across different go-to-market tiers.
When to use it
- Developing positioning strategy for a new product or rebrand
- Creating messaging frameworks for different audience segments
- Building competitive battlecards and win/loss analysis
- Planning product launches or major feature releases
When not to
- Short-term tactical marketing campaigns or paid ads
- Content creation for existing marketing channels
- Product development or feature prioritization decisions
Install
These commands install from the publisher's repository and need no account.
skills CLI
npx skills add openclaudia/openclaudia-skills --skill product-marketingInstalls from the repository's default branch, which may have changed since the commit we checked.
GitHub CLI 2.90 or later
gh skill install openclaudia/openclaudia-skills product-marketing@28bf209f393aa78dcd56636faed941af5a2537abInstalls the commit we checked (28bf209).
Copy by hand
Download the folder at 28bf209 and put it in .claude/skills/product-marketing for Claude Code and in .agents/skills/product-marketing for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.
Copy for your agent
A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.
Prompt
Install the agent skill "product-marketing" by OpenClaudia. Source, pinned to commit 28bf209f393aa78dcd56636faed941af5a2537ab: https://github.com/openclaudia/openclaudia-skills/tree/28bf209f393aa78dcd56636faed941af5a2537ab/skills/product-marketing 1. Download that folder at exactly this commit. Do not use the default branch. 2. Copy every file unchanged, keeping the folder structure, into .claude/skills/product-marketing/ for Claude Code and .agents/skills/product-marketing/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist. 3. Do not edit the files, and do not run any script in the folder unless I ask you to. 4. When you are done, list the files you copied and where you put them. Listing and checks: https://www.agentnative.dev/skills/openclaudia/product-marketing
SKILL.md at the pin
---
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 → Proof
```
### Messaging 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:
```markdown
# 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, Twitter, LinkedIn)
□ Partner/integration co-marketing
POST-LAUNCH (+2 weeks)
□ Follow-up content (case study, deep dive, tutorial)
□ Retargeting ads to landing page visitors
□ Win/loss tracking on new deals
□ Performance metrics review
□ Iterate messaging based on response
```
### Sales Enablement Package
For each product or major feature, create:
1. **One-pager** — Single page overview for prospects
2. **Pitch deck** — 10-15 slide presentation
3. **Demo script** — Guided walkthrough of key use cases
4. **Battlecards** — Per-competitor comparison (see above)
5. **ROI calculator** — Spreadsheet showing value vs. cost
6. **Case studies** — Customer success stories with metrics
7. **FAQ** — Common questions from prospects
## Output Format
```markdown
# Product Marketing Strategy: {Product}
## Positioning
**For** {target customer} **who** {need/situation},
**{Product}** is a {category} that {key benefit}.
**Unlike** {alternative}, we {differentiator}.
## Value Propositions
1. **{Pillar 1}:** {Benefit + proof}
2. **{Pillar 2}:** {Benefit + proof}
3. **{Pillar 3}:** {Benefit + proof}
## Messaging Matrix
| Audience | Headline | Key Message | Proof Point |
|----------|----------|------------|-------------|
## Competitive Landscape
{Positioning map or comparison table}
## GTM Plan
{Launch tier and timeline}
## Sales Enablement
{Materials needed and status}
## Success Metrics
| Metric | Baseline | Target | Timeline |
```
## Important Notes
- Positioning is not tagline writing. It's a strategic decision about how to frame your product in the market.
- Talk to customers before finalizing positioning. Internal assumptions are often wrong.
- Refresh battlecards quarterly. Competitors change fast.
- The best positioning makes the competition irrelevant rather than inferior.
- Don't try to be everything to everyone. Strong positioning means saying no to some audiences.
From openclaudia/openclaudia-skills at 28bf209, shown as plain text under its license: MIT (permissive). The license text is in LICENSE.
View SKILL.md on GitHub at 28bf209Files
- SKILL.md8.0 KB · 230e22f0d05d
1 file, 8.0 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.
Skill folder on GitHub at 28bf209Related in Marketing, sales and product
accelo-automation
This skill enables agents to automate Accelo project management tasks by discovering and executing operations through Composio's Accelo toolkit via Rube MCP.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 6 days ago
acculynx-automation
This skill automates Acculynx operations by discovering and executing available tools through the Rube MCP server.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 6 days ago
active-campaign-automation
This skill automates ActiveCampaign tasks by discovering and executing tools through Rube MCP and Composio's ActiveCampaign toolkit.
by ComposioOfficial publisher
Agents not labelled yet · about 710 tokens · pinned 6 days ago
adrapid-automation
This skill enables agents to automate Adrapid tasks through Composio's toolkit via Rube MCP.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 6 days ago
aeroleads-automation
This skill automates Aeroleads tasks by connecting to the Aeroleads toolkit via Composio's Rube MCP server.
by ComposioOfficial publisher
Agents not labelled yet · about 700 tokens · pinned 6 days ago
affinity-automation
This skill automates Affinity CRM operations by executing tools through Rube MCP and Composio's Affinity toolkit.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 6 days ago