← NimbleCONTENT HISTORY

Update to Nimble

Snapshot Sep 30, 2026 · 22:54 UTC · version 1.7.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "seo-intel",
  "description": "SEO intelligence toolkit covering the full lifecycle via live web data:\nkeyword research, rank tracking, site audits, content gap analysis,\ncompetitor keyword reverse-engineering, AI visibility across five platforms\n(ChatGPT, Perplexity, Google AI, Gemini, Grok), and GitHub repo SEO.\nCrawls real sites and SERPs via Nimble CLI — no fabricated metrics.\n\nTriggers: \"SEO\", \"keywords\", \"rank tracker\", \"site audit\", \"content gap\",\n\"competitor keywords\", \"AI visibility\", \"GitHub SEO\", \"SERP analysis\",\n\"keyword research\", \"technical SEO\", \"keyword difficulty\", \"topic\nclusters\", \"ranking delta\", \"on-page SEO\", \"AI citation audit\".\n\nDo NOT use for competitor business signals — use `competitor-intel`\ninstead. Do NOT use for competitor messaging — use\n`competitor-positioning` instead. Do NOT use for general web scraping\n— use `nimble-web-expert` instead.\n",
  "included_files": [
    {
      "relative_path": "references/ai-platform-profiles.md",
      "size_in_bytes": 11542
    },
    {
      "relative_path": "references/ai-visibility-agent-prompt.md",
      "size_in_bytes": 6300
    },
    {
      "relative_path": "references/audit-agent-prompt.md",
      "size_in_bytes": 3884
    },
    {
      "relative_path": "references/content-gap-agent-prompt.md",
      "size_in_bytes": 5783
    },
    {
      "relative_path": "references/github-seo-checks.md",
      "size_in_bytes": 12044
    },
    {
      "relative_path": "references/keyword-research-agent-prompt.md",
      "size_in_bytes": 2990
    },
    {
      "relative_path": "references/memory-and-distribution.md",
      "size_in_bytes": 22058
    },
    {
      "relative_path": "references/nimble-playbook.md",
      "size_in_bytes": 37015
    },
    {
      "relative_path": "references/profile-and-onboarding.md",
      "size_in_bytes": 9344
    },
    {
      "relative_path": "references/seo-audit-checks.md",
      "size_in_bytes": 15437
    },
    {
      "relative_path": "references/seo-extraction-prompt.md",
      "size_in_bytes": 6923
    },
    {
      "relative_path": "references/serp-query-patterns.md",
      "size_in_bytes": 6551
    },
    {
      "relative_path": "references/wf-ai-visibility.md",
      "size_in_bytes": 20160
    },
    {
      "relative_path": "references/wf-competitor-keywords.md",
      "size_in_bytes": 19283
    },
    {
      "relative_path": "references/wf-content-gap.md",
      "size_in_bytes": 18407
    },
    {
      "relative_path": "references/wf-github-seo.md",
      "size_in_bytes": 16088
    },
    {
      "relative_path": "references/wf-keyword-research.md",
      "size_in_bytes": 18701
    },
    {
      "relative_path": "references/wf-rank-tracker.md",
      "size_in_bytes": 15237
    },
    {
      "relative_path": "references/wf-site-audit.md",
      "size_in_bytes": 15167
    }
  ],
  "skill_md_contents": "---\nname: seo-intel\ndescription: |\n  SEO intelligence toolkit covering the full lifecycle via live web data:\n  keyword research, rank tracking, site audits, content gap analysis,\n  competitor keyword reverse-engineering, AI visibility across five platforms\n  (ChatGPT, Perplexity, Google AI, Gemini, Grok), and GitHub repo SEO.\n  Crawls real sites and SERPs via Nimble CLI — no fabricated metrics.\n\n  Triggers: \"SEO\", \"keywords\", \"rank tracker\", \"site audit\", \"content gap\",\n  \"competitor keywords\", \"AI visibility\", \"GitHub SEO\", \"SERP analysis\",\n  \"keyword research\", \"technical SEO\", \"keyword difficulty\", \"topic\n  clusters\", \"ranking delta\", \"on-page SEO\", \"AI citation audit\".\n\n  Do NOT use for competitor business signals — use `competitor-intel`\n  instead. Do NOT use for competitor messaging — use\n  `competitor-positioning` instead. Do NOT use for general web scraping\n  — use `nimble-web-expert` instead.\nallowed-tools:\n  - Bash(nimble:*)\n  - Bash(date:*)\n  - Bash(cat:*)\n  - Bash(mkdir:*)\n  - Bash(python3:*)\n  - Bash(echo:*)\n  - Bash(jq:*)\n  - Bash(ls:*)\n  - Bash(gh:*)\n  - Read\n  - Write\n  - Edit\n  - Glob\n  - Grep\n  - Agent\n  - AskUserQuestion\nmetadata:\n  author: Nimbleway\n  version: 1.6.1\n  category: seo\n---\n\n# SEO Intelligence Toolkit\n\nAll-in-one SEO intelligence: keyword discovery, rank tracking, technical audits,\ncontent gaps, competitor analysis, AI visibility, and GitHub SEO.\n\nUser request: $ARGUMENTS\n\n**Before running any commands**, read `references/nimble-playbook.md` for Claude Code\nconstraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).\nTag all `nimble` CLI calls: `nimble --client-source nimble-agent-skills <subcommand>`. MCP requests are attributed at the transport level — see `references/nimble-playbook.md`.\n\n---\n\n## Workflow Router\n\nDetect the user's SEO intent from `$ARGUMENTS` and route to the appropriate\nworkflow. If the intent is ambiguous or generic (\"help me with SEO\"), ask which\nworkflow to run.\n\n### Available Workflows\n\n| Workflow | Triggers | Reference |\n|----------|----------|-----------|\n| **Keyword Research** | keyword opportunities, topic clusters, difficulty, what to rank for | `references/wf-keyword-research.md` |\n| **Rank Tracker** | track rankings, keyword positions, ranking delta, position check | `references/wf-rank-tracker.md` |\n| **Site Audit** | SEO audit, technical SEO, meta tags, schema, crawl for issues, CWV | `references/wf-site-audit.md` |\n| **Content Gap** | content gap, keyword gap, compare coverage, missing topics | `references/wf-content-gap.md` |\n| **Competitor Keywords** | competitor keywords, reverse-engineer SEO, competitor title tags | `references/wf-competitor-keywords.md` |\n| **AI Visibility** | AI visibility, ChatGPT presence, Perplexity, AI Overview, GEO | `references/wf-ai-visibility.md` |\n| **GitHub SEO** | github seo, repo discoverability, optimize readme, repo audit | `references/wf-github-seo.md` |\n\n### Intent Detection\n\nMap the request to one workflow:\n\n- **Keywords / topics / difficulty / clusters / \"what to rank for\"** → Keyword Research\n- **Rankings / positions / tracking / delta / monitoring** → Rank Tracker\n- **Audit / crawl / technical / meta / schema / links / CWV** → Site Audit\n- **Gap / missing topics / coverage comparison / \"what should I write\"** → Content Gap\n- **Competitor site crawl / reverse-engineer / on-page at scale** → Competitor Keywords\n- **AI visibility / ChatGPT / Perplexity / AI Overview / GEO** → AI Visibility\n- **GitHub / repo / README / discoverability** → GitHub SEO\n\nIf unclear, present the options with AskUserQuestion:\n\n> Which SEO workflow should I run?\n> - **Keyword Research** — discover keyword opportunities and topic clusters\n> - **Rank Tracker** — check and track keyword positions over time\n> - **Site Audit** — full technical SEO crawl with JS rendering\n> - **Content Gap** — compare content coverage against competitors\n> - **Competitor Keywords** — reverse-engineer competitor on-page SEO at scale\n> - **AI Visibility** — measure brand presence across 5 AI platforms\n> - **GitHub SEO** — audit repository discoverability and README quality\n\n### Execution\n\nOnce a workflow is identified:\n\n1. **Read** the corresponding `references/wf-{name}.md`\n2. **Follow** its instructions from Step 0 (Preflight) through to the output format\n3. All `references/` paths inside workflow files are relative to this skill's directory\n\n### Workflow Chaining\n\nAfter completing a workflow, suggest natural next steps using sibling workflows.\nCommon chains:\n\n- Site Audit → Keyword Research → Content Gap → Rank Tracker\n- Keyword Research → Competitor Keywords → Content Gap\n- AI Visibility → Content Gap → Keyword Research\n\nWhen chaining, read the next workflow file and continue. Context from the\nprevious run (discovered domains, keyword lists, profile data) carries forward\n— do not re-run preflight or re-ask onboarding questions.\n\n### Shared Configuration\n\nAll workflows use:\n- **Business profile + onboarding:** `references/profile-and-onboarding.md`\n- **Data persistence:** `references/memory-and-distribution.md`\n- **CLI patterns + constraints:** `references/nimble-playbook.md`\n- **AI platform agent discovery:** `references/ai-platform-profiles.md`\n"
}

SHA-256: aefb5959ae8a9155edd2834bb067d2f727e41b09d3efd3056284ce35291c6894