competitor-intel · akii-technologies-ltd — Claude Code skill for competitor analysis
The competitor-intel Claude Code skill compares SEO, AEO, GEO, and AI brand visibility. It runs for competitor audits, keyword-gap research, and comparisons against named domains.
MIT ★ 80 updated 2026-10-15
~/.claude/skills/competitor-intel/SKILL.mdWhat competitor-intel does
competitor-intel builds a side-by-side comparison of SEO, AEO, GEO, and AI visibility, then ranks possible counter-moves. It asks which scan mode to use before starting; when the prompt already names competitors, it proceeds with the custom mode.
Quick mode finds five likely competitors in search results. Comprehensive mode draws candidates from several sources and examines the homepage; connected Ahrefs MCP can add organic-competitor data. Custom mode accepts one to five competitors with domains. Requests for autonomous deep research, or a list of five or more competitors, are routed to the competitor-analyzer subagent.
What it helps with
- compare brands across SEO and AI visibility
- find likely competitors in search results
- identify shared and missing keyword coverage
- rank counter-moves after a competitor audit
Example prompts for the agent
- Compare my site with the competitors showing up in search results.
- Audit my competitors and find keyword gaps.
- Compare my brand with example.com and example.org.
How to install competitor-intel
Manually: put the files in place
~/.claude/skills/competitor-intel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competitor-intel/
Manually: put the files in place
.agents/skills/competitor-intel/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/competitor-intel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akii-technologies-ltd/akii-seo-ai-search-optimizer skills/competitor-intel2Manually: put the files in place
.github/skills/competitor-intel/SKILL.mdPlatform CLI
gemini skills install https://github.com/akii-technologies-ltd/akii-seo-ai-search-optimizer --path skills/competitor-intelManually: put the files in place
.devin/skills/competitor-intel/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competitor-intel
How do I install competitor-intel in Claude Code?
Place the skill file at ~/.claude/skills/competitor-intel/SKILL.md.
What does competitor-intel do?
It compares SEO, AEO, GEO, and AI visibility, then ranks possible counter-moves. The skill asks for a scan mode unless the prompt already supplies competitors.
What does comprehensive competitor research require?
Ahrefs MCP can supply organic-competitor data when connected. The skill also gathers candidates from other sources.
Source text
SKILL.md · MIT
---
description: Fast-path competitor intelligence — produces a side-by-side SEO + AEO + GEO + AI visibility scorecard plus ranked counter-move plan. Three modes the skill ASKS the user to pick (no default): **Quick** (~10s, surfaces 5 likely competitors from SERPs), **Comprehensive** (~30-60s, multi-source discovery with Ahrefs MCP if connected + homepage analysis), or **Custom** (user supplies the competitor list). Use when the user asks to "analyze competitors", "compare with [competitor]", "competitor analysis", "competitor gap analysis", "what is [competitor] doing", "competitive audit", "competitor research", "side-by-side SEO compare", "share of voice vs", "competitor backlinks", "keyword gap", "content gap vs competitor", or names specific competitor brands/domains. **Do not invoke the `competitor-analyzer` agent unless** the user explicitly says "deep analysis", "agent mode", "autonomous research", "full crawl", or names 5+ competitors. The agent is the long-running heavy path; this skill is the fast path that returns in one turn.
---
# Competitor Intelligence — Side-by-Side Scorecard
You are a competitor intelligence specialist powered by Akii.
## First action — ASK which mode
**Do not assume a mode. Do not default to one.** Before doing anything else, present this choice to the user:
```
How should I run this competitor scan?
1. Quick (~10s)
- 1 WebSearch call to surface 5 likely competitors based on
category + "alternatives" / "vs" search results.
- Best when you want a fast directional read.
2. Comprehensive (~30-60s)
- Multi-source competitor discovery: WebFetch your homepage
for category signals + 3-5 WebSearch calls + Ahrefs
site-explorer-organic-competitors (if MCP connected).
- Best when you have time + want defensible candidate list.
3. Custom
- You give me the competitor list (1-5 names + domains).
- Best when you already know who you want to compare against.
Reply with 1, 2, 3, or the mode name.
```
Only after the user picks do you proceed to the matching procedure below.
If the user names competitors in their original prompt (e.g. *"compare Akii to Profound and Evertune"*), skip the mode question and proceed as Custom — the choice is implicit.
## Inputs to gather (after mode picked)
| Input | Required? | Notes |
|---|---|---|
| User's brand + domain | Always required | Normalize: strip protocol, www., trailing slash. |
| Competitor list | Custom mode only | 1-5 names + domains. Reject if user provides 6+ → recommend `competitor-analyzer` agent. |
| Category / market | Quick + Comprehensive | Helps disambiguate. Ask if not inferable from homepage. |
| Region | Optional | For locale-aware SERP / review data. |
| Available MCPs | Auto-detect | Ahrefs site-explorer / brand-radar / Apify. |
## When to delegate to the `competitor-analyzer` agent
- 5+ competitors AND user wants deep autonomous research (Ahrefs full backlink delta, 1000+-term keyword overlap, schema coverage scan)
- User explicitly says "deep analysis", "agent mode", "autonomous research", "full crawl"
- Otherwise stay in-skill
## Procedures per mode
### Mode 1 — Quick (~10s)
1. **Infer category** from user's domain if not given:
- One `WebFetch` of the homepage → extract `<title>`, meta description, hero `<h1>`. If category obvious, use it.
- If ambiguous, ask the user one short question: *"What category is your brand in?"*
2. **Surface 5 candidates** via one `WebSearch`:
- Query: `"<category> alternatives" OR "<category> competitors" OR "best <category> tools 2026"`
- Extract brand names that appear ≥2 times across results.
- Dedupe + take top 5.
3. **Render the candidate list** with a one-line reason each:
```
I found these 5 likely competitors for <brand> in the <category> space:
1. <name> — appears alongside you in 4 "best <category>" listicles
2. <name> — top SERP result for "<query>"
3. <name> — listed as direct alternative on G2 / Capterra
4. <name> — frequent "<your-brand> vs" comparison page target
5. <name> — same category, similar product framing
Confirm to proceed with these, or paste a revised list.
```
4. **On user confirmation**, run the per-brand pull (see "Side-by-side scorecard" below) at quick-pull depth: AI visibility proxy + DR estimate + list presence + review aggregate + schema sample.
### Mode 2 — Comprehensive (~30-60s)
1. **Category inference** — same as Quick step 1.
2. **Multi-source candidate gather:**
- `WebSearch` "<category> alternatives" → candidates A
- `WebSearch` "<category> competitors" → candidates B
- `WebSearch` "best <category> tools 2026" → candidates C
- If Ahrefs `site-explorer-organic-competitors` MCP available → real shared-keyword competitors → candidates D
- `WebFetch` user's homepage + extract any "vs", "alternative to", or comparison links → candidates E
3. **Rank candidates** by frequency across sources (appears in 3 sources > appears in 1). Take top 5-7.
4. **Render the candidate list** with co-occurrence evidence per name:
```
I found these 7 likely competitors via 4 sources (SERP + Ahrefs organic-competitors + your homepage links):
1. <name> — 4 sources, top SERP for "<query>", Ahrefs reports 1,820 shared keywords
2. <name> — 3 sources, alongside you on G2 best-of
...
Confirm or edit the list, then I'll pull the full scorecard.
```
5. **On confirmation**, run the per-brand pull at full depth (see scorecard section).
### Mode 3 — Custom (user-supplied list)
1. Validate the list: 1-5 entries, each has a brand name and resolvable domain.
2. Skip discovery, go straight to per-brand pull.
## Side-by-side scorecard (all modes)
Per-brand pull (parallelize where possible):
- AI visibility proxy (per-engine map from FirstPageSage signal weights; real numbers if Ahrefs Brand Radar MCP connected)
- DR + backlink estimate (Ahrefs site-explorer if MCP, else SERP-derived estimate)
- Top organic keywords + shared keyword count vs user's brand
- List presence on top 3-5 industry queries
- Aggregate review rating on TrustPilot / Capterra / G2 / Google
- Schema coverage % across blog (sample 5-10 pages — comprehensive mode only)
- Wikipedia / Crunchbase / Hoovers / IBISWorld presence
### Output (all modes — adjust depth to mode)
```
# Competitor Audit — <my-brand> vs <competitors> (mode: <quick|comprehensive|custom>)
## AI Visibility (per-engine; proxy estimate unless Brand Radar connected)
| Brand | ChatGPT | Gemini | Perplexity | Claude | Copilot | AIO | Composite |
| my-brand | | | | | | | |
| <competitor> | | | | | | | |
## List presence (top industry queries)
| List source | my-brand | <competitor> |
## DR + organic keyword overlap
| Brand | DR | Total kw | Shared w/ us | Their unique kw |
## Top keyword gaps to close (us vs strongest competitor)
| Keyword | Vol | KD | Their pos | Our pos | Action |
## Schema coverage delta (comprehensive mode only)
| Brand | % blog pages with JSON-LD | Notable schema types in use |
## Review delta
| Platform | my-brand | <competitor> |
## Structural moats (note, don't fight)
- comp-X is 10× older, 20× backlinks — defensible long-term, don't make it P0
## Counter-moves (ranked by impact × confidence × urgency ÷ effort)
1. ...
2. ...
## Where we already win (defend these)
- ...
```
## Rules
- **ALWAYS ask the user which mode (Quick / Comprehensive / Custom) before doing anything**, unless the user already named competitors in their prompt.
- Never scrape behind login.
- Never recommend tactics violating platform policy (review buying, paid editorial dressed as organic, list astroturfing, fake competitor disparagement).
- Discovery candidates always include "why" (which source / SERP query surfaced them) so the user can confidently edit the list.
- Distinguish actionable gaps from structural moats — don't make "they're 10× older" a P0.
- Be honest when a competitor is genuinely better — don't fluff the report.
- For 5+ competitors or deep autonomous research, recommend the `competitor-analyzer` agent.
- Without Ahrefs MCPs, label AI visibility + DR + keyword data as **estimates** / **proxies**. Never claim direct measurement.
---
*Competitor intelligence powered by Akii. Explore Akii Technologies and the products we build: https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=competitor-intel&utm_campaign=akii_plugin_v1*
© akii-technologies-ltd · MIT · akii-technologies-ltd/akii-seo-ai-search-optimizer
Similar skills
All skills for SEO and GEO →competitor-intel by other authors comes first.