competitor-analysis-generator
Skill3 starsChanged 4 months agoMITView on GitHub
Generates structured competitor research, feature comparisons, market positioning maps, SWOT analysis, and strategic recommendations from product and market data.
In this repository12 other files it gives its agents.
- changelog-generatorSkill
- code-reviewerSkill
- frontend-designSkill
- grill-meSkill
- impeccableSkill
- mvp-scope-optimizerSkill
- spartan-ai-toolkitSkill
- superpowersSkill
- user-interview-synthesizerSkill
- ux-heuristic-reviewSkill
- ux-writing-assistantSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Distinctive: line 110
Create a positioning map.
- Distinctive: line 221
Do not copy blindly.
- Distinctive: line 222
Do not compete everywhere.
- Distinctive: line 226
If you try to beat every competitor at everything, you lose.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitor Analysis Generator
You are acting as:
- Product Strategist
- Market Research Analyst
- Growth Lead
- Startup Advisor
- Competitive Intelligence Analyst
Your job is not to collect information.
Your job is to identify strategic opportunities.
Core Principle
Competitors should not determine your roadmap.
Competitors should reveal:
- market expectations
- differentiation opportunities
- pricing boundaries
- positioning gaps
- customer frustrations
Research Inputs
You may receive:
- Product names
- Company names
- Websites
- Feature lists
- Pricing pages
- Customer reviews
- Launch announcements
- Sales notes
- Market reports
Combine all available information.
Step 1 — Identify Competitors
Categorize competitors as:
Direct Competitors
Solve the same problem for the same customer.
Indirect Competitors
Solve the same problem differently.
Substitute Competitors
Users could use these instead of your product.
Future Competitors
Likely entrants or adjacent players.
Step 2 — Company Profiles
For every competitor identify:
- Company size
- Target audience
- Primary use case
- Pricing strategy
- Positioning statement
- Distribution model
Step 3 — Feature Matrix
Build a matrix:
| Feature | Us | Competitor A | Competitor B | Competitor C |
Classify:
- Core features
- Differentiators
- Missing capabilities
- Commodity features
Step 4 — Positioning Analysis
Determine:
- Premium vs budget
- Enterprise vs SMB
- Self-serve vs sales-led
- Simplicity vs power
Create a positioning map.
Examples:
- Ease of Use vs Power
- Price vs Capability
- Automation vs Control
Step 5 — SWOT Analysis
For each competitor analyze:
Strengths
Weaknesses
Opportunities
Threats
Step 6 — Customer Sentiment Analysis
Analyze:
- Positive reviews
- Negative reviews
- Feature requests
- Churn reasons
Identify repeated complaints.
Repeated complaints are market opportunities.
Step 7 — Strategic Gaps
Identify:
- Underserved segments
- Missing workflows
- Poor experiences
- Pricing gaps
- Geographic gaps
Step 8 — Moat Analysis
Evaluate:
- Network effects
- Data advantages
- Brand strength
- Distribution advantages
- Ecosystem lock-in
Step 9 — Recommendation Engine
Generate:
Features to Copy
Industry expectations users now assume.
Features to Ignore
Expensive low-value features.
Areas to Differentiate
High leverage opportunities.
Areas to Avoid
Crowded battlegrounds.
Output Format
Executive Summary
Market Overview
Competitor Profiles
Feature Matrix
Positioning Map
SWOT Analysis
Customer Sentiment
Strategic Opportunities
Recommended Positioning
Recommended Roadmap
Strategic Rules
- Do not copy blindly.
- Do not compete everywhere.
- Win somewhere specific first.
- Focus on unique advantages.
If you try to beat every competitor at everything, you lose.
Find the battle you can actually win.
Templates
The 9-step research process above applies universally, but which sections carry the most strategic weight depends on market context. Pick the closest match in templates/:
templates/saas-analysis.md— B2B SaaS competitive analysis, weighted toward feature matrix and pricing positioningtemplates/startup-analysis.md— early-stage/pre-PMF analysis, weighted toward underserved segments and where NOT to compete yettemplates/enterprise-analysis.md— enterprise-market analysis, weighted toward moat, distribution, and procurement/compliance positioningtemplates/ai-product-analysis.md— AI-product analysis, weighted toward model-quality differentiation, data moat, and the pace of feature commoditization
Examples
Worked, end-to-end analyses live in examples/:
examples/ai-coding-assistant.mdexamples/crm-market.mdexamples/productivity-tools.md
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.