Positioning
Articulate why a product exists, who it serves, and what it replaces. Generates positioning statements, competitive angles, and category definitions. Use when launching something new, entering a crowded market, or when nobody can explain what the product does in one sentence.From its SKILL.md
npx -y skills add Dragoon0x/product-skills --skill positioningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.3 KB, 421 tokens by cl100k_base, as published. Nobody here has run it
Positioning
Articulate why a product exists, who it serves, and what it replaces.
How to use
/positioningApply positioning constraints to any product or feature work in this conversation./positioning <context>Generate a positioning framework for the described product or idea.
Constraints
Clarity First
- MUST be explainable in one sentence to someone outside the industry
- MUST name the specific person this is for, not "everyone" or "businesses"
- MUST state what this replaces or what people currently do instead
- NEVER use jargon in the primary positioning statement
- NEVER claim to be "the only" or "the first" without verifiable evidence
Positioning Statement Structure
- WHO: The specific person experiencing the problem (role, context, situation)
- PROBLEM: What they struggle with today, stated in their language
- SOLUTION: What this product does, in concrete terms
- DIFFERENCE: Why this approach is different from alternatives
- PROOF: Evidence that this works (metrics, testimonials, case studies)
Category Strategy
- MUST decide: are you entering an existing category or creating a new one
- If existing category: define your differentiation axis clearly
- If new category: name it in plain language, not marketing speak
- NEVER position against a competitor by name in the primary statement
- SHOULD frame the competition as the old way of doing things, not as enemies
Validation Checks
- Read the positioning statement aloud. Does it sound like a human talking?
- Remove every adjective. Does it still make sense?
- Show it to someone unfamiliar with the product. Can they repeat it back?
- If any answer is no, rewrite.
Anti-Patterns
- Stacking benefits without specificity ("fast, easy, powerful, flexible")
- Leading with features instead of the problem they solve
- Using superlatives that can't be proven
- Positioning for investors instead of users
- Trying to appeal to everyone, which means appealing to no one
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.