Discover evidence-aware GEO questions, query rewrites, intent clusters, and prioritized content opportunities from a structured brief. Use for AI search intent mining, question or keyword expansion, query research, FAQ discovery, 拓词, and GEO topic discovery in Chinese or English.
Resources
6Install
npx skillscat add yaojingang/geohub/geo-discover Install via the SkillsCat registry.
We need to produce a 2-3 sentence plain-text summary, objective, factual, no marketing language, no superlatives, no calls to action. At most 60 words. Should explain what the skill does, what problem it solves, when to use it. From description: skill discovers evidence-aware GEO questions, query rewrites, intent clusters, prioritized content opportunities from a structured brief. Used for AI search intent mining, question/keyword expansion, query research, FAQ discovery, 拓词, GEO topic discovery in Chinese or English.
GEO Discover
Workflow
- Read
references/discovery-method.md; readreferences/discovery-method-v2.mdwhen requesting a non-legacy execution mode. - Prepare a protocol
1.0.0file-backed GEO brief. - Run
python3 scripts/run_discover.py --input <brief.json> --output <runs-root> --execution-mode <legacy|deterministic|research|provider>. Legacy remains the compatibility default. - Inspect
quality-report.jsonandrun-lineage.json; surface all warnings and failed checks. - Deliver the Artifact Bus directory as the output contract.
Output contract
Treat the output argument as the runs root. Produce <runs-root>/<run-id>/input/geo-brief.json, run-manifest.json, run-lineage.json, evidence-ledger.json, query-map.json, opportunity-map.json, and quality-report.json. Return the actual <runs-root>/<run-id> directory.
Boundaries
Legacy and deterministic modes are offline and file-backed. Research mode consumes only approved evidence already present in the brief. Provider mode needs an explicit runtime adapter; the packaged CLI has no adapter and degrades to deterministic generation with a recorded failure. Discovery records missing evidence and never invents platform responses, volume, ranking, conversion, competitor, or customer data. Diagnosis and content generation remain separate Registry stages.