seo-geo-report-engine: Skill for Claude Code

skill-navigator

Pure orchestration. The user has a goal but doesn't know which capability to reach for — or the goal spans several. This skill reads the live catalog, picks the shortest correct path through it, and hands back an ordered plan the user (or the next agent) can run step by step. It does no MCP calls and produces no analysis — it routes. The CLAUDE.md routing table is a starting hint, but the inventory on disk is the source of truth: a skill exists only if its folder does.

Methodology (PERCEIVE → ANALYZE → VALIDATE → ACT)

PERCEIVE — read the live inventory. Never hardcode the skill/command list; the catalog grows. Resolve the project if one is implied (./bin/mkt config show --project <client>), then:

ls -1 skills/                                   # every available skill
ls -1 commands/                                 # every /command workflow
for f in skills/*/SKILL.md; do printf '\n=== %s ===\n' "$f"; sed -n '1,12p' "$f"; done
sed -n '1,40p' commands/*.md                    # what each /command orchestrates

Read the description frontmatter of candidate skills and the intro of candidate commands so matching is grounded in what each actually does — not in this file's memory of them. If a client is named, read projects/<client>/client.yml and ls projects/<client>/research/ to see which inputs/artifacts already exist (so the plan starts where the client actually is).

ANALYZE — match intent → ordered path. Decompose the ask into intents, then map each to the inventory:

• Primary skill — the one capability that most directly satisfies the core ask.
• Up to 2 supporting skills — what the primary needs upstream (e.g. keyword-research before content-brief) or what naturally follows downstream.
• A /command if one fits — commands orchestrate multiple skills into a full deliverable (e.g. /discovery-audit, /growth-proposal). Prefer a command over hand-chaining skills when it already encodes the same path.
• Order by dependency, not by preference: a step that consumes research/keywords.csv comes after the step that writes it. GTM skills (positioning-messaging, customer-research) feed SEO/content skills — sequence them first when the brand language doesn't exist yet.