competitive-analysis
Skill8 starsChanged 8 months agoMITView on GitHub
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGrouptheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use usability-test-plan, user-research and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
launchapp-devSkillusability-test-plan
Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.
Also in 3 projects that use this
AnthropicSkilluser-research
Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.
Also in 3 projects that use this
walternateSkillgo-to-market
Build a go-to-market (GTM) strategy for launching a product or entering a new market. Use when planning how to reach customers, position your product, choose channels, set pricing, and execute launch. Covers market entry strategy, customer segmentation, positioning, channel strategy, and GTM execution plan. Trigger on "go-to-market", "GTM strategy", "market entry", "launch strategy", "how to reach customers", "GTM plan".
Also in 3 projects that use this
narlyseorgSkillsecure-code-review
Use when reviewing source code for security vulnerabilities, performing static analysis of a codebase, auditing code for injection flaws, authentication issues, cryptographic weaknesses, insecure deserialization, SSRF, path traversal, memory safety bugs, hardcoded secrets, or misconfigurations. Use when the user asks to find security bugs in code, assess code quality from a security perspective, or review pull requests for security implications. Use when performing dependency audits, secrets scanning, or configuration review of application source.
Also in 3 projects that use this
AutumnsGroveSkillapi-designer
Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation
Also in 4 projects that use this
huntsyeaSkilljobs-to-be-done
Applies Bob Moesta's demand-side thinking and Jobs-to-be-Done framework to help product teams understand why customers switch, hire, and fire products. Use when conducting switch interviews, drawing forces diagrams, writing job statements, mapping demand timelines, understanding the struggling moment, analyzing why customers hire or fire your product, exploring passive or active looking behavior, researching JTBD, or when user mentions Bob Moesta, demand-side thinking, big hire, little hire, push/pull/anxiety/habit, or the four forces of progress.
Also in 3 projects that use this
Other versions54 projects use a version of this.
Word for word · 1
- shawnpang/startup-founder-skills★ 331100% same
Edited · 0
None found.
Wrote their own version · 53
- anthropics/financial-services★ 41ksame name
- anthropics/financial-services-plugins★ 41ksame name
- claude-office-skills/skills★ 433same name
- mverab/eGEOagents★ 218same name
- Fokkyp/claude-skills★ 211same name
- aakashg/pm-claude-code-setup★ 152same name
- nahid-sparktales/agent-dispatcher★ 59same name
- agencia-conversion/agentic-seo-skills★ 51same name
- launchapp-dev/animus-cli★ 39same name
- nimadorostkar/Claude-Skills-collection★ 33same name
43 more not listed
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 repository49 other files it gives its agents.
- accelerator-applicationSkill
- architecture-designSkill
- board-updateSkill
- churn-analysisSkill
- cicd-setupSkill
- code-reviewSkill
- cold-outreachSkill
- community-discoverySkill
- competitor-monitoringSkill
- content-strategySkill
- contract-reviewSkill
- daily-product-digestSkill
- data-roomSkill
- earned-media-outreachSkill
- email-marketingSkill
- employer-brandSkill
- event-hostingSkill
- feedback-synthesisSkill
- founder-thought-leadershipSkill
- fundraising-emailSkill
- interview-kitSkill
- investor-researchSkill
- job-descriptionSkill
- landing-pageSkill
- launch-strategySkill
- lead-scoringSkill
- market-researchSkill
- mvp-scopingSkill
- onboarding-flowSkill
- partnership-outreachSkill
- pitch-deckSkill
- prd-writingSkill
- privacy-policySkill
- process-docsSkill
- proposal-generationSkill
- review-miningSkill
- roadmap-planningSkill
- sales-scriptSkill
- security-reviewSkill
- sentiment-monitoringSkill
- seo-technicalSkill
- soc2-prepSkill
- social-contentSkill
- sourcing-outreachSkill
- startup-contextSkill
- support-docsSkill
- tech-stack-evalSkill
- terms-of-serviceSkill
- user-research-synthesisSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
3
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
- Distinctive: line 55
Primary sources over secondhand: Use the competitor's own product (sign up for free trials), pricing page, job postings (reveal strategy), …
- Distinctive: line 57
Compete on a different axis: If incumbents compete on features, compete on simplicity.
- Distinctive: line 61
Refresh cadence: Update quarterly in fast-moving markets, semi-annually in slower ones.
“Common” is measured: kept by at least 6 in 10 of the 44 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
Competitive Analysis
When to Use
Activate when a founder needs to analyze the competitive landscape, evaluate specific competitors, find differentiation opportunities, or prepare a competitive brief. Trigger phrases include "who are our competitors," "analyze this competitor," "competitive landscape," "how do we compare to X," "feature comparison," "what's our moat," or "differentiation opportunities." Also activate before fundraising (investors will ask) or when entering a new market segment.
Context Required
- From startup-context: product description, target market, current positioning, key differentiators, pricing model, geographic scope.
- From the user: specific competitors to analyze (or request to identify them), market/industry segment to scope, the strategic question driving the analysis (positioning, pricing, feature gaps, market entry).
Workflow
- Scope the market -- Define the market boundaries, industry segment, and customer type. Precision here determines whether the competitive set is meaningful.
- Identify 5 primary competitors -- Find direct competitors (same problem, same customer), adjacent competitors (different approach to same problem), and emerging entrants. Distinguish between direct competitors and alternatives (including "do nothing" or manual workarounds).
- Gather competitive intelligence -- Research each competitor across: product capabilities, pricing/business model, positioning and messaging, distribution channels, team/funding, and traction signals. Use competitor websites, pricing pages, customer reviews (G2, Capterra), job postings, and product trials as primary sources.
- Assess strengths and weaknesses -- For each competitor, identify core product strengths, product gaps, business model advantages, and competitive threats. Validate insights across multiple sources.
- Map differentiation opportunities -- Identify unmet customer pain points no competitor addresses well, underserved segments, and areas where you can credibly win. Focus on where the market is heading, not just where it is.
- Synthesize strategic positioning -- Formulate a competitive positioning recommendation with suggested positioning, key differentiators, target segments to prioritize, competitors to monitor, and 12-18 month competitive risks.
Output Format
Market Overview
One paragraph defining the market structure: how many players, how fragmented, major categories of solutions, and overall market dynamics.
Competitor Profiles (x5)
For each competitor:
| Dimension | Details |
| Company Profile | Background, founding, funding, team size, headquarters |
| Core Product Strengths | Key capabilities, UX quality, integrations, technical advantages |
| Product Gaps | Missing features, weak areas, customer complaints |
| Business Model & Pricing | Model type, price points, free tier, enterprise options |
| Competitive Threats | What makes them dangerous -- momentum, funding, distribution, brand |
Differentiation Opportunities
- Unmet customer pain points no competitor addresses well
- Underserved market segments or personas
- Emerging needs created by market shifts or technology changes
- Positioning angles that create clear separation from the field
Competitive Positioning Recommendation
- Suggested market positioning and category framing
- Key differentiators to emphasize (backed by evidence)
- Target segments where competitive dynamics favor your approach
- Monitoring priorities (which competitors to watch and why)
- 12-18 month competitive risks and mitigation strategies
Frameworks & Best Practices
- Primary sources over secondhand. Use the competitor's own product (sign up for free trials), pricing page, job postings (reveal strategy), and customer reviews over analyst reports. Job postings are strategy signals -- hiring ML engineers means AI investment, enterprise sales reps means upmarket movement.
- Status quo is your biggest competitor. For most startups, the real competitor is "do nothing" or "use a spreadsheet." Analyze this alternative with the same rigor as named competitors.
- Compete on a different axis. If incumbents compete on features, compete on simplicity. If they compete on price, compete on experience. Winning means changing the evaluation criteria, not beating incumbents at their own game.
- Track momentum, not just position. A well-funded competitor with flat growth is weaker than an unfunded one growing 20% month-over-month. Monitor hiring velocity, product release cadence, and review sentiment trends.
- Distinguish direct from adjacent. Direct competitors solve the same problem for the same customer. Adjacent competitors solve the same problem differently or solve a related problem. Both matter but require different strategic responses.
- Feature comparison honesty. Mark your own product's gaps accurately. An internal competitive analysis that overstates your strengths is useless. The purpose is truth, not comfort.
- Refresh cadence. Update quarterly in fast-moving markets, semi-annually in slower ones. Track funding rounds, executive moves, and product launches as trigger events for ad-hoc updates.
- Identify subtle differentiation. The most durable competitive advantages are often not feature-based -- they are distribution advantages, data moats, ecosystem effects, or brand trust built over time.
Related Skills
market-research-- Pair competitive analysis with market sizing to understand both the landscape and the size of the prize.prd-writing-- Use competitive gaps to inform the solution section of a PRD. Build what competitors miss.user-research-synthesis-- Ground feature comparisons in what customers actually value, not what competitors assume they value.
Examples
Example 1: Competitive landscape for fundraising
User: "I need a competitive landscape slide for our Series A deck."
Good output: A market overview paragraph, profiles of 4-5 key competitors highlighting their weaknesses relative to the startup's strengths, a differentiation map showing clear whitespace where the startup sits, and a positioning recommendation that tells a narrative about why competitive dynamics favor the startup's approach.
Example 2: Direct competitor deep-dive
User: "We keep losing deals to Competitor X. Help us understand why and how to win."
Good output: Deep analysis of Competitor X's strengths in the dimensions that matter to buyers (e.g., enterprise readiness, integrations, brand trust), identification of the specific evaluation criteria where they win, and actionable recommendations to either match their advantages on must-have dimensions or shift the evaluation criteria to dimensions where you are stronger.
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.

