Geo Agent Skill

Route GEO and generative engine optimization requests to an available GEOHub capability. Use for broad GEO requests, GEOHub workflow selection, capability checks, or requests spanning discovery, brand/site/page diagnosis, content, strategy, knowledge, publishing, and measurement.

3k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

101

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/yaojingang/GEOHub --skill geo

What comes with it

10 171 bytes besides the instruction

agents/interface.yaml

evals/output/cases.jsonl

evals/semantic_config.json

evals/trigger_cases.json

manifest.json

references/routing-contract.md

reports/output_quality_scorecard.md

reports/skill-ir.json

reports/trust-report.md

scripts/run_route.py

The instruction itself

4 sections, as written by the author

GEOHub

Workflow

Read references/routing-contract.md and the suite resolver contract at ../RESOLVER.md.
Run the deterministic python3 scripts/run_route.py --text "<request>" wrapper or python -m geo_seo_hub route --text "<request>".
Dispatch only when the JSON result has 'runnable: true' and a non-null 'entry'.
For 'pending-implementation' or 'planned', return the registry status and suggested available route exactly as reported.

Output contract

Return the selected skill ID, lifecycle status, runnable flag, reason, entry path, suggestion, and optional stable workflow DAG. Preserve uncertainty when two routes have the same score.

Boundaries

This skill selects capabilities. It does not generate discovery artifacts or simulate unavailable stages.

How to use it

Copy the folder

Take yaojingang/geo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.