/competitor-intel

name: competitor-intel
description: Run end-to-end competitor research and monitoring through the Hyper MCP — pick the set, scrape every public surface (site, blog, pricing, organic social, search rank, mentions, demand) via Firecrawl + HyperSEO + the Apify scrapers, diff against last run, and synthesize a brief. Use when the user wants to research competitors, build a battle card or comparison page, run a weekly digest, or asks "what's [competitor] doing?" or "how do we compare?".
metadata:
  version: 1.0.0
requires_toolkits:
  - firecrawl_toolkit
  - meta_ads_library
icon: firecrawl
short_description: Scrape and monitor competitors across web, SEO, and social, then synthesize battle cards.

Competitor Intel

End-to-end competitor research and monitoring. Define the set, pull from every public surface that matters, diff against last run (or your own), and produce a brief that's actually useful — battle card, weekly digest, board update, or comparison-page input.

Out of scope — defer to other skills

| Request | Send them to | | --- | --- | | Competitor *paid ads* (Facebook / Instagram active ads) | [`meta-ads-library`](../meta-ads-library) | | Pure SEO / keyword research with HyperSEO as the primary surface | [`seo-research`](../seo-research) — uses the same HyperSEO toolkit but goes much deeper on keyword work | | Generating *creative* (images / copy) for a comparison campaign once the intel is in | [`ad-creative-generation`](../ad-creative-generation) | | Pulling data from competitor *email programs* | Not feasible — opt-in only. Use `firecrawl_urls_scrape` on their landing pages instead. |

`competitor-intel` is the *integration layer* — it pulls from every source and synthesizes. It uses HyperSEO for the rank/backlink/intersection slice but isn't the SEO research skill itself.

Requirements

• **Hyper MCP installed and connected.** [https://app.hyperfx.ai/mcp](https://app.hyperfx.ai/mcp)
• **At least one of these toolkits** connected at [https://app.hyperfx.ai/apps](https://app.hyperfx.ai/apps):
• **Firecrawl** *(highly recommended — backbone for any site/blog/pricing-page work)*
• **HyperSEO** *(needed for rank, backlink, domain-overlap analysis)*
• **Apify scrapers** — Instagram, TikTok, LinkedIn, Twitter, Reddit, Google search, Google Trends
• **Image generation** *(optional — only if the brief feeds a comparison-page or battle-card asset downstream)*

If none of those tool prefixes appear in the agent's tool list (`firecrawl_*`, `hyperseo_*`, `instagram_scrape*`, `scrape_tiktok*`, `x_tweets_search`, `reddit_scrape*`, `google_search_results_search`, `google_trends_scrape`, `web_pages_scrape`), stop and tell the user to enable the Hyper MCP and connect at least Firecrawl + one social scraper. The LinkedIn scraper (`scrape_linkedin_profiles`) is only present when that specific integration is enabled — gracefully skip the LinkedIn slice if it's missing rather than failing the whole brief.

How to run the tools in this skill

Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:

| Surface | Find a tool | Run it | | --- | --- | --- | | MCP client (Claude, Cursor, Codex, ChatGPT) | `search("<what you want to do>")`, then `describe("<name>")` | `call("<name>", {...})` | | Hyper CLI | `hyperai search "<what you want to do>"`, then `hyperai describe <name>` | `hyperai call <name> --json '{...}'` |

If a tool is not found, its integration is not connected or not enabled for the workspace: stop and tell the user which integration to connect.

Tool surface

| Phase | Tools | | --- | --- | | Site & web content | `firecrawl_urls_scrape`, `firecrawl_urls_scrape_batch`, `firecrawl_websites_crawl`, `firecrawl_screenshots_create`, `firecrawl_branding_extract`, `web_pages_scrape` (JS-rendering fallback, supports `ai_query` for targeted extraction), `web_pages_fetch`, `web_pages_load` | | Search rankings & backlinks | `hyperseo_competitors_search`, `hyperseo_competitor_domains_search`, `hyperseo_domain_overview_get`, `hyperseo_domain_keywords_get`, `hyperseo_domain_intersections_search`, `hyperseo_site_keywords_search`, `hyperseo_backlinks_history_get`, `hyperseo_rank_history_get`, `hyperseo_mentions_track` | | Brand mentions in AI search & SERPs | `hyperseo_ai_overviews_get`, `hyperseo_ai_search_volume_get`, `hyperseo_mentions_track`, `google_search_results_search`, `web_search` | | Organic social — Instagram | `instagram_scrape`, `instagram_posts_scrape`, `instagram_followers_count_scrape` | | Organic social — TikTok | `tiktok_videos_scrape`, `tiktok_comments_scrape` | | Organic social — LinkedIn | `scrape_linkedin_profiles` *(conditional — only available when the LinkedIn-scraper integration is enabled in your Hyper workspace)* | | Organic social — Twitter / X | `x_tweets_search` | | Community / sentiment — Reddit | `reddit_scrape`, `reddit_leads_scrape` | | Ecommerce competitor specifics | `ecommerce_products_scrape`, `ecommerce_reviews_scrape` | | Demand / trend signals | `google_trends_scrape`, `hyperseo_search_volume_get`, `hyperseo_intents_search` | | Optional: comparison-page assets | `images_generate` |

Critical rules

1. **Public-only data.** Never scrape behind login walls or paywalls. If a target is gated, stop and surface that — don't try to bypass. 2. **Pick the competitor set before scraping.** 3–5 competitors is the sweet spot. 10+ produces an unreadable brief and burns scraper credits. If the user doesn't have a list, run `hyperseo_competitors_search(domain=<their_domain>)` first to surface the top organic competitors, then confirm the set with them. 3. **Snapshot, then diff.** First run is just a baseline — there's nothing to compare against. The value compounds on the second and third runs (what changed in pricing, what new posts went up, who lost rank). Make this expectation clear when the user runs it for the first time. 4. **HyperSEO is credit-metered.** Be intentional. Don't loop `hypers