competitor-analyst
Use this skill when analyzing competitors, building competitive positioning, creating feature comparison matrices, or applying strategic frameworks like SWOT or Porter's Five Forces. Trigger phrases: 'analyze our competitors', 'competitive analysis for', 'how do we compare to', 'create a feature matrix', 'SWOT analysis of'. Not for sizing the total market (use market-researcher), writing pitch decks (use pitch-deck-writer), or pricing strategy modeling.
What this skill does
# Competitor Analyst ## Overview This skill provides structured frameworks for competitive intelligence—from gathering information on competitors through applying analytical frameworks (SWOT, Porter's Five Forces, positioning maps, feature matrices) to synthesizing insights into strategic recommendations. Good competitive analysis reveals where to attack, where to defend, and how to position your product to win. ## When to Use - Building a competitive landscape analysis for investors, board, or internal strategy - Creating a feature comparison matrix for sales or product teams - Developing a competitive positioning strategy - Tracking and monitoring competitor moves over time - Preparing a competitive battle card for sales - Identifying whitespace opportunities in the market ## When NOT to Use - Sizing total market opportunity (use market-researcher skill) - Writing a full pitch deck (use pitch-deck-writer skill) - Conducting primary research interviews with competitor customers (use ux-researcher skill) - Financial modeling or pricing analysis (use a finance skill) ## Quick Reference | Framework | Use Case | Output | |-----------|----------|--------| | SWOT Analysis | Internal + external audit per competitor | 2×2 matrix | | Porter's Five Forces | Industry-level threat assessment | Force ratings + strategy | | Feature Matrix | Product comparison for sales/product | Comparison table | | Positioning Map | Visual differentiation | 2×2 or 2-axis plot | | Battle Card | Sales competitive enablement | 1-page quick reference | | Win/Loss Analysis | Understanding why deals are won or lost | Pattern report | | Competitive monitoring | Ongoing intel tracking | Change log | ## Instructions ### Step 1: Define the Scope Before researching, clarify: 1. **Who are the direct competitors?** (Same product category, same customer) 2. **Who are the indirect competitors?** (Different product, same job-to-be-done) 3. **Who are the potential entrants?** (Not yet competing but could) 4. **What decisions will this analysis inform?** (Positioning, product roadmap, pricing, sales training) **Competitor tiers:** | Tier | Description | Example | |------|-------------|---------| | Tier 1 (Primary) | Direct, head-to-head competition for same buyer | Feature-for-feature match | | Tier 2 (Secondary) | Adjacent solutions solving same problem differently | Different approach/category | | Tier 3 (Indirect) | Status quo / manual alternatives | Spreadsheets, custom-built tools | ### Step 2: Information Gathering Never rely on competitor websites alone—they only show strengths. **Primary sources (no login required):** - Competitor website: positioning, messaging, pricing page, case studies - Job postings: hiring signals reveal engineering investment, new products, geographic expansion - Blog and content: what problems they're addressing, thought leadership positioning - Press releases and news: funding, partnerships, product launches, executive changes - SEC filings (public companies): actual revenue, customer counts, churn rates **Review sites (customer voice — most valuable):** - G2, Capterra, Trustpilot, App Store, Google Play - Reddit (r/[industry], r/[product category]) - LinkedIn recommendations and testimonials - Twitter/X: search "[competitor name] sucks" or "[competitor name] alternatives" **Social signals:** - LinkedIn company page: growth rate, recent posts, employee count trend - LinkedIn job postings: volume and department signal investment areas - GitHub (if relevant): open source activity, developer engagement **Paid research (optional):** - SimilarWeb: web traffic estimates and traffic sources - Crunchbase/PitchBook: funding, investors, valuation signals - Gartner Peer Insights, Forrester Wave: analyst positioning **Information to collect per competitor:** ``` Company overview: Founded, HQ, employees, funding, estimated revenue Target customer: Segment, ICP, use case Product: Core features, differentiators, recent launches Pricing: Model (per seat, usage, flat), tiers, pricing page public? Go-to-market: Sales motion (PLG, inside sales, enterprise sales), channels Positioning: Tagline, key messages, what they claim to do best Weaknesses: Negative reviews, common complaints, gaps Recent moves: Last 3 major announcements or product launches ``` ### Step 3: SWOT Analysis Conduct a SWOT for each major competitor and for your own company. **Template:** ``` Competitor: [Name] Date: [Quarter/Year] STRENGTHS (internal, positive) - What do they do better than anyone? - Why do customers choose them? - What resources/assets give them an advantage? WEAKNESSES (internal, negative) - Where do customers complain the most? (G2, Capterra) - What features are they missing? - What business model or technical constraints limit them? OPPORTUNITIES (external, positive) - What market trends benefit them? - What adjacent markets could they expand into? - What partnerships could amplify them? THREATS (external, negative) - What could disrupt their current advantage? - New entrants, regulatory changes, technology shifts? - How could you attack them? ``` ### Step 4: Porter's Five Forces Apply at the industry level to understand structural attractiveness and competitive intensity. **Force 1: Threat of New Entrants** (How easy is it to enter this market?) - High threat: Low barriers to entry, no switching costs, open source alternatives - Low threat: High R&D cost, regulatory approval needed, strong network effects, data moats **Force 2: Bargaining Power of Buyers** (How much leverage do customers have?) - High power: Many alternatives, low switching cost, price-sensitive buyers - Low power: Switching costs high, product deeply embedded, few alternatives **Force 3: Bargaining Power of Suppliers** (How dependent are you on key vendors?) - High power: Few cloud providers, API dependency (OpenAI, Stripe), regulatory monopolies - Low power: Multiple alternatives, open standards, commoditized inputs **Force 4: Threat of Substitutes** (Can buyers solve the problem a completely different way?) - High threat: Problem can be solved with Excel, custom code, manual process - Low threat: No reasonable substitute; unique technology **Force 5: Rivalry Among Existing Competitors** (How intense is competition?) - High rivalry: Commoditized product, price wars, slow market growth - Low rivalry: Differentiated, fast-growing market, not yet zero-sum **Strategic implications by force rating:** ``` If buyers have high power → compete on switching costs, contracts, integrations If new entrants threat is high → build moats (network effects, data, brand, distribution) If rivalry is intense → differentiate aggressively; avoid head-to-head on price ``` ### Step 5: Feature Comparison Matrix Used by product teams to spot gaps and by sales teams to win deals. **Matrix template:** | Feature | Your Product | Competitor A | Competitor B | Competitor C | |---------|-------------|-------------|-------------|-------------| | **Core features** | | | | | | Feature 1 | ✅ Full | ✅ Full | ⚠️ Partial | ❌ No | | Feature 2 | ✅ Full | ❌ No | ✅ Full | ✅ Full | | **Differentiating features** | | | | | | Your key differentiator | ✅ | ❌ | ❌ | ❌ | | **Integrations** | | | | | | Salesforce | ✅ | ✅ | ❌ | ✅ | | Slack | ✅ | ⚠️ Beta | ✅ | ❌ | | **Commercial** | | | | | | Pricing (per seat/mo) | $15 | $20 | $12 | $18 | | Free plan | ✅ | ❌ | ✅ | ❌ | | Enterprise tier | ✅ | ✅ | ❌ | ✅ | | SOC 2 Type II | ✅ | ✅ | ❌ | ✅ | Legend: ✅ Full support | ⚠️ Partial/Beta | ❌ Not available ### Step 6: Positioning Map A 2-axis map reveals whitespace and where you're differentiated. **Process:** 1. Choose two dimensions that matter most to buyers (not two where you win automatically) 2. Common axis pairs: - Price (budget → premium) × Ease of use (complex → simple) - Target user (SMB → Enterprise) × Feature breadth (focused → all-in-one) - Deployment (cloud → on-prem) × Customization (out-of-box → highly custom) 3. Plot each compet
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.