marketing-strategy-pmm
Skill0 starsChanged 6 months agoMITView on GitHub
Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry.
8 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- darkweb19/skillsedited, first seen Nov 8, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
- I-Onlabs/claude-code-skillstheir own version, first seen Oct 25, 2026
- Hassaan146/claude-skillsedited, first seen Jul 25, 2026
- mahiunfiltered/claude-code-skillsedited, first seen Jul 8, 2026
- Hussain-Elfalah/Agentic-Skillsedited, first seen Jun 4, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Hassaan146/claude-skills★ 1884% same
- Hussain-Elfalah/Agentic-Skills★ 283% same
- mahiunfiltered/claude-code-skills★ 184% same
- darkweb19/skills★ 084% same
- Getampz/Skills★ 084% same
Wrote their own version · 3
- I-Onlabs/claude-code-skills★ 4same name
- OpenxIntelligence/Coding-Agent-Skills★ 4same name
- harriswat/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ad-first-marketingSkill
- afrexai-community-growth-engineSkill
- agent-fleet-statusSkill
- agentgramSkill
- ai-cold-emailSkill
- answeroverflowSkill
- answeroverflowSkill
- api-gatewaySkill
- apple-notesSkill
- autonomous-operatorSkill
- autonomous-revenueSkill
- brand-analyzerSkill
- brand-identitySkill
- brand-operatorSkill
- browser-useSkill
- byteroverSkill
- calendlySkill
- clawdcursorSkill
- clawd-provisionerSkill
- client-acquisitionSkill
- cold-email-writerSkill
- cold-outreachSkill
- Community ManagerSkill
- community-mod-packSkill
- competitive-ads-extractorSkill
- competitor-analyzerSkill
- content-engineSkill
- content-qa-scorerSkill
- content-repurposeSkill
- cron-automatorSkill
- daily-brief-generatorSkill
- deep-researchSkill
- elite-longterm-memorySkill
- email-responderSkill
- fathom-tele-tvSkill
- fleet-commanderSkill
- frontend-designSkill
- gogSkill
- himalayaSkill
- imsgSkill
- internet-marketingSkill
- klaviyoSkill
- knowledge-extractorSkill
- koino-frontendSkill
- lead-research-assistantSkill
- lead-scorerSkill
- macos-calendarSkill
- marketing-drafterSkill
- marketingSkill
- master-marketingSkill
- meeting-prepSkill
- moltbookSkill
- moltguardSkill
- objection-destroyerSkill
- ontologySkill
- pipeline-autopilotSkill
- marketing-ideasSkill
- proactive-agentSkill
- proposal-generatorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 7 are common, 0 are distinctive, and 0 are very specific to this project.
7
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 43
Document psychographics (pain level, motivation, risk tolerance)
- Common: line 97
Test with 10+ customer interviews
- Common: line 137
Read G2/Capterra reviews (pros and cons)
- Common: line 210
Create sales enablement (deck, demo, battlecard)
- Common: line 242
Create sales deck (15-20 slides, visual-first)
- Common: line 245
Write email templates (outreach, follow-up, closing)
- Common: line 246
Create ROI calculator (input costs, output savings)
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing Strategy & PMM
Product marketing patterns for positioning, GTM strategy, and competitive intelligence.
Table of Contents
- ICP Definition Workflow
- Positioning Development
- Competitive Intelligence
- Product Launch Planning
- Sales Enablement
- International Expansion
- Reference Documentation
ICP Definition Workflow
Define ideal customer profile for targeting:
- Analyze existing customers (top 20% by LTV)
- Identify common firmographics (size, industry, revenue)
- Map technographics (tools, maturity, integrations)
- Document psychographics (pain level, motivation, risk tolerance)
- Define 3-5 buyer personas (economic, technical, user)
- Validate against sales cycle and churn data
- Score prospects A/B/C/D based on ICP fit
- Validation: A-fit customers have lowest churn and fastest close
Firmographics Template
| Dimension | Target Range | Rationale |
| Employees | 50-5000 | Series A sweet spot |
| Revenue | $5M-$500M | Budget available |
| Industry | SaaS, Tech, Services | Product fit |
| Geography | US, UK, DACH | Market priority |
| Funding | Seed to Growth | Willing to adopt |
Buyer Personas
Economic Buyer (signs contract):
- Title: VP, Director, Head of [Department]
- Goals: ROI, team productivity, cost reduction
- Messaging: Business outcomes, ROI, case studies
Technical Buyer (evaluates product):
- Title: Engineer, Architect, Tech Lead
- Goals: Technical fit, easy integration
- Messaging: Architecture, security, documentation
User/Champion (advocates internally):
- Title: Manager, Team Lead, Power User
- Goals: Makes job easier, quick wins
- Messaging: UX, ease of use, time savings
ICP Validation Checklist
- 5+ paying customers match this profile
- Fastest sales cycles (< median)
- Highest LTV (> median)
- Lowest churn (< 5% annual)
- Strong product engagement
- Willing to do case studies
Positioning Development
Develop positioning using April Dunford methodology:
- List competitive alternatives (direct, adjacent, status quo)
- Isolate unique attributes (features only you have)
- Map attributes to customer value (why it matters)
- Define best-fit customers (who cares most)
- Choose market category (head-to-head, niche, new category)
- Layer on relevant trends (timing justification)
- Test with 10+ customer interviews
- Validation: 7+ customers describe value unprompted
Positioning Statement Template
FOR [target customer]
WHO [statement of need]
THE [product] IS A [category]
THAT [key benefit]
UNLIKE [competitive alternative]
OUR PRODUCT [primary differentiation]Value Proposition Formula
Template: [Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]
Example: "Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI"
Messaging Hierarchy
| Level | Content | Example |
| Headline | 5-7 words | "Ship faster with AI automation" |
| Subhead | 1 sentence | "Automate workflows so teams focus on what matters" |
| Benefits | 3-4 bullets | Speed, quality, collaboration, cost |
| Features | Supporting evidence | AI automation → 10 hrs/week saved |
| Proof | Social proof | Customer logos, stats, case studies |
Competitive Intelligence
Build competitive knowledge base:
- Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo)
- Sign up for competitor products (hands-on evaluation)
- Monitor competitor websites, pricing, messaging
- Analyze sales call recordings for competitor mentions
- Read G2/Capterra reviews (pros and cons)
- Track competitor job postings (roadmap signals)
- Update battlecards monthly
- Validation: Sales team uses battlecards in 80%+ competitive deals
Competitive Tier Structure
| Tier | Definition | Examples |
| 1 | Direct competitor, same category | [Competitor A, B] |
| 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] |
| 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |
Battlecard Template
COMPETITOR: [Name]
OVERVIEW: Founded [year], Funding [stage], Size [employees]
POSITIONING:
- They say: "[Their claim]"
- Reality: [Your assessment]
STRENGTHS:
1. [What they do well]
2. [What they do well]
WEAKNESSES:
1. [Where they fall short]
2. [Where they fall short]
OUR ADVANTAGES:
1. [Your advantage + evidence]
2. [Your advantage + evidence]
WHEN WE WIN:
- [Scenario where you win]
WHEN WE LOSE:
- [Scenario where they win]
TALK TRACK:
Objection: "[Common objection]"
Response: "[Your response]"Win/Loss Analysis
Track monthly:
- Win rate by competitor
- Top win reasons (product fit, ease of use, price)
- Top loss reasons (missing feature, price, relationship)
- Action items for product, sales, marketing
Product Launch Planning
Plan launches by tier:
| Tier | Scope | Prep Time | Budget |
| 1 | New product, major feature | 6-8 weeks | $50-100k |
| 2 | Significant feature, integration | 3-4 weeks | $10-25k |
| 3 | Small improvement | 1 week | <$5k |
Tier 1 Launch Workflow
Execute major product launch:
- Kickoff meeting with Product, Marketing, Sales, CS
- Define goals (pipeline $, MQLs, press coverage)
- Develop positioning and messaging
- Create sales enablement (deck, demo, battlecard)
- Build campaign assets (landing page, emails, ads)
- Train sales and CS teams
- Execute launch day (press, email, ads, outbound)
- Monitor and optimize for 30 days
- Validation: Pipeline on track to goal by week 2
Launch Day Checklist
- Press release distributed
- Email announcement sent
- Social media posts live
- Paid ads at full budget
- Sales outbound blitz launched
- In-app notification active
- Metrics monitored every 2 hours
Launch Metrics
| Metric | Leading (Daily) | Lagging (Weekly) |
| Traffic | Landing page visitors | - |
| Engagement | Demo requests, signups | Feature adoption % |
| Pipeline | MQLs generated | SQLs, pipeline $ |
| Revenue | - | Deals closed, revenue |
Sales Enablement
Equip sales team with PMM assets:
- Create sales deck (15-20 slides, visual-first)
- Build one-pagers (product, competitive, case study)
- Develop demo script (30-45 min with discovery)
- Write email templates (outreach, follow-up, closing)
- Create ROI calculator (input costs, output savings)
- Conduct monthly enablement calls
- Deliver quarterly training (positioning, competitive)
- Validation: Sales uses assets in 80%+ of opportunities
Sales Deck Structure
| Slide | Content |
| 1-2 | Title, agenda |
| 3-4 | Company intro, problem statement |
| 5-7 | Solution, key benefits, demo |
| 8-10 | Differentiation, case study, pricing |
| 11-12 | Implementation, support, next steps |
Demo Flow
1. Intro (2 min): Who we are, agenda
2. Discovery (5 min): Their needs, pain points
3. Demo (20 min): Product focused on their use case
4. Q&A (10 min): Objection handling
5. Next steps (3 min): Trial, POC, proposalSales-Marketing Handoff
| Handoff | Frequency | Content |
| Weekly sync | 30 min | Win/loss, competitive, new assets |
| Monthly enablement | 60 min | Product updates, training |
| Quarterly review | Half-day | Results, strategy, planning |
International Expansion
Enter new markets systematically:
- Validate market demand (inbound leads, TAM analysis)
- Localize website, pricing, legal
- Establish sales coverage (hire or agency)
- Adapt messaging for cultural fit
- Build local partnerships and references
- Launch localized campaigns
- Monitor CAC and conversion by market
- Validation: 3+ paying customers from market in first 90 days
Market Priority (Series A)
| Market | Timeline | Budget % | Target ARR |
| US | Months 1-6 | 50% | $1M |
| UK | Months 4-9 | 20% | $500k |
| DACH | Months 7-12 | 15% | $300k |
| France | Months 10-15 | 10% | $200k |
| Canada | Months 7-12 | 5% | $100k |
Localization Checklist
- Website translation (professional, not machine)
- Currency and pricing localized
- Local phone number and address
- Legal compliance (GDPR, PIPEDA)
- Local payment methods
- Sales coverage during local hours
- Local case studies and references
Reference Documentation
Positioning Frameworks
references/positioning-frameworks.md contains:
- April Dunford 5-step positioning process
- Geoffrey Moore positioning statement template
- Positioning validation interview protocol
- Competitive positioning map construction
Launch Checklists
references/launch-checklists.md contains:
- Tier 1/2/3 launch checklists
- Week-by-week launch timeline
- Launch day runbook
- Post-launch metrics dashboard
International GTM
references/international-gtm.md contains:
- US, UK, DACH, France, Canada playbooks
- Market-specific channel mix and messaging
- Localization requirements per market
- Entry timeline and budget allocation
Messaging Templates
references/messaging-templates.md contains:
- Value proposition formulas
- Persona-specific messaging
- Competitive response scripts
- Objection handling templates
- Channel-specific copy (landing pages, emails, ads)
PMM KPIs
| Metric | Target | Measurement |
| Product adoption | >40% in 90 days | Feature usage after launch |
| Win rate | >30% competitive | Deals won vs. competitors |
| Sales velocity | -20% YoY | Days from SQL to close |
| Deal size | +25% YoY | Average contract value |
| Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |
Quick Reference
PMM Monthly Rhythm
| Week | Focus |
| 1 | Review metrics, update battlecards |
| 2 | Create assets, publish content |
| 3 | Support launches, optimize campaigns |
| 4 | Monthly report, plan next month |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

