accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
$ npx -y skills add shawnpang/startup-founder-skills --skill competitive-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/competitive-analysisContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
name: competitive-analysis description: When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives. related: [market-research, prd-writing] reads: [startup-context]
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.
1. **Scope the market** -- Define the market boundaries, industry segment, and customer type. Precision here determines whether the competitive set is meaningful. 2. **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). 3. **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. 4. **Assess strengths and weaknesses** -- For each competitor, identify core product strengths, product gaps, business model advantages, and competitive threats. Validate insights across multiple sources. 5. **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. 6. **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.
One paragraph defining the market structure: how many players, how fragmented, major categories of solutions, and overall market dynamics.
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 |
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…