forked from bchanot/claude
6,416 → 4,243 chars (≈ −540 tokens/session, catalog loaded every session). Kept per BDR-014/LRN-043: 'Use when' pattern, discriminating FR+EN triggers, all 'For X → /Y' disambiguation lines. Cut: redundant trigger synonyms, header/engine enumerations, prose the model derives. find-docs excluded (ctx7-owned, regen clobbers — LRN-086); doc + geo taken instead. All ≤ ~505 chars body (BDR-014 aspirational ceiling). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016zA3Qh2Q1QpcGXzXxKeDHR
1.1 KiB
1.1 KiB
name, description, argument-hint, allowed-tools
| name | description | argument-hint | allowed-tools | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| geo | Use when a web project needs AI-search visibility audit — ChatGPT, Perplexity, Gemini, AI Overviews, Copilot… Standalone GEO; dispatches the geo-analyzer agent. Triggers: "geo", "AI search", "llms.txt", "AI crawlers", "entity SEO", "Wikidata", "generative engine optimization", "référencement IA". Combined SEO+GEO → /seo. | optional keywords/scope, e.g. "SaaS B2B content GEO" or "audit llms.txt et entity SEO" |
|
Load and follow strictly:
- $HOME/.claude/agents/geo-analyzer.md
Execute the GEO-ANALYZER agent on the following target:
$ARGUMENTS
Note on integration
If .claude/audits/SEO.md already exists, the geo-analyzer will
merge its findings into that file's §7 — Optimisation GEO / IA
section (rather than writing a separate GEO.md). This keeps a
single consolidated report when both /seo and /geo have been run.
If no .claude/audits/SEO.md exists, the agent writes .claude/audits/GEO.md (run mkdir -p .claude/audits first).