Agent skill
product-marketing
Build product marketing strategy including positioning, messaging, and go-to-market.
Filed under Positioning and messaging.
From OpenClaudia/openclaudia-skills · 61 skills · 664 · pushed 2026-08-25
What it does when it runs
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.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/OpenClaudia/openclaudia-skills.git /tmp/openclaudia-skills git -C /tmp/openclaudia-skills sparse-checkout set "skills/product-marketing" mkdir -p ~/.claude/skills/product-marketing cp -R "/tmp/openclaudia-skills/skills/product-marketing/." ~/.claude/skills/product-marketing/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from OpenClaudia/openclaudia-skills/blob/221b37d7ab95c14d5343c7b24fd9f9367a3fb400/skills/product-marketing/SKILL.md, which is licensed MIT (repository). 1,129 words, 34 headings.
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:
# 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:
- One-pager — Single page overview for prospects
- Pitch deck — 10-15 slide presentation
- Demo script — Guided walkthrough of key use cases
- Battlecards — Per-competitor comparison (see above)
- ROI calculator — Spreadsheet showing value vs. cost
- Case studies — Customer success stories with metrics
- 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.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- product-marketing by coreyhaines31 · 45,947
- marketing-product-ideas by realjaymes · 55
- product-marketing-metrics by realjaymes · 55
- product-marketing-ops by shalintripathi · 7
- co-marketing by coreyhaines31 · 45,947
- community-marketing by coreyhaines31 · 45,947
- influencer-marketing by coreyhaines31 · 45,947
- marketing-council by coreyhaines31 · 45,947
Need help setting it up?
This page tells you what product-marketing does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.