SEO Intelligence Toolkit
All-in-one SEO intelligence: keyword discovery, rank tracking, technical audits,
content gaps, competitor analysis, AI visibility, and GitHub SEO.
User request: $ARGUMENTS
Before running any commands, read references/nimble-playbook.md for Claude Code
constraints (no shell state, no &/wait, sub-agent permissions, communication style).
Tag all nimble CLI calls: nimble --client-source nimble-agent-skills <subcommand>. MCP requests are attributed at the transport level — see references/nimble-playbook.md.
Workflow Router
Detect the user's SEO intent from $ARGUMENTS and route to the appropriate
workflow. If the intent is ambiguous or generic ("help me with SEO"), ask which
workflow to run.
Available Workflows
| Workflow |
Triggers |
Reference |
| Keyword Research |
keyword opportunities, topic clusters, difficulty, what to rank for |
references/wf-keyword-research.md |
| Rank Tracker |
track rankings, keyword positions, ranking delta, position check |
references/wf-rank-tracker.md |
| Site Audit |
SEO audit, technical SEO, meta tags, schema, crawl for issues, CWV |
references/wf-site-audit.md |
| Content Gap |
content gap, keyword gap, compare coverage, missing topics |
references/wf-content-gap.md |
| Competitor Keywords |
competitor keywords, reverse-engineer SEO, competitor title tags |
references/wf-competitor-keywords.md |
| AI Visibility |
AI visibility, ChatGPT presence, Perplexity, AI Overview, GEO |
references/wf-ai-visibility.md |
| GitHub SEO |
github seo, repo discoverability, optimize readme, repo audit |
references/wf-github-seo.md |
Intent Detection
Map the request to one workflow:
- Keywords / topics / difficulty / clusters / "what to rank for" → Keyword Research
- Rankings / positions / tracking / delta / monitoring → Rank Tracker
- Audit / crawl / technical / meta / schema / links / CWV → Site Audit
- Gap / missing topics / coverage comparison / "what should I write" → Content Gap
- Competitor site crawl / reverse-engineer / on-page at scale → Competitor Keywords
- AI visibility / ChatGPT / Perplexity / AI Overview / GEO → AI Visibility
- GitHub / repo / README / discoverability → GitHub SEO
If unclear, present the options with AskUserQuestion:
Which SEO workflow should I run?
- Keyword Research — discover keyword opportunities and topic clusters
- Rank Tracker — check and track keyword positions over time
- Site Audit — full technical SEO crawl with JS rendering
- Content Gap — compare content coverage against competitors
- Competitor Keywords — reverse-engineer competitor on-page SEO at scale
- AI Visibility — measure brand presence across 5 AI platforms
- GitHub SEO — audit repository discoverability and README quality
Execution
Once a workflow is identified:
- Read the corresponding
references/wf-{name}.md
- Follow its instructions from Step 0 (Preflight) through to the output format
- All
references/ paths inside workflow files are relative to this skill's directory
Workflow Chaining
After completing a workflow, suggest natural next steps using sibling workflows.
Common chains:
- Site Audit → Keyword Research → Content Gap → Rank Tracker
- Keyword Research → Competitor Keywords → Content Gap
- AI Visibility → Content Gap → Keyword Research
When chaining, read the next workflow file and continue. Context from the
previous run (discovered domains, keyword lists, profile data) carries forward
— do not re-run preflight or re-ask onboarding questions.
Shared Configuration
All workflows use:
- Business profile + onboarding:
references/profile-and-onboarding.md
- Data persistence:
references/memory-and-distribution.md
- CLI patterns + constraints:
references/nimble-playbook.md
- AI platform agent discovery:
references/ai-platform-profiles.md
1---
2name: seo-intel
3description: |
4 SEO intelligence toolkit covering the full lifecycle via live web data:
5 keyword research, rank tracking, site audits, content gap analysis,
6 competitor keyword reverse-engineering, AI visibility across five platforms
7 (ChatGPT, Perplexity, Google AI, Gemini, Grok), and GitHub repo SEO.
8 Crawls real sites and SERPs via Nimble CLI — no fabricated metrics.
9
10 Triggers: "SEO", "keywords", "rank tracker", "site audit", "content gap",
11 "competitor keywords", "AI visibility", "GitHub SEO", "SERP analysis",
12 "keyword research", "technical SEO", "keyword difficulty", "topic
13 clusters", "ranking delta", "on-page SEO", "AI citation audit".
14
15 Do NOT use for competitor business signals — use `competitor-intel`
16 instead. Do NOT use for competitor messaging — use
17 `competitor-positioning` instead. Do NOT use for general web scraping
18 — use `nimble-web-expert` instead.
19allowed-tools:
20 - Bash(nimble:*)
21 - Bash(date:*)
22 - Bash(cat:*)
23 - Bash(mkdir:*)
24 - Bash(python3:*)
25 - Bash(echo:*)
26 - Bash(jq:*)
27 - Bash(ls:*)
28 - Bash(gh:*)
29 - Read
30 - Write
31 - Edit
32 - Glob
33 - Grep
34 - Agent
35 - AskUserQuestion
36metadata:
37 source: https://skillmd.com/skills/nimbleway/seo-intel
38 author: Nimbleway
39 version: 1.7.0
40 category: seo
41---
42
43# SEO Intelligence Toolkit
44
45All-in-one SEO intelligence: keyword discovery, rank tracking, technical audits,
46content gaps, competitor analysis, AI visibility, and GitHub SEO.
47
48User request: $ARGUMENTS
49
50**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
51constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
52Tag all `nimble` CLI calls: `nimble --client-source nimble-agent-skills <subcommand>`. MCP requests are attributed at the transport level — see `references/nimble-playbook.md`.
53
54---
55
56## Workflow Router
57
58Detect the user's SEO intent from `$ARGUMENTS` and route to the appropriate
59workflow. If the intent is ambiguous or generic ("help me with SEO"), ask which
60workflow to run.
61
62### Available Workflows
63
64| Workflow | Triggers | Reference |
65|----------|----------|-----------|
66| **Keyword Research** | keyword opportunities, topic clusters, difficulty, what to rank for | `references/wf-keyword-research.md` |
67| **Rank Tracker** | track rankings, keyword positions, ranking delta, position check | `references/wf-rank-tracker.md` |
68| **Site Audit** | SEO audit, technical SEO, meta tags, schema, crawl for issues, CWV | `references/wf-site-audit.md` |
69| **Content Gap** | content gap, keyword gap, compare coverage, missing topics | `references/wf-content-gap.md` |
70| **Competitor Keywords** | competitor keywords, reverse-engineer SEO, competitor title tags | `references/wf-competitor-keywords.md` |
71| **AI Visibility** | AI visibility, ChatGPT presence, Perplexity, AI Overview, GEO | `references/wf-ai-visibility.md` |
72| **GitHub SEO** | github seo, repo discoverability, optimize readme, repo audit | `references/wf-github-seo.md` |
73
74### Intent Detection
75
76Map the request to one workflow:
77
78- **Keywords / topics / difficulty / clusters / "what to rank for"** → Keyword Research
79- **Rankings / positions / tracking / delta / monitoring** → Rank Tracker
80- **Audit / crawl / technical / meta / schema / links / CWV** → Site Audit
81- **Gap / missing topics / coverage comparison / "what should I write"** → Content Gap
82- **Competitor site crawl / reverse-engineer / on-page at scale** → Competitor Keywords
83- **AI visibility / ChatGPT / Perplexity / AI Overview / GEO** → AI Visibility
84- **GitHub / repo / README / discoverability** → GitHub SEO
85
86If unclear, present the options with AskUserQuestion:
87
88> Which SEO workflow should I run?
89> - **Keyword Research** — discover keyword opportunities and topic clusters
90> - **Rank Tracker** — check and track keyword positions over time
91> - **Site Audit** — full technical SEO crawl with JS rendering
92> - **Content Gap** — compare content coverage against competitors
93> - **Competitor Keywords** — reverse-engineer competitor on-page SEO at scale
94> - **AI Visibility** — measure brand presence across 5 AI platforms
95> - **GitHub SEO** — audit repository discoverability and README quality
96
97### Execution
98
99Once a workflow is identified:
100
1011. **Read** the corresponding `references/wf-{name}.md`
1022. **Follow** its instructions from Step 0 (Preflight) through to the output format
1033. All `references/` paths inside workflow files are relative to this skill's directory
104
105### Workflow Chaining
106
107After completing a workflow, suggest natural next steps using sibling workflows.
108Common chains:
109
110- Site Audit → Keyword Research → Content Gap → Rank Tracker
111- Keyword Research → Competitor Keywords → Content Gap
112- AI Visibility → Content Gap → Keyword Research
113
114When chaining, read the next workflow file and continue. Context from the
115previous run (discovered domains, keyword lists, profile data) carries forward
116— do not re-run preflight or re-ask onboarding questions.
117
118### Shared Configuration
119
120All workflows use:
121- **Business profile + onboarding:** `references/profile-and-onboarding.md`
122- **Data persistence:** `references/memory-and-distribution.md`
123- **CLI patterns + constraints:** `references/nimble-playbook.md`
124- **AI platform agent discovery:** `references/ai-platform-profiles.md`