[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DHQZ50C2BFVWSHPCW8JMPF":3,"skill-same:01M7DHQZ50C2BFVWSHPCW8JMPF":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DHQZ50C2BFVWSHPCW8JMPF","competitor-profiling",null,"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,'...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcompetitor-profiling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competitor-profiling\ndescription: 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,'...\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-profiling\nsource_repo: coreyhaines31\u002Fmarketingskills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Competitor Profiling\n## When to Use\n\nUse this skill when you need 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,'...\n\n\nYou 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.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nBefore profiling, confirm:\n\n1. **Competitor URLs** — the list of competitor website URLs to profile\n2. **Your product** — what you do (if not in product marketing context)\n3. **Depth level** — quick scan (key facts only) or deep profile (full research)\n4. **Focus areas** — any specific dimensions to prioritize (e.g., pricing, positioning, SEO strength, content strategy)\n\nIf the user provides URLs and context is available, proceed without asking.\n\n---\n\n## Core Principles\n\n### 1. Facts Over Opinions\nEvery claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly.\n\n### 2. Structured and Comparable\nAll profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile.\n\n### 3. Current Data\nProfiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., \"pricing page last updated 2023\").\n\n### 4. Honest Assessment\nDon't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles.\n\n---\n\n## Saving Raw Data\n\nBefore 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.\n\n**Directory layout** (relative to project root):\n\n```\ncompetitor-profiles\u002F\n├── raw\u002F\n│   └── \u003Ccompetitor-slug>\u002F\n│       └── \u003CYYYY-MM-DD>\u002F\n│           ├── scrapes\u002F    # one .md file per scraped page (homepage.md, pricing.md, ...)\n│           ├── seo\u002F        # one .json file per DataForSEO call (backlinks-summary.json, ranked-keywords.json, ...)\n│           └── reviews\u002F    # one .md or .json file per review source (g2.md, capterra.md, ...)\n├── \u003Ccompetitor-slug>.md    # final synthesized profile\n└── _summary.md             # cross-competitor summary\n```\n\nRules:\n\n- `\u003Ccompetitor-slug>` is lowercase, hyphenated (e.g. `responsehub`, `safe-base`)\n- `\u003CYYYY-MM-DD>` is the date the data was pulled — supports re-running and diffing snapshots over time\n- Save each Firecrawl scrape as raw markdown to `scrapes\u002F\u003Cpage-name>.md`\n- Save each DataForSEO response as raw JSON to `seo\u002F\u003Cendpoint-name>.json`\n- Save each review source to `reviews\u002F\u003Csource>.md` (cleaned text) or `.json` (raw)\n- Always create the date folder fresh on a new run; never overwrite a prior date's data\n\nThe synthesized profile (`\u003Ccompetitor-slug>.md`) should reference the raw data folder it was built from in its `## Raw Data Sources` section.\n\n---\n\n## Research Process\n\n### Phase 1: Site Scraping (Firecrawl)\n\nFor each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging.\n\n#### Step 1: Map the site\n\nUse **Firecrawl Map** to discover the competitor's site structure and identify key pages:\n\n```\nfirecrawl_map → competitor URL\n```\n\nFrom the map, identify and prioritize these page types:\n- Homepage\n- Pricing page\n- Features \u002F product pages\n- About \u002F company page\n- Blog (top-level, for content strategy signals)\n- Customers \u002F case studies page\n- Integrations page\n- Changelog \u002F what's new (if exists)\n\n#### Step 2: Scrape key pages\n\nUse **Firecrawl Scrape** on each identified page:\n\n```\nfirecrawl_scrape → each key page URL\n```\n\nSave each result to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Fscrapes\u002F\u003Cpage-name>.md` before extracting fields.\n\nExtract from each page:\n\n| Page | What to Extract |\n|------|----------------|\n| **Homepage** | Headline, subheadline, value proposition, primary CTA, social proof claims, target audience signals |\n| **Pricing** | Tiers, prices, feature breakdown per tier, billing options, free tier\u002Ftrial details, enterprise pricing signals |\n| **Features** | Feature categories, key capabilities, how they describe each feature, screenshots\u002Fdemo signals |\n| **About** | Founding story, team size, funding, mission statement, headquarters |\n| **Customers** | Named customers, logos, industries served, case study themes |\n| **Integrations** | Integration count, key integrations, categories |\n| **Changelog** | Release velocity, recent focus areas, product direction signals |\n\n#### Step 3: Scrape competitor reviews (optional but high-value)\n\nUse **Firecrawl Scrape** or **Firecrawl Search** to find:\n- G2 reviews page for the competitor\n- Capterra reviews page\n- Product Hunt launch page\n- TrustRadius profile\n\nSave each scraped review page to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Freviews\u002F\u003Csource>.md`. Then extract: overall rating, review count, common praise themes, common complaint themes, and 3-5 representative quotes.\n\n---\n\n### Phase 2: SEO & Market Data (DataForSEO)\n\nUse DataForSEO MCP tools to gather quantitative competitive intelligence. Save each raw response as JSON to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Fseo\u002F\u003Cendpoint-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\u002Ftool-reference.md](references\u002Ftool-reference.md).\n\n#### Domain Authority & Backlinks\n\nUse **backlinks_summary** to get:\n- Domain rank \u002F authority score\n- Total backlinks\n- Referring domains count\n- Spam score\n\nUse **backlinks_referring_domains** for:\n- Top referring domains (quality signals)\n- Link acquisition patterns\n\n#### Keyword & Traffic Intelligence\n\nUse **dataforseo_labs_google_ranked_keywords** to get:\n- Total organic keywords ranking\n- Keywords in top 3, top 10, top 100\n- Estimated organic traffic\n\nUse **dataforseo_labs_google_domain_rank_overview** for:\n- Domain-level organic metrics\n- Estimated traffic value\n- Top keywords by traffic\n\nUse **dataforseo_labs_google_keywords_for_site** to discover:\n- What keywords they target\n- Content gaps vs. your site\n\n#### Competitive Positioning Data\n\nUse **dataforseo_labs_google_competitors_domain** to find:\n- Their closest organic competitors (may reveal competitors you haven't considered)\n- Market overlap data\n\nUse **dataforseo_labs_google_relevant_pages** to find:\n- Their highest-traffic pages\n- Content that drives the most organic value\n\n---\n\n### Phase 3: Synthesis\n\nCombine 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\u002Fbacklink profile supports that scale).\n\n---\n\n## Output Format\n\n### Profile Document Structure\n\nGenerate one markdown file per competitor, saved to a `competitor-profiles\u002F` directory in the project root.\n\n**Filename**: `competitor-profiles\u002F[competitor-name].md`\n\n**For the full profile and summary templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\nEach profile follows this structure:\n\n```markdown\n# [Competitor Name] — Competitor Profile\n\n**URL**: [website]\n**Generated**: [date]\n**Depth**: [quick scan \u002F deep profile]\n\n---\n\n## At a Glance\n\n| Metric | Value |\n|--------|-------|\n| Tagline | [from homepage] |\n| Founded | [year] |\n| Headquarters | [location] |\n| Team size | [estimate] |\n| Funding | [if known] |\n| Domain rank | [from DataForSEO] |\n| Est. organic traffic | [monthly] |\n| Referring domains | [count] |\n| Organic keywords | [count] |\n\n---\n\n## Positioning & Messaging\n\n**Primary value proposition**: [headline + subheadline from homepage]\n\n**Target audience**: [who they're speaking to, based on copy analysis]\n\n**Positioning angle**: [how they position — e.g., \"simplicity-first,\" \"enterprise-grade,\" \"all-in-one\"]\n\n**Key messaging themes**:\n- [theme 1 — with source page]\n- [theme 2]\n- [theme 3]\n\n---\n\n## Product & Features\n\n### Core capabilities\n- [capability 1] — [brief description from their site]\n- [capability 2]\n- ...\n\n### Notable differentiators\n- [what they emphasize as unique]\n\n### Integrations\n- [count] integrations\n- Key: [list top 5-10]\n\n### Product direction signals\n- [based on changelog \u002F recent feature releases]\n\n---\n\n## Pricing\n\n| Tier | Price | Key Inclusions |\n|------|-------|---------------|\n| [Free\u002FStarter] | [price] | [what's included] |\n| [Pro\u002FGrowth] | [price] | [what's included] |\n| [Enterprise] | [price] | [what's included] |\n\n**Billing**: [monthly\u002Fannual, discount for annual]\n**Free trial**: [yes\u002Fno, duration]\n**Notable**: [any pricing quirks — per-seat, usage-based, hidden costs]\n\n---\n\n## Customers & Social Proof\n\n**Named customers**: [list notable logos]\n**Industries**: [primary industries served]\n**Case study themes**: [what outcomes they highlight]\n**Review ratings**:\n- G2: [rating] ([count] reviews)\n- Capterra: [rating] ([count] reviews)\n\n---\n\n## SEO & Content Strategy\n\n**Organic strength**:\n- Estimated monthly organic traffic: [number]\n- Organic keywords (top 10): [count]\n- Organic traffic value: $[estimated]\n\n**Top organic pages** (by estimated traffic):\n1. [page URL] — [keyword] — [est. traffic]\n2. [page URL] — [keyword] — [est. traffic]\n3. [page URL] — [keyword] — [est. traffic]\n\n**Content strategy signals**:\n- Blog post frequency: [estimate]\n- Primary content types: [guides, comparisons, templates, etc.]\n- Content focus areas: [topics they invest in]\n\n**Backlink profile**:\n- Referring domains: [count]\n- Top referring sites: [list 5]\n- Link acquisition pattern: [growing\u002Fstable\u002Fdeclining]\n\n---\n\n## Strengths & Weaknesses\n\n### Strengths\n- [strength 1 — with evidence source]\n- [strength 2]\n- [strength 3]\n\n### Weaknesses\n- [weakness 1 — with evidence source]\n- [weakness 2]\n- [weakness 3]\n\n---\n\n## Competitive Implications for [Your Product]\n\n**Where they're strong vs. us**: [areas where this competitor has an advantage]\n\n**Where we're strong vs. them**: [areas where you have an advantage]\n\n**Opportunities**: [gaps in their offering or positioning we can exploit]\n\n**Threats**: [areas where they're improving or gaining ground]\n\n---\n\n## Raw Data Sources\n\n- Homepage scraped: [date]\n- Pricing page scraped: [date]\n- SEO data pulled: [date]\n- Review data pulled: [date, sources]\n```\n\n---\n\n### Summary Document\n\nAfter profiling all competitors, generate a `competitor-profiles\u002F_summary.md` that includes:\n\n1. **Competitor landscape overview** — one paragraph summarizing the competitive field\n2. **Comparison table** — key metrics side by side for all profiled competitors\n3. **Positioning map** — where each competitor sits (e.g., simple↔complex, cheap↔premium)\n4. **Key takeaways** — 3-5 strategic observations from the research\n5. **Gaps and opportunities** — where the market is underserved\n\n---\n\n## Quick Scan vs. Deep Profile\n\n### Quick Scan (faster, lower cost)\n- Scrape: homepage + pricing page only\n- SEO: domain rank overview + ranked keywords summary\n- Skip: reviews, technology stack, backlink details\n- Output: abbreviated profile (At a Glance + Positioning + Pricing + SEO summary)\n\n### Deep Profile (comprehensive)\n- Scrape: all key pages + review sites\n- SEO: full backlink analysis + keyword intelligence + competitor discovery\n- Include: technology stack, content strategy analysis, review mining\n- Output: full profile template\n\nDefault to **quick scan** unless the user requests deep profiling or specifies a small number of competitors (3 or fewer).\n\n---\n\n## Handling Multiple Competitors\n\nWhen profiling more than one competitor:\n\n1. **Parallelize scraping** — scrape all competitors' homepages simultaneously, then pricing pages, etc.\n2. **Use consistent metrics** — pull the same DataForSEO metrics for every competitor so profiles are comparable\n3. **Build the summary last** — after all individual profiles are complete\n4. **Prioritize by relevance** — if the user has 10+ competitors, suggest profiling the top 5 first based on domain overlap or market similarity\n\n---\n\n## Updating Profiles\n\nProfiles are snapshots. When updating:\n\n- Check pricing pages first (most volatile)\n- Re-pull SEO metrics (traffic and rankings shift monthly)\n- Scan changelog for product changes\n- Update the \"Generated\" date\n- Note what changed since last profile in a `## Change Log` section at the bottom\n\n---\n\n## Task-Specific Questions\n\nOnly ask if not answered by context or input:\n\n1. What competitor URLs should I profile?\n2. Quick scan or deep profile?\n3. Any specific dimensions to focus on (pricing, SEO, positioning)?\n4. Should I compare findings against your product?\n\n---\n\n## Related Skills\n\n- **competitors**: For creating comparison\u002Falternative pages from these profiles\n- **prospecting**: For broader list-building qualification (this skill does deep research on specific accounts; prospecting builds the initial list)\n- **customer-research**: For mining reviews and community sentiment in depth\n- **content-strategy**: For using competitor content gaps to plan your own content\n- **seo-audit**: For auditing your own site relative to competitors\n- **sales-enablement**: For turning profiles into battle cards and sales collateral\n- **ads**: For analyzing competitor ad strategies\n- **pricing**: For deeper pricing analysis informed by competitor profiles\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Competitor Profiling\n## When to Use\n\nUse this skill when you need 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,'...\n\n\nYou 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.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nBefore profiling, confirm:\n\n1. **Competitor URLs** — the list of competitor website URLs to profile\n2. **Your product** — what you do (if not in product marketing context)\n3. **Depth level** — quick scan (key facts only) or deep profile (full research)\n4. **Focus areas** — any specific dimensions to prioritize (e.g., pricing, positioning, SEO strength, content strategy)\n\nIf the user provides URLs and context is available, proceed without asking.\n\n---\n\n## Core Principles\n\n### 1. Facts Over Opinions\nEvery claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly.\n\n### 2. Structured and Comparable\nAll profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile.\n\n### 3. Current Data\nProfiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., \"pricing page last updated 2023\").\n\n### 4. Honest Assessment\nDon't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles.\n\n---\n\n## Saving Raw Data\n\nBefore 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.\n\n**Directory layout** (relative to project root):\n\n```\ncompetitor-profiles\u002F\n├── raw\u002F\n│   └── \u003Ccompetitor-slug>\u002F\n│       └── \u003CYYYY-MM-DD>\u002F\n│           ├── scrapes\u002F    # one .md file per scraped page (homepage.md, pricing.md, ...)\n│           ├── seo\u002F        # one .json file per DataForSEO call (backlinks-summary.json, ranked-keywords.json, ...)\n│           └── reviews\u002F    # one .md or .json file per review source (g2.md, capterra.md, ...)\n├── \u003Ccompetitor-slug>.md    # final synthesized profile\n└── _summary.md             # cross-competitor summary\n```\n\nRules:\n\n- `\u003Ccompetitor-slug>` is lowercase, hyphenated (e.g. `responsehub`, `safe-base`)\n- `\u003CYYYY-MM-DD>` is the date the data was pulled — supports re-running and diffing snapshots over time\n- Save each Firecrawl scrape as raw markdown to `scrapes\u002F\u003Cpage-name>.md`\n- Save each DataForSEO response as raw JSON to `seo\u002F\u003Cendpoint-name>.json`\n- Save each review source to `reviews\u002F\u003Csource>.md` (cleaned text) or `.json` (raw)\n- Always create the date folder fresh on a new run; never overwrite a prior date's data\n\nThe synthesized profile (`\u003Ccompetitor-slug>.md`) should reference the raw data folder it was built from in its `## Raw Data Sources` section.\n\n---\n\n## Research Process\n\n### Phase 1: Site Scraping (Firecrawl)\n\nFor each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging.\n\n#### Step 1: Map the site\n\nUse **Firecrawl Map** to discover the competitor's site structure and identify key pages:\n\n```\nfirecrawl_map → competitor URL\n```\n\nFrom the map, identify and prioritize these page types:\n- Homepage\n- Pricing page\n- Features \u002F product pages\n- About \u002F company page\n- Blog (top-level, for content strategy signals)\n- Customers \u002F case studies page\n- Integrations page\n- Changelog \u002F what's new (if exists)\n\n#### Step 2: Scrape key pages\n\nUse **Firecrawl Scrape** on each identified page:\n\n```\nfirecrawl_scrape → each key page URL\n```\n\nSave each result to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Fscrapes\u002F\u003Cpage-name>.md` before extracting fields.\n\nExtract from each page:\n\n| Page | What to Extract |\n|------|----------------|\n| **Homepage** | Headline, subheadline, value proposition, primary CTA, social proof claims, target audience signals |\n| **Pricing** | Tiers, prices, feature breakdown per tier, billing options, free tier\u002Ftrial details, enterprise pricing signals |\n| **Features** | Feature categories, key capabilities, how they describe each feature, screenshots\u002Fdemo signals |\n| **About** | Founding story, team size, funding, mission statement, headquarters |\n| **Customers** | Named customers, logos, industries served, case study themes |\n| **Integrations** | Integration count, key integrations, categories |\n| **Changelog** | Release velocity, recent focus areas, product direction signals |\n\n#### Step 3: Scrape competitor reviews (optional but high-value)\n\nUse **Firecrawl Scrape** or **Firecrawl Search** to find:\n- G2 reviews page for the competitor\n- Capterra reviews page\n- Product Hunt launch page\n- TrustRadius profile\n\nSave each scraped review page to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Freviews\u002F\u003Csource>.md`. Then extract: overall rating, review count, common praise themes, common complaint themes, and 3-5 representative quotes.\n\n---\n\n### Phase 2: SEO & Market Data (DataForSEO)\n\nUse DataForSEO MCP tools to gather quantitative competitive intelligence. Save each raw response as JSON to `competitor-profiles\u002Fraw\u002F\u003Ccompetitor-slug>\u002F\u003CYYYY-MM-DD>\u002Fseo\u002F\u003Cendpoint-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\u002Ftool-reference.md](references\u002Ftool-reference.md).\n\n#### Domain Authority & Backlinks\n\nUse **backlinks_summary** to get:\n- Domain rank \u002F authority score\n- Total backlinks\n- Referring domains count\n- Spam score\n\nUse **backlinks_referring_domains** for:\n- Top referring domains (quality signals)\n- Link acquisition patterns\n\n#### Keyword & Traffic Intelligence\n\nUse **dataforseo_labs_google_ranked_keywords** to get:\n- Total organic keywords ranking\n- Keywords in top 3, top 10, top 100\n- Estimated organic traffic\n\nUse **dataforseo_labs_google_domain_rank_overview** for:\n- Domain-level organic metrics\n- Estimated traffic value\n- Top keywords by traffic\n\nUse **dataforseo_labs_google_keywords_for_site** to discover:\n- What keywords they target\n- Content gaps vs. your site\n\n#### Competitive Positioning Data\n\nUse **dataforseo_labs_google_competitors_domain** to find:\n- Their closest organic competitors (may reveal competitors you haven't considered)\n- Market overlap data\n\nUse **dataforseo_labs_google_relevant_pages** to find:\n- Their highest-traffic pages\n- Content that drives the most organic value\n\n---\n\n### Phase 3: Synthesis\n\nCombine 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\u002Fbacklink profile supports that scale).\n\n---\n\n## Output Format\n\n### Profile Document Structure\n\nGenerate one markdown file per competitor, saved to a `competitor-profiles\u002F` directory in the project root.\n\n**Filename**: `competitor-profiles\u002F[competitor-name].md`\n\n**For the full profile and summary templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\nEach profile follows this structure:\n\n```markdown\n# [Competitor Name] — Competitor Profile\n\n**URL**: [website]\n**Generated**: [date]\n**Depth**: [quick scan \u002F deep profile]\n\n---\n\n## At a Glance\n\n| Metric | Value |\n|--------|-------|\n| Tagline | [from homepage] |\n| Founded | [year] |\n| Headquarters | [location] |\n| Team size | [estimate] |\n| Funding | [if known] |\n| Domain rank | [from DataForSEO] |\n| Est. organic traffic | [monthly] |\n| Referring domains | [count] |\n| Organic keywords | [count] |\n\n---\n\n## Positioning & Messaging\n\n**Primary value proposition**: [headline + subheadline from homepage]\n\n**Target audience**: [who they're speaking to, based on copy analysis]\n\n**Positioning angle**: [how they position — e.g., \"simplicity-first,\" \"enterprise-grade,\" \"all-in-one\"]\n\n**Key messaging themes**:\n- [theme 1 — with source page]\n- [theme 2]\n- [theme 3]\n\n---\n\n## Product & Features\n\n### Core capabilities\n- [capability 1] — [brief description from their site]\n- [capability 2]\n- ...\n\n### Notable differentiators\n- [what they emphasize as unique]\n\n### Integrations\n- [count] integrations\n- Key: [list top 5-10]\n\n### Product direction signals\n- [based on changelog \u002F recent feature releases]\n\n---\n\n## Pricing\n\n| Tier | Price | Key Inclusions |\n|------|-------|---------------|\n| [Free\u002FStarter] | [price] | [what's included] |\n| [Pro\u002FGrowth] | [price] | [what's included] |\n| [Enterprise] | [price] | [what's included] |\n\n**Billing**: [monthly\u002Fannual, discount for annual]\n**Free trial**: [yes\u002Fno, duration]\n**Notable**: [any pricing quirks — per-seat, usage-based, hidden costs]\n\n---\n\n## Customers & Social Proof\n\n**Named customers**: [list notable logos]\n**Industries**: [primary industries served]\n**Case study themes**: [what outcomes they highlight]\n**Review ratings**:\n- G2: [rating] ([count] reviews)\n- Capterra: [rating] ([count] reviews)\n\n---\n\n## SEO & Content Strategy\n\n**Organic strength**:\n- Estimated monthly organic traffic: [number]\n- Organic keywords (top 10): [count]\n- Organic traffic value: $[estimated]\n\n**Top organic pages** (by estimated traffic):\n1. [page URL] — [keyword] — [est. traffic]\n2. [page URL] — [keyword] — [est. traffic]\n3. [page URL] — [keyword] — [est. traffic]\n\n**Content strategy signals**:\n- Blog post frequency: [estimate]\n- Primary content types: [guides, comparisons, templates, etc.]\n- Content focus areas: [topics they invest in]\n\n**Backlink profile**:\n- Referring domains: [count]\n- Top referring sites: [list 5]\n- Link acquisition pattern: [growing\u002Fstable\u002Fdeclining]\n\n---\n\n## Strengths & Weaknesses\n\n### Strengths\n- [strength 1 — with evidence source]\n- [strength 2]\n- [strength 3]\n\n### Weaknesses\n- [weakness 1 — with evidence source]\n- [weakness 2]\n- [weakness 3]\n\n---\n\n## Competitive Implications for [Your Product]\n\n**Where they're strong vs. us**: [areas where this competitor has an advantage]\n\n**Where we're strong vs. them**: [areas where you have an advantage]\n\n**Opportunities**: [gaps in their offering or positioning we can exploit]\n\n**Threats**: [areas where they're improving or gaining ground]\n\n---\n\n## Raw Data Sources\n\n- Homepage scraped: [date]\n- Pricing page scraped: [date]\n- SEO data pulled: [date]\n- Review data pulled: [date, sources]\n```\n\n---\n\n### Summary Document\n\nAfter profiling all competitors, generate a `competitor-profiles\u002F_summary.md` that includes:\n\n1. **Competitor landscape overview** — one paragraph summarizing the competitive field\n2. **Comparison table** — key metrics side by side for all profiled competitors\n3. **Positioning map** — where each competitor sits (e.g., simple↔complex, cheap↔premium)\n4. **Key takeaways** — 3-5 strategic observations from the research\n5. **Gaps and opportunities** — where the market is underserved\n\n---\n\n## Quick Scan vs. Deep Profile\n\n### Quick Scan (faster, lower cost)\n- Scrape: homepage + pricing page only\n- SEO: domain rank overview + ranked keywords summary\n- Skip: reviews, technology stack, backlink details\n- Output: abbreviated profile (At a Glance + Positioning + Pricing + SEO summary)\n\n### Deep Profile (comprehensive)\n- Scrape: all key pages + review sites\n- SEO: full backlink analysis + keyword intelligence + competitor discovery\n- Include: technology stack, content strategy analysis, review mining\n- Output: full profile template\n\nDefault to **quick scan** unless the user requests deep profiling or specifies a small number of competitors (3 or fewer).\n\n---\n\n## Handling Multiple Competitors\n\nWhen profiling more than one competitor:\n\n1. **Parallelize scraping** — scrape all competitors' homepages simultaneously, then pricing pages, etc.\n2. **Use consistent metrics** — pull the same DataForSEO metrics for every competitor so profiles are comparable\n3. **Build the summary last** — after all individual profiles are complete\n4. **Prioritize by relevance** — if the user has 10+ competitors, suggest profiling the top 5 first based on domain overlap or market similarity\n\n---\n\n## Updating Profiles\n\nProfiles are snapshots. When updating:\n\n- Check pricing pages first (most volatile)\n- Re-pull SEO metrics (traffic and rankings shift monthly)\n- Scan changelog for product changes\n- Update the \"Generated\" date\n- Note what changed since last profile in a `## Change Log` section at the bottom\n\n---\n\n## Task-Specific Questions\n\nOnly ask if not answered by context or input:\n\n1. What competitor URLs should I profile?\n2. Quick scan or deep profile?\n3. Any specific dimensions to focus on (pricing, SEO, positioning)?\n4. Should I compare findings against your product?\n\n---\n\n## Related Skills\n\n- **competitors**: For creating comparison\u002Falternative pages from these profiles\n- **prospecting**: For broader list-building qualification (this skill does deep research on specific accounts; prospecting builds the initial list)\n- **customer-research**: For mining reviews and community sentiment in depth\n- **content-strategy**: For using competitor content gaps to plan your own content\n- **seo-audit**: For auditing your own site relative to competitors\n- **sales-enablement**: For turning profiles into battle cards and sales collateral\n- **ads**: For analyzing competitor ad strategies\n- **pricing**: For deeper pricing analysis informed by competitor profiles\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-profiling",1782864000000,"coreyhaines31\u002Fmarketingskills","community","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fcompetitor-profiling",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill competitor-profiling",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill competitor-profiling",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill competitor-profiling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcompetitor-profiling\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Fevals.json","REFERENCE","参考文档",7496,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcompetitor-profiling\u002Fevals\u002Fevals.json",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ftemplates.md",4668,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcompetitor-profiling\u002Freferences\u002Ftemplates.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ftool-reference.md",7082,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcompetitor-profiling\u002Freferences\u002Ftool-reference.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]