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 opencode
constraints (no shell state, no &/wait, sub-agent permissions, communication style).
Tag all nimble CLI calls: nimble --client-source skill-seo-intel <subcommand>. MCP path: not yet supported — see references/nimble-playbook.md for status.
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-intel3description: SEO intelligence toolkit covering the full lifecycle via live web data: keyword research, rank tracking, site audits, content gap analysis, competitor.4---56# SEO Intelligence Toolkit78All-in-one SEO intelligence: keyword discovery, rank tracking, technical audits,9content gaps, competitor analysis, AI visibility, and GitHub SEO.1011User request: $ARGUMENTS1213**Before running any commands**, read `references/nimble-playbook.md` for opencode14constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).15Tag all `nimble` CLI calls: `nimble --client-source skill-seo-intel <subcommand>`. MCP path: not yet supported — see `references/nimble-playbook.md` for status.1617---1819## Workflow Router2021Detect the user's SEO intent from `$ARGUMENTS` and route to the appropriate22workflow. If the intent is ambiguous or generic ("help me with SEO"), ask which23workflow to run.2425### Available Workflows2627| Workflow | Triggers | Reference |28|----------|----------|-----------|29| **Keyword Research** | keyword opportunities, topic clusters, difficulty, what to rank for | `references/wf-keyword-research.md` |30| **Rank Tracker** | track rankings, keyword positions, ranking delta, position check | `references/wf-rank-tracker.md` |31| **Site Audit** | SEO audit, technical SEO, meta tags, schema, crawl for issues, CWV | `references/wf-site-audit.md` |32| **Content Gap** | content gap, keyword gap, compare coverage, missing topics | `references/wf-content-gap.md` |33| **Competitor Keywords** | competitor keywords, reverse-engineer SEO, competitor title tags | `references/wf-competitor-keywords.md` |34| **AI Visibility** | AI visibility, ChatGPT presence, Perplexity, AI Overview, GEO | `references/wf-ai-visibility.md` |35| **GitHub SEO** | github seo, repo discoverability, optimize readme, repo audit | `references/wf-github-seo.md` |3637### Intent Detection3839Map the request to one workflow:4041- **Keywords / topics / difficulty / clusters / "what to rank for"** → Keyword Research42- **Rankings / positions / tracking / delta / monitoring** → Rank Tracker43- **Audit / crawl / technical / meta / schema / links / CWV** → Site Audit44- **Gap / missing topics / coverage comparison / "what should I write"** → Content Gap45- **Competitor site crawl / reverse-engineer / on-page at scale** → Competitor Keywords46- **AI visibility / ChatGPT / Perplexity / AI Overview / GEO** → AI Visibility47- **GitHub / repo / README / discoverability** → GitHub SEO4849If unclear, present the options with AskUserQuestion:5051> Which SEO workflow should I run?52> - **Keyword Research** — discover keyword opportunities and topic clusters53> - **Rank Tracker** — check and track keyword positions over time54> - **Site Audit** — full technical SEO crawl with JS rendering55> - **Content Gap** — compare content coverage against competitors56> - **Competitor Keywords** — reverse-engineer competitor on-page SEO at scale57> - **AI Visibility** — measure brand presence across 5 AI platforms58> - **GitHub SEO** — audit repository discoverability and README quality5960### Execution6162Once a workflow is identified:63641. **Read** the corresponding `references/wf-{name}.md`652. **Follow** its instructions from Step 0 (Preflight) through to the output format663. All `references/` paths inside workflow files are relative to this skill's directory6768### Workflow Chaining6970After completing a workflow, suggest natural next steps using sibling workflows.71Common chains:7273- Site Audit → Keyword Research → Content Gap → Rank Tracker74- Keyword Research → Competitor Keywords → Content Gap75- AI Visibility → Content Gap → Keyword Research7677When chaining, read the next workflow file and continue. Context from the78previous run (discovered domains, keyword lists, profile data) carries forward79— do not re-run preflight or re-ask onboarding questions.8081### Shared Configuration8283All workflows use:84- **Business profile + onboarding:** `references/profile-and-onboarding.md`85- **Data persistence:** `references/memory-and-distribution.md`86- **CLI patterns + constraints:** `references/nimble-playbook.md`87- **AI platform agent discovery:** `references/ai-platform-profiles.md`
yigityildiz0