geo is the orchestrator skill of the GEO-SEO Claude toolkit. It answers /geo commands such as audit, quick, citability, crawlers, llmstxt, brands, platforms, schema, technical, content, report and report-pdf, and sends each one to a specialised sub-skill.
A full audit fetches the homepage, detects the business type (SaaS, local service, e-commerce, publisher, agency), launches five parallel subagents and combines their findings into one GEO Score from 0 to 100 with a prioritised action plan.
What You Get
- A single /geo command set covering audit, page, quick, citability, crawlers, llmstxt, brands, platforms, schema, technical, content, report and report-pdf
- A composite GEO Score from 0 to 100 built from six weighted categories
- One named output file per command, such as GEO-AUDIT-REPORT.md or GEO-CITABILITY-SCORE.md
- Business-type detection that changes the recommendations for SaaS, local, e-commerce, publisher and agency sites
- A pandoc and headless Chrome route to a styled GEO-REPORT.pdf
Common Use Cases
- Run a full AI search audit on a client website and hand over a prioritised action plan
- Take a 60-second GEO snapshot of a competitor before a pitch
- Check whether AI crawlers can reach a site and which pages are quotable
- Turn an audit markdown file into a branded PDF for a client
What Makes It Unique
Most SEO skills cover one task. This one is a router over fourteen sub-skills and five subagents, with fixed scoring weights (citability 25%, brand authority 20%, content 20%, technical 15%, schema 10%, platforms 10%) and quality gates on crawl size, timeouts and request pacing. It also reaches past audits into prospecting, proposals and monthly progress reports for agencies.
Under The Hood
The SKILL.md is a routing table and an orchestration recipe. It tells the agent to fetch pages with curl or WebFetch, read sitemap.xml, check robots.txt, delegate to five subagent files in the repository’s agents folder, and write report files (markdown, llms.txt, PDF) into the current directory. Prospect, proposal and comparison commands write into a ~/.geo-prospects folder in the home directory. The PDF route runs pandoc and a headless Google Chrome from the shell. It declares Read, Grep, Glob, Bash, WebFetch and Write tools. Quality gates cap an audit at 50 pages, 30 seconds per fetch and one second between requests.