From superpowers
Analyzes competitors via web research for verified business metrics, actionable leverage strategies, and predicted next moves. Useful for competitive intelligence, analysis, market positioning, or strategic opportunities.
npx claudepluginhub lunartech-x/superpowers --plugin superpowersThis skill uses the workspace's default tool permissions.
Provide data-backed competitive intelligence by researching real signals across the web—no assumptions, no made-up numbers.
Analyzes competitors via web research for verified business metrics, actionable leverage strategies, and predicted next moves. Useful for competitive intelligence, analysis, market positioning, or strategic opportunities.
Gathers live web data via Bright Data CLI to analyze competitors' pricing, features, reviews, hiring patterns, content strategy, and market positioning for intelligence reports.
Gathers competitive intelligence from websites, social media, ads, news, reviews, job postings, and product updates; analyzes positioning, identifies patterns, and generates strategic recommendations.
Share bugs, ideas, or general feedback.
Provide data-backed competitive intelligence by researching real signals across the web—no assumptions, no made-up numbers.
Check $ARGUMENTS first to determine execution mode:
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.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
Check if FOUNDER_CONTEXT.md exists in the project root.
From the user's requirements, extract:
This skill REQUIRES web search. Do not proceed without searching.
Execute web searches across these sources:
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 fundingSearch 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)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 developerSearch for ad strategy and spend signals:
https://www.facebook.com/ads/library/ for [Competitor]"[Competitor]" ads site:facebook.com/ads/library"[Competitor]" advertising spend OR ad budget"[Competitor]" marketing campaignSearch 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 suedSearch 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)From research, extract ONLY verified numbers with sources:
CRITICAL RULE: If a metric cannot be found with a source, mark it as "Not publicly available" — DO NOT estimate or assume.
Analyze collected data to find 3 actionable weak spots:
Look for patterns in:
For each weakness, formulate an actionable strategy your company can execute.
Based on all signals, predict what the competitor will likely do next:
Signals to interpret:
Structure findings according to Output Format section.
Hard constraints. No interpretation.
# 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]
- [Signal 2 with source]
**Implication for you:** [How to prepare/respond]
### Prediction 2: [What they'll likely do]
**Confidence:** High/Medium/Low
**Supporting signals:**
- [Signal 1 with source]
- [Signal 2 with source]
**Implication for you:** [How to prepare/respond]
---
## 4. Information Gaps
Metrics and data that could not be verified:
- [Item 1]
- [Item 2]
**Suggested next steps to fill gaps:**
- [How to find this information]
Before finalizing, verify ALL of the following:
If ANY check fails → revise before presenting.
Use these unless overridden:
Document any assumptions made in the output.