Competitive framing
Skill Dragoon0x/product-skills/skills/strategy/competitive-framing
The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.
npx -y skills add Dragoon0x/product-skills --skill competitive-framingAssembled 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.
- 3 stars3 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.
What its author says it does
Copied from the file, not written here
Position against alternatives without being negative. Maps competitive landscape, identifies differentiation axes, and generates comparison frameworks. Use when building comparison pages, handling objections, or differentiating from existing solutions.
SKILL.md
1.9 KB, as published. Nobody here has run it
Competitive Framing
Position against alternatives without being negative.
How to use
/competitive-framingApply competitive framing constraints to this conversation./competitive-framing <product>Generate a competitive frame for the described product.
Constraints
Landscape Mapping
- MUST identify the real alternatives (including "do nothing" and manual workarounds)
- MUST map alternatives on 2-3 axes that matter to the target user
- NEVER define axes where you win on every dimension. That's not framing, that's fantasy.
- SHOULD acknowledge where alternatives are genuinely strong
Framing Rules
- Frame the shift, not the competitor. "Spreadsheets vs. purpose-built tools" not "Us vs. Excel"
- MUST lead with what you enable, not what others lack
- NEVER use negative language about competitors by name
- SHOULD use "before/after" framing over "us/them" framing
- MUST ground every comparison in observable, verifiable differences
Comparison Pages
- MUST be factually accurate. Verify every claim.
- SHOULD include dates for competitor feature checks (features change)
- MUST disclose if comparison data comes from public sources vs. direct testing
- NEVER cherry-pick metrics where you win while hiding areas where you don't
- SHOULD include a "best for" recommendation for each alternative, including honest cases where the competitor is the better choice
Anti-Patterns
- FUD (fear, uncertainty, doubt) tactics
- Comparing your roadmap to their current product
- Using outdated competitor information
- Making the comparison page the landing page (establish value first)
- Positioning against a competitor that your users have never heard of