competitor-profiling · diff
v1.1.0 to v1.2.0
106 added, 394 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: competitor-profiling
- description: "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 competitor-alternatives. For sales-specific battle cards, see sales-enablement."
+ description: "Use when the user wants competitor research, a named competitor profile or dossier, competitive landscape discovery, an alternative-universe comparison, or competitive signals/change investigation. Accept URLs, supplied research, and targeted verification requests. For external market/category conditions, see market-intelligence; for comparison pages, see competitor-alternatives; for battlecards, see sales-enablement; for closed-deal causes, see win-loss-intelligence."
metadata:
- version: 1.1.0
+ version: 1.2.0
---
# Competitor Profiling
- **Use the company SSOT when present:** follow `../_shared/ssot-consumption.md` and the project manifest to load relevant approved client context. Keep competitor observations separate from the company’s canonical positioning and cite sources for comparisons.
-
- 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
-
- **Load the evidence labels:** read `../_shared/evidence-gaps.md` (relative to this skill's folder) and follow it. Label every claim, benchmark, and number Sourced, Assumed, or Gap. Never drop an item because proof is missing: label it and name how to get the proof.
-
- **Check for product marketing context first:**
- If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered.
-
- Before profiling, confirm:
+ Establish sourced facts about alternatives, structure a comparable landscape,
+ and verify changes against dated baselines. Separate facts, reported claims,
+ interpretations, and implications. Research does not approve strategy.
- 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)
+ ## Before starting
- If the user provides URLs and context is available, proceed without asking.
+ - Resolve the active project/product scope. Keep other projects' evidence and
+ approval references out of this return; IDs are project-scoped.
+ - Read `../_shared/evidence-gaps.md` and `../_shared/ssot-consumption.md`.
+ - Read `../_shared/context-establishment.md` when available. It owns Phase 1
+ evidence, readiness, and handoff/return semantics. Otherwise use the compatible
+ minimum in [references/templates.md](references/templates.md).
+ Read that reference for domain checks and the return template on every run.
+ - Load relevant manifest-mapped approved context. Record version, authority,
+ health, and gaps. Bootstrap context stays provisional.
+ - Preserve originating HND/GAP/SRC/FND IDs, exact question, completion criteria,
+ scope, constraints, opposing evidence, and return destination.
+ - Inventory profiles, raw captures, supplied dossiers, customer findings, and
+ dated snapshots before collecting more. Mark inspection coverage and unavailable material.
+ - Resolve job/problem or named entity, geography, period, intended use, and depth.
+ Ask only for missing facts that materially change the work.
+ Exploration requires useful scope, not approved personas or an accepted market.
- ---
+ ## Choose the smallest useful mode
- ## Core Principles
+ Read the selected section of [references/modes.md](references/modes.md).
+ Use only modes needed for the question.
- ### 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.
+ | Mode | Exact job and triggers | Output |
+ |---|---|---|
+ | Competitive landscape | Identify and structure the relevant alternative universe. “Who competes for this job?” “Map our alternatives.” | Inclusion rationale, alternative register, supported comparison, coverage/freshness view. |
+ | Entity profiling | Establish sourced facts about a named alternative. “Profile this competitor.” “Verify whether this feature exists.” | Focused or full dossier with field-level provenance and verification. |
+ | Competitive signals | Identify and verify changes against a dated baseline. “What changed since our last profile?” “Investigate this launch.” | Event/delta register with verification, materiality, and affected references. |
- ### 2. Structured and Comparable
- All profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile.
+ Landscape discovery may commission focused profiles before comparison.
+ Signals refresh affected fields and comparisons without repeating full studies.
+ Named-entity requests need not start with landscape discovery.
- ### 3. Current Data
- Profiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., "pricing page last updated 2023").
+ ## Research and evidence
- ### 4. Honest Assessment
- Don't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles.
+ Use existing evidence and the smallest useful verification. URLs are optional.
+ Methods include supplied-material analysis, documentation, published commercial
+ terms, release notes, original filings, permitted demos/trials, and customer findings.
+ Scraping and SEO are optional methods, not prerequisites. Read
+ [references/tool-reference.md](references/tool-reference.md) only when those tools
+ fit the question. Missing tools never justify invented data.
- ---
+ Keep these distinctions explicit:
+ - Competitor-authored claim versus documented behavior versus direct verification.
+ - Customer-reported experience versus general product fact.
+ - Unknown capability versus scoped evidence of absence in a tier/version.
+ - Announcement versus available, beta, limited access, or withdrawn capability.
+ - Observed change versus inference about intent, demand, or commercial impact.
+ - Search overlap versus evidence of commercial competition.
- ## Saving Raw Data
+ Record lineage and counterevidence. Copies of one announcement are one signal.
+ Ratings, traffic, and review counts do not verify revenue or customer totals.
+ Never infer absence from an omitted feature or inaccessible page. Compare equivalent
+ versions, tiers, currencies, billing periods, and regions. No universal source-count
+ threshold establishes confidence or readiness.
- Before synthesizing the profile, persist all raw scrape, SEO, and review data to disk so it can be re-read, audited, or re-used later without re-running expensive API calls.
+ ## Persistence and refresh
- **Directory layout** (relative to project root):
+ Preserve the existing project-relative competitor-profiles location when used:
- ```
+ ```text
competitor-profiles/
- ├── raw/
- │ └── <competitor-slug>/
- │ └── <YYYY-MM-DD>/
- │ ├── scrapes/ # one .md file per scraped page (homepage.md, pricing.md, ...)
- │ ├── seo/ # one .json file per DataForSEO call (backlinks-summary.json, ranked-keywords.json, ...)
- │ └── reviews/ # one .md or .json file per review source (g2.md, capterra.md, ...)
- ├── <competitor-slug>.md # final synthesized profile
- └── _summary.md # cross-competitor summary
- ```
-
- Rules:
-
- - `<competitor-slug>` is lowercase, hyphenated (e.g. `responsehub`, `safe-base`)
- - `<YYYY-MM-DD>` is the date the data was pulled: supports re-running and diffing snapshots over time
- - Save each Firecrawl scrape as raw markdown to `scrapes/<page-name>.md`
- - Save each DataForSEO response as raw JSON to `seo/<endpoint-name>.json`
- - Save each review source to `reviews/<source>.md` (cleaned text) or `.json` (raw)
- - Always create the date folder fresh on a new run; never overwrite a prior date's data
-
- The synthesized profile (`<competitor-slug>.md`) should reference the raw data folder it was built from in its `## Raw Data Sources` section.
-
- ---
-
- ## Research Process
-
- ### Phase 1: Site Scraping (Firecrawl)
-
- For each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging.
-
- #### Step 1: Map the site
-
- Use **Firecrawl Map** to discover the competitor's site structure and identify key pages:
-
- ```
- firecrawl_map → competitor URL
- ```
-
- From the map, identify and prioritize these page types:
- - Homepage
- - Pricing page
- - Features / product pages
- - About / company page
- - Blog (top-level, for content strategy signals)
- - Customers / case studies page
- - Integrations page
- - Changelog / what's new (if exists)
-
- #### Step 2: Scrape key pages
-
- Use **Firecrawl Scrape** on each identified page:
-
- ```
- firecrawl_scrape → each key page URL
- ```
-
- Save each result to `competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/scrapes/<page-name>.md` before extracting fields.
-
- Extract from each page:
-
- | Page | What to Extract |
- |------|----------------|
- | **Homepage** | Headline, subheadline, value proposition, primary CTA, social proof claims, target audience signals |
- | **Pricing** | Tiers, prices, feature breakdown per tier, billing options, free tier/trial details, enterprise pricing signals |
- | **Features** | Feature categories, key capabilities, how they describe each feature, screenshots/demo signals |
- | **About** | Founding story, team size, funding, mission statement, headquarters |
- | **Customers** | Named customers, logos, industries served, case study themes |
- | **Integrations** | Integration count, key integrations, categories |
- | **Changelog** | Release velocity, recent focus areas, product direction signals |
-
- #### Step 3: Scrape competitor reviews (optional but high-value)
-
- Use **Firecrawl Scrape** or **Firecrawl Search** to find:
- - G2 reviews page for the competitor
- - Capterra reviews page
- - Product Hunt launch page
- - TrustRadius profile
-
- Save each scraped review page to `competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/reviews/<source>.md`. Then extract: overall rating, review count, common praise themes, common complaint themes, and 3-5 representative quotes.
-
- ---
-
- ### Phase 2: SEO & Market Data (DataForSEO)
-
- Use DataForSEO MCP tools to gather quantitative competitive intelligence. Save each raw response as JSON to `competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/seo/<endpoint-name>.json` before parsing it into the profile. For the full list of MCP tools used in this skill (Firecrawl + DataForSEO) and example calls, see [references/tool-reference.md](references/tool-reference.md).
-
- #### Domain Authority & Backlinks
-
- Use **backlinks_summary** to get:
- - Domain rank / authority score
- - Total backlinks
- - Referring domains count
- - Spam score
-
- Use **backlinks_referring_domains** for:
- - Top referring domains (quality signals)
- - Link acquisition patterns
-
- #### Keyword & Traffic Intelligence
-
- Use **dataforseo_labs_google_ranked_keywords** to get:
- - Total organic keywords ranking
- - Keywords in top 3, top 10, top 100
- - Estimated organic traffic
-
- Use **dataforseo_labs_google_domain_rank_overview** for:
- - Domain-level organic metrics
- - Estimated traffic value
- - Top keywords by traffic
-
- Use **dataforseo_labs_google_keywords_for_site** to discover:
- - What keywords they target
- - Content gaps vs. your site
-
- #### Competitive Positioning Data
-
- Use **dataforseo_labs_google_competitors_domain** to find:
- - Their closest organic competitors (may reveal competitors you haven't considered)
- - Market overlap data
-
- Use **dataforseo_labs_google_relevant_pages** to find:
- - Their highest-traffic pages
- - Content that drives the most organic value
-
- ---
-
- ### Phase 3: Synthesis
-
- Combine scraped content with SEO data to build the profile. Cross-reference claims (e.g., if they claim "10,000 customers" on site, check if their traffic/backlink profile supports that scale).
-
- ---
-
- ## Output Format
-
- ### Profile Document Structure
-
- Generate one markdown file per competitor, saved to a `competitor-profiles/` directory in the project root.
-
- **Filename**: `competitor-profiles/[competitor-name].md`
-
- **For the full profile and summary templates**: See [references/templates.md](references/templates.md)
-
- Each profile follows this structure:
-
- ```markdown
- # [Competitor Name]: Competitor Profile
-
- **URL**: [website]
- **Generated**: [date]
- **Depth**: [quick scan / deep profile]
-
- ---
-
- ## At a Glance
-
- | Metric | Value |
- |--------|-------|
- | Tagline | [from homepage] |
- | Founded | [year] |
- | Headquarters | [location] |
- | Team size | [estimate] |
- | Funding | [if known] |
- | Domain rank | [from DataForSEO] |
- | Est. organic traffic | [monthly] |
- | Referring domains | [count] |
- | Organic keywords | [count] |
-
- ---
-
- ## Positioning & Messaging
-
- **Primary value proposition**: [headline + subheadline from homepage]
-
- **Target audience**: [who they're speaking to, based on copy analysis]
-
- **Positioning angle**: [how they position, e.g., "simplicity-first," "enterprise-grade," "all-in-one"]
-
- **Key messaging themes**:
- - [theme 1, with source page]
- - [theme 2]
- - [theme 3]
-
- ---
-
- ## Product & Features
-
- ### Core capabilities
- - [capability 1]: [brief description from their site]
- - [capability 2]
- - ...
-
- ### Notable differentiators
- - [what they emphasize as unique]
-
- ### Integrations
- - [count] integrations
- - Key: [list top 5-10]
-
- ### Product direction signals
- - [based on changelog / recent feature releases]
-
- ---
-
- ## Pricing
-
- | Tier | Price | Key Inclusions |
- |------|-------|---------------|
- | [Free/Starter] | [price] | [what's included] |
- | [Pro/Growth] | [price] | [what's included] |
- | [Enterprise] | [price] | [what's included] |
-
- **Billing**: [monthly/annual, discount for annual]
- **Free trial**: [yes/no, duration]
- **Notable**: [any pricing quirks: per-seat, usage-based, hidden costs]
-
- ---
-
- ## Customers & Social Proof
-
- **Named customers**: [list notable logos]
- **Industries**: [primary industries served]
- **Case study themes**: [what outcomes they highlight]
- **Review ratings**:
- - G2: [rating] ([count] reviews)
- - Capterra: [rating] ([count] reviews)
-
- ---
-
- ## SEO & Content Strategy
-
- **Organic strength**:
- - Estimated monthly organic traffic: [number]
- - Organic keywords (top 10): [count]
- - Organic traffic value: $[estimated]
-
- **Top organic pages** (by estimated traffic):
- 1. [page URL]: [keyword]: [est. traffic]
- 2. [page URL]: [keyword]: [est. traffic]
- 3. [page URL]: [keyword]: [est. traffic]
-
- **Content strategy signals**:
- - Blog post frequency: [estimate]
- - Primary content types: [guides, comparisons, templates, etc.]
- - Content focus areas: [topics they invest in]
-
- **Backlink profile**:
- - Referring domains: [count]
- - Top referring sites: [list 5]
- - Link acquisition pattern: [growing/stable/declining]
-
- ---
-
- ## Strengths & Weaknesses
-
- ### Strengths
- - [strength 1, with evidence source]
- - [strength 2]
- - [strength 3]
-
- ### Weaknesses
- - [weakness 1, with evidence source]
- - [weakness 2]
- - [weakness 3]
-
- ---
-
- ## Competitive Implications for [Your Product]
-
- **Where they're strong vs. us**: [areas where this competitor has an advantage]
-
- **Where we're strong vs. them**: [areas where you have an advantage]
-
- **Opportunities**: [gaps in their offering or positioning we can exploit]
-
- **Threats**: [areas where they're improving or gaining ground]
-
- ---
-
- ## Raw Data Sources
-
- - Homepage scraped: [date]
- - Pricing page scraped: [date]
- - SEO data pulled: [date]
- - Review data pulled: [date, sources]
+ raw/<alternative-slug>/<YYYY-MM-DD>/<capture-id>/
+ scrapes/
+ seo/
+ reviews/
+ supplied/
+ <alternative-slug>.md
+ _summary.md
+ _signals.md
```
- ---
-
- ### Summary Document
-
- After profiling all competitors, generate a `competitor-profiles/_summary.md` that includes:
-
- 1. **Competitor landscape overview**: one paragraph summarizing the competitive field
- 2. **Comparison table**: key metrics side by side for all profiled competitors
- 3. **Positioning map**: where each competitor sits (e.g., simple↔complex, cheap↔premium)
- 4. **Key takeaways**: 3-5 strategic observations from the research
- 5. **Gaps and opportunities**: where the market is underserved
-
- ---
-
- ## Quick Scan vs. Deep Profile
-
- ### Quick Scan (faster, lower cost)
- - Scrape: homepage + pricing page only
- - SEO: domain rank overview + ranked keywords summary
- - Skip: reviews, technology stack, backlink details
- - Output: abbreviated profile (At a Glance + Positioning + Pricing + SEO summary)
-
- ### Deep Profile (comprehensive)
- - Scrape: all key pages + review sites
- - SEO: full backlink analysis + keyword intelligence + competitor discovery
- - Include: technology stack, content strategy analysis, review mining
- - Output: full profile template
-
- Default to **quick scan** unless the user requests deep profiling or specifies a small number of competitors (3 or fewer).
-
- ---
-
- ## Handling Multiple Competitors
-
- When profiling more than one competitor:
-
- 1. **Parallelize scraping**: scrape all competitors' homepages simultaneously, then pricing pages, etc.
- 2. **Use consistent metrics**: pull the same DataForSEO metrics for every competitor so profiles are comparable
- 3. **Build the summary last**: after all individual profiles are complete
- 4. **Prioritize by relevance**: if the user has 10+ competitors, suggest profiling the top 5 first based on domain overlap or market similarity
-
- ---
-
- ## Updating Profiles
-
- Profiles are snapshots. When updating:
-
- - Check pricing pages first (most volatile)
- - Re-pull SEO metrics (traffic and rankings shift monthly)
- - Scan changelog for product changes
- - Update the "Generated" date
- - Note what changed since last profile in a `## Change Log` section at the bottom
-
- ---
-
- ## Task-Specific Questions
-
- Only ask if not answered by context or input:
+ Use only applicable subdirectories. Existing date-only raw folders remain valid.
+ A capture ID prevents overwriting same-day runs. Retain source IDs and precise
+ paths on refresh. Capture collected raw evidence before synthesis when saving is
+ part of the task. Reference supplied originals without rewriting them; respect
+ access/use restrictions. If capture is unavailable, disclose the limitation.
+ Never overwrite earlier raw captures. Preserve profile versions, change history,
+ and supersession links. _summary.md is a derived comparison, not another authority.
+ _signals.md is an optional noncanonical event view, not an installed monitor.
- 1. What competitor URLs should I profile?
- 2. Quick scan or deep profile?
- 3. Any specific dimensions to focus on (pricing, SEO, positioning)?
- 4. Should I compare findings against your product?
+ Save only in the user's project when requested or workflow-authorized.
+ Do not write into the skills repository during production runs.
+ Research or a cadence does not authorize outreach, account creation, spending,
+ installed monitoring, or sending alerts.
- ---
+ ## Ownership and handoffs
- ## Output Rules
+ | Need | Owner and boundary |
+ |---|---|
+ | Market conditions, category conventions, opportunity hypotheses | `market-intelligence`. Competitive gaps do not establish demand. |
+ | Customer experience themes and reusable language | `customer-research`. Reuse findings and attribute reported experience. |
+ | Closed-deal causes and buyer/seller disagreement | `win-loss-intelligence`. Competitor presence is not loss causality. |
+ | Objection library | `objection-intelligence`. Route evidence, not invented responses. |
+ | Where/whether to enter and company-specific sizing | `market-entry-brief`. Landscape relevance does not select a market. |
+ | Who to target and buying group | `icp-and-buyer-personas`. Their targeting claims do not select our ICP. |
+ | Our positioning, differentiation, and category/frame | `positioning-strategy`. Maps/whitespace are research, not strategic choices. |
+ | Messaging architecture | `messaging-framework`. Observed wording does not change our messages. |
+ | Pricing/packaging decisions | `pricing-strategy`. Record terms without recommending our price. |
+ | GTM or competitive response decisions | `go-to-market-strategy` and relevant decision owners. Surface review needs without committing actions. |
+ | Battlecards and comparison pages | `sales-enablement` and `competitor-alternatives`. Consume sourced views and approved company claims. |
+ | Integrated context and goal-relative readiness | `product-marketing-context`. Return findings without becoming an orchestrator. |
+ | Approved canon, drift verdicts, and persistence | `ssot-context-loop`. Explicit human approval is mandatory for canonical changes. |
- - No em dashes in output.
- - Open with the "Inputs and assumptions" note from `../_shared/evidence-gaps.md`.
- - Label every claim, benchmark, and number Sourced, Assumed, or Gap.
- - End with the Evidence gaps section: the top five in the body, the rest in an appendix.
- - Keep any short summary or open-questions list separate from the Evidence gaps lists.
+ Never write canonical files, decisions, manifests, or state.md.
+ Return to originating PMC or named requester using the packet in templates.md.
+ Suggest competitive context for living/06-competitive.md and supporting evidence
+ for living/07-evidence.md without duplicating claims. SSOT chooses destinations
+ and gates. Verified external changes are not SSOT drift verdicts and never
+ silently rewrite strategy or collateral.
- ## Related Skills
+ ## Output rules
- - **competitor-alternatives**: For creating comparison/alternative pages from these profiles
- - **customer-research**: For mining reviews and community sentiment in depth
- - **content-strategy**: For using competitor content gaps to plan your own content
- - **search-discoverability**: For auditing your own site relative to competitors
- - **sales-enablement**: For turning profiles into battle cards and sales collateral
- - **paid-ads**: For analyzing competitor ad strategies
- - **pricing-strategy**: For deeper pricing analysis informed by competitor profiles
+ - Open with Inputs and assumptions, selected mode, scope, and inspected coverage.
+ - Use Sourced / Assumed / Gap with kind, verification, confidence/rationale,
+ limitations, approval status, and review trigger.
+ - Expose derivations and labeled inputs without adding a Derived evidence tag.
+ - Preserve unknowns, opposing evidence, and completion-criteria assessment.
+ - End with ranked Evidence gaps: top five in the body, all others in an appendix.
+ Give owners and milestones, explicitly marking suggestions.
+ - Use no em dashes. Keep sentences short and bullets led by outcomes.