Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongtm-positioning-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches gtm-positioning-strategy from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gtm-positioning-strategy. Access via /gtm-positioning-strategy in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.
Triggers:
Context:
The Pattern:
Early enterprise conversations for an autonomous AI product. Positioned as "autonomous AI agent."
Developers: "Cool, but scary." Managers: "Will this replace our team?" Deal progression: Slow. Lots of "we'll think about it."
The Change:
One word: "autonomous" → "AI teammate"
Same product. Same capabilities. Different framing.
Result:
Developers: "This helps me." Managers: "This makes my team more productive." Deal progression: Measurably faster.
Why This Matters:
Positioning isn't what you do. It's what you don't say.
We could've said "replaces developers" (technically true for some tasks). Would've killed every enterprise deal.
The Framework: Word Choice Shapes Buyer Psychology
Words that scare enterprises:
Words that convert:
How to Test Word Choice:
Don't guess. Test.
Test 1: Outbound Email A/B
Test 2: Website Homepage A/B
Test 3: Sales Call Scripts
Common Mistake:
Changing positioning based on internal consensus, not customer feedback. Your team isn't the buyer.
The Pattern:
Positioning changes create risk. Brand confusion. Sales misalignment. Customer churn (if existing customers don't recognize you).
De-risk through phased rollout:
Crawl Phase (1-2 weeks): Validation
Test messaging without committing product/org resources.
Actions:
Measurement:
Go/No-Go:
Walk Phase (2-3 weeks): Alignment
If testing validates, align product and sales to new positioning (but don't rebrand publicly yet).
Actions:
Measurement:
Go/No-Go:
Run Phase (2-3 weeks and ongoing): Scale
Full commitment. This is the rebrand.
Actions:
Measurement:
Common Mistakes:
The Pattern:
If your messaging closely resembles competitors' messaging, you have a positioning problem, not a product problem.
Positioning Failure Manifests As:
How to Execute:
Step 1: Competitor Messaging Audit
Example:
If everyone says "fastest," "most reliable," "easiest to use" — these are table stakes, not differentiation.
Step 2: Assess Your Actual Strengths
Step 3: Find Under-Served Position
Step 4: Stake a Clear Claim
Must be:
Common Mistakes:
Layer 1: Market Context
Example: "Infrastructure teams manage increasingly complex deployments across hybrid environments. Organizations adopt microservices and distributed systems. This creates operational complexity that traditional monitoring tools can't handle."
Layer 2: Positioning Statement (1-2 sentences)
Example: "We help platform teams ship faster through [core capability] that connects [workflow A], [workflow B], and [business outcome] in real-time."
Layer 3: Narrative
Expand positioning into story:
How to Execute:
Write all three layers before testing. Test Layer 2 (positioning statement) first with Crawl-Walk-Run methodology. If that validates, build out Layer 3.
Principle: Clear positioning requires testable structure: headline (what are you?) + sub-headline (for whom? why?).
Main Headline Formats:
Examples:
Red Flags:
Sub-headline Purpose:
Clarifies who, why, how it's different from status quo.
Examples:
How to Test:
A/B test headline + sub-headline combinations:
Measure CTR, reply rates, conversion.
Pick winner based on data, not opinion.
Principle: A positioning is only valuable if competitors can't easily copy it.
Defensibility Hierarchy:
1. Structural Advantage (Strongest)
2. Market Position (Strong if First)
3. Product Feature (Weak)
How to Assess:
For each positioning claim, ask:
Common Mistake:
Positioning on features competitors can easily match. This creates positioning treadmill — you're always defending, never owning.
Is brand awareness strong but conversion weak?
├─ Yes → Positioning problem, test new angles
└─ No → Continue...
│
Does our messaging sound like competitors?
├─ Yes → Positioning problem
└─ No → Not a positioning issue
Do we have structural advantage competitors can't copy?
├─ Yes → Position on structural advantage
└─ No → Continue...
│
Are we first in a category?
├─ Yes → Position on category ownership
└─ No → Find under-served segment/use case
Did new positioning outperform incumbent by 20%+?
├─ Yes → Move to Walk (alignment phase)
└─ No → Continue...
│
Did we run test long enough (2+ weeks)?
├─ No → Run longer
└─ Yes → Try different positioning angle or stay with incumbent
1. Claiming to be "better" at what everyone does
2. Positioning on easily-copied features
3. Waiting for perfect product before positioning shift
4. Testing too many positioning angles simultaneously
5. Skipping validation phase
6. One positioning for all buyer personas
7. Generic positioning that doesn't differentiate
Crawl-Walk-Run Testing:
Word choice that converts:
Positioning audit steps:
Defensibility hierarchy:
Testing hierarchy (signal strength):
Based on positioning work at AI agent and developer platforms, including navigating the framing spectrum from "autonomous" to "AI companion" and how category framing changes enterprise buyer perception. Also includes Crawl-Walk-Run rollout methodology from repositioning products without breaking existing customer recognition. Not theory — patterns from testing positioning before committing to rebrands.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
I recommend gtm-positioning-strategy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gtm-positioning-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gtm-positioning-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
gtm-positioning-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for gtm-positioning-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend gtm-positioning-strategy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gtm-positioning-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for gtm-positioning-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
gtm-positioning-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
gtm-positioning-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64