competitor-intel
Analyzes competitors using web research to provide verified business metrics, actionable leverage strategies, and predicted next moves. Use when user needs competitive intelligence, competitor analysis, market positioning insights, or strategic leverage opportunities.
What this skill does
# Competitor Intel ## Purpose Provide data-backed competitive intelligence by researching real signals across the web—no assumptions, no made-up numbers. --- ## Execution Logic **Check $ARGUMENTS first to determine execution mode:** ### If $ARGUMENTS is empty or not provided: Respond with: "competitor-intel loaded, proceed with competitor name and any context (website, industry, etc.)" Then wait for the user to provide their requirements in the next message. ### If $ARGUMENTS contains content: Proceed immediately to Task Execution (skip the "loaded" message). --- ## Task Execution When user requirements are available (either from initial $ARGUMENTS or follow-up message): ### 1. Check for Business Context (Optional) Check if `FOUNDER_CONTEXT.md` exists in the project root. - **If it exists:** Read it to understand your company's positioning, strengths, and goals—this informs the leverage strategies. - **If it doesn't exist:** Proceed with analysis focused purely on competitor weaknesses. ### 2. Extract Input From the user's requirements, extract: - Competitor name (required) - Competitor website (if provided) - Industry/vertical (if provided) - Specific areas of interest (if provided) ### 3. Research Phase — MANDATORY WEB SEARCH **This skill REQUIRES web search. Do not proceed without searching.** Execute web searches across these sources: #### Business Metrics Research Search for verified data only. Query patterns: - `"[Competitor]" revenue OR MRR OR ARR site:crunchbase.com` - `"[Competitor]" funding raised valuation site:crunchbase.com` - `"[Competitor]" employees headcount site:linkedin.com` - `"[Competitor]" revenue growth OR metrics` - `"[Competitor]" pricing customers` - `"[Competitor]" CEO OR founder interview revenue` - `"[Competitor]" Series A OR Series B OR funding` #### Traffic & SEO Research Search for web traffic and search presence signals: - `"[Competitor]" site:similarweb.com` (traffic estimates, top pages, traffic sources) - `"[Competitor]" site:ahrefs.com` (backlinks, domain rating, organic keywords) - `"[Competitor]" site:semrush.com` (traffic, keyword rankings, ad spend) - `"[Competitor]" site:trends.google.com` (search interest over time) - `[Competitor website domain] site:builtwith.com` (tech stack, tools used) #### Technical & Product Research Search for product and development signals: - `"[Competitor]" site:github.com` (open source activity, tech stack, hiring signals) - `[Competitor GitHub org]` (commit frequency, contributors, project activity) - `"[Competitor]" API OR integration OR developer` #### Advertising Research Search for ad strategy and spend signals: - Search Meta Ads Library: `https://www.facebook.com/ads/library/` for [Competitor] - `"[Competitor]" ads site:facebook.com/ads/library` - `"[Competitor]" advertising spend OR ad budget` - `"[Competitor]" marketing campaign` #### Weakness & Sentiment Research Search for complaints, issues, and struggles: - `"[Competitor]" reviews site:g2.com` - `"[Competitor]" reviews site:capterra.com` - `"[Competitor]" reviews site:trustpilot.com` - `"[Competitor]" complaints OR issues OR problems` - `"[Competitor]" "doesn't work" OR "broken" OR "terrible"` - `"[Competitor]" layoffs OR firing OR cuts` - `"[Competitor]" lawsuit OR sued` #### Signal Research (for predictions) Search for hiring, product, and strategic signals: - `"[Competitor]" hiring site:linkedin.com` - `"[Competitor]" job openings` - `"[Competitor]" new feature OR launch OR release` - `"[Competitor]" roadmap OR upcoming` - `"[Competitor]" partnership OR integration` - `"[Competitor]" site:twitter.com OR site:x.com` (founder/company posts) ### 4. Compile Verified Metrics From research, extract ONLY verified numbers with sources: - MRR/ARR (if disclosed) - Funding raised (total and rounds) - Valuation (if known) - Employee count - Customer count - Churn rate (if disclosed) - Growth rate (if disclosed) - Pricing tiers **CRITICAL RULE:** If a metric cannot be found with a source, mark it as "Not publicly available" — DO NOT estimate or assume. ### 5. Identify Leverage Opportunities Analyze collected data to find 3 actionable weak spots: Look for patterns in: - **Product gaps**: Features users complain about, missing integrations - **Service failures**: Support complaints, response times, bugs - **Pricing friction**: Users complaining about cost, hidden fees, poor value - **Trust issues**: Security concerns, data breaches, broken promises - **Operational struggles**: Layoffs, leadership changes, funding difficulties - **Marketing weaknesses**: Poor ad execution, weak positioning, low engagement For each weakness, formulate an actionable strategy your company can execute. ### 6. Predict Next Moves Based on all signals, predict what the competitor will likely do next: Signals to interpret: - **Hiring patterns**: Engineering = product push, Sales = growth mode, Support = scaling issues - **Job postings**: Reveal technology bets, market expansion, new products - **Funding status**: Recent raise = aggressive expansion, No raise in 2+ years = potential trouble - **Content/PR**: Topics they're pushing indicate strategic focus - **Partnership announcements**: Reveal market positioning and gaps - **Founder activity**: Where they speak, what they post, who they meet ### 7. Format Output Structure findings according to **Output Format** section. --- ## Writing Rules Hard constraints. No interpretation. ### Core Rules - Every metric MUST include a source link or be marked "Not publicly available" - No estimations, assumptions, or "likely" numbers for metrics - Strategies must be actionable (specific steps, not vague advice) - Predictions must cite the signals that support them - Use neutral, analytical tone—not competitive trash talk - Date all findings (data freshness matters) ### Source Rules - Prioritize primary sources (company announcements, founder interviews, SEC filings) - Crunchbase, LinkedIn, G2, Capterra are acceptable secondary sources - News articles are acceptable if they cite primary sources - Avoid unverified Twitter/X claims unless from official company accounts ### Strategy Rules - Each strategy must exploit a verified weakness - Each strategy must include concrete next steps - Strategies should be achievable within 30-90 days - Avoid strategies that require significant capital unless user has it --- ## Output Format ```markdown # Competitor Intel: [Competitor Name] **Generated:** [Date] **Sources searched:** [Count] sources across Crunchbase, LinkedIn, G2, Capterra, news, social --- ## 1. Verified Business Metrics | Metric | Value | Source | Date | |--------|-------|--------|------| | Funding Raised | $X | [Source](url) | [Date] | | Valuation | $X | [Source](url) | [Date] | | Employee Count | X | [Source](url) | [Date] | | MRR/ARR | Not publicly available | — | — | | Customer Count | ~X | [Source](url) | [Date] | | Churn Rate | Not publicly available | — | — | **Key Observations:** - [Insight about their financial health] - [Insight about their growth trajectory] --- ## 2. Leverage Strategies ### Strategy 1: [Name] **Weakness exploited:** [What you found] **Evidence:** [Quote or data point with source] **Action steps:** 1. [Specific action] 2. [Specific action] 3. [Specific action] **Expected outcome:** [What this achieves] --- ### Strategy 2: [Name] **Weakness exploited:** [What you found] **Evidence:** [Quote or data point with source] **Action steps:** 1. [Specific action] 2. [Specific action] 3. [Specific action] **Expected outcome:** [What this achieves] --- ### Strategy 3: [Name] **Weakness exploited:** [What you found] **Evidence:** [Quote or data point with source] **Action steps:** 1. [Specific action] 2. [Specific action] 3. [Specific action] **Expected outcome:** [What this achieves] --- ## 3. Predicted Next Moves ### Prediction 1: [What they'll likely do] **Confidence:** High/Medium/Low **Supporting signals:** - [Signal 1 with source] - [Signa
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.