
Product Marketing
- 339 installs
- 614 repo stars
- Updated August 5, 2026
- openclaudia/openclaudia-skills
product-marketing is a Claude Code agent skill that crafts positioning, messaging, launch narratives, and go-to-market assets so a shipped product is understood, differentiated, and adopted by the right buyers.
About
product-marketing is an agent skill for developers and technical founders shipping products who need structured go-to-market work inside the coding assistant. The skill builds positioning using the April Dunford method—competitive alternatives, unique attributes, value themes, and target segments—then produces messaging frameworks, competitive battlecards, sales enablement outlines, and launch plans. Trigger phrases include positioning, messaging framework, GTM strategy, competitive positioning, battlecard, sales enablement, and launch plan. product-marketing fits the gap between a working codebase and market clarity: teams with a shippable API, SaaS, or mobile app use it to articulate differentiation before App Store pages, landing copy, or sales conversations go live.
- Positioning and messaging hierarchy
- Launch checklist and narrative arcs
- Persona and jobs-to-be-done framing
- Competitive differentiation templates
- Sales and self-serve asset outlines
Product Marketing by the numbers
- 339 all-time installs (skills.sh)
- +16 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #225 of 853 Sales & Marketing skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/openclaudia/openclaudia-skills --skill product-marketingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 339 |
|---|---|
| repo stars | ★ 614 |
| Last updated | August 5, 2026 |
| Repository | openclaudia/openclaudia-skills ↗ |
How do you write product positioning and GTM messaging?
Craft positioning, messaging, launch narratives, and go-to-market assets so a shipped product is understood, differentiated, and adopted by the right buyers.
Who is it for?
Technical founders and developer-led teams launching a SaaS, API, or mobile product who need structured positioning and GTM messaging.
Skip if: Teams needing paid ad campaign execution, SEO technical audits, or in-depth competitor web scraping automation.
When should I use this skill?
User mentions positioning, messaging framework, GTM strategy, battlecard, sales enablement, launch plan, or competitive positioning.
What you get
Positioning document, messaging framework, competitive battlecard, and go-to-market launch plan artifacts.
- positioning document
- messaging framework
- go-to-market launch plan
Files
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, 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 responseSales 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
# 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.
Related skills
FAQ
What positioning method does product-marketing use?
product-marketing applies the April Dunford positioning framework, walking through competitive alternatives, unique attributes, value themes, and target customer segments before drafting messaging.
What artifacts does product-marketing generate?
product-marketing produces positioning documents, messaging frameworks, competitive battlecards, sales enablement outlines, and go-to-market launch plans for shipped technical products.