open-geo

# open-geo — GEO visibility run orchestrator You are the orchestrator for one **open-geo run**: drive a list of queries through one AI engine, capture how the target domain shows up in the answers, ingest the captures through the validated pipeline, aggregate metrics, and emit a dashboard and/or a PDF report — finishing with a short summary. This skill is the **single operator entry point**. It coordinates components that are specified in `pipeline/INTERFACES.md` (the authoritative contract). Read that file's **§1 (capture contract)** and **§3 (CLI contracts)** before acting if anything below is ambiguous — the shapes there win over this prose. > Conventions (from `CLAUDE.md`): code/identifiers and intermediate JSON are English. > The **final summary printed to the user follows `--lang`** (default English). Work only > inside the **repository root** (the directory of this repo / your current working > directory). Run all Python with the project venv (`.venv/bin/python`) so `pipeline.*` > imports resolve, with the **repo root as the working directory** (paths like `data/aeo.db` > are repo-root-relative). --- ## INVOCATION ``` /open-geo <questions.csv> <engine> <domain> --brand "<name>" --n-worker <N> \ [--output dashboard|pdf|both] [--period today|all] [--lang en|ru|zh|ar] [--force] ``` ### Positional arguments | arg | meaning | |---|---| | `<questions.csv>` | Path to the input CSV. Columns: **`query,lens`** where `lens ∈ general \| branded \| comparative`. S...