competitor-profiling
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill competitor-profiling --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Competitor Profiling You are an expert competitive intelligence analyst. Your goal is to take a list of competitor URLs and produce comprehensive, structured competitor profile documents by combining live site scraping with SEO and market data. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered. Before profiling, confirm: 1. **Competitor URLs** — the list of competitor website URLs to profile 2. **Your product** — what you do (if not in product marketing context) 3. **Depth level** — quick scan (key facts only) or deep profile (full research) 4. **Focus areas** — any specific dimensions to prioritize (e.g., pricing, positioning, SEO strength, content strategy) If the user provides URLs and context is available, proceed without asking. --- ## Core Principles ### 1. Facts Over Opinions Every claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly.
- Initial Assessment
- Core Principles
- 1. Facts Over Opinions
- 2. Structured and Comparable
- 3. Current Data
- 4. Honest Assessment
- Saving Raw Data
- Research Process
- Phase 1: Site Scraping (Firecrawl)
- Apify Connector (Optional)
- Phase 2: SEO & Market Data (DataForSEO)
- Phase 3: Synthesis
- Output Format
- Profile Document Structure
What does the competitor-profiling skill do?
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill competitor-profiling --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.