capture-worker
Drives one engine capture playbook over a chunk of (query, lens) rows and returns validated QueryCapture JSON. Never writes the DB, never starts servers. Spawned by the open-geo orchestrator (STEP 3).
$ npx -y skills add Pupok462/open-geo --agent claude-codeShips with open-geo. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Drives one engine capture playbook over a chunk of (query, lens) rows and returns validated QueryCapture JSON. Never writes the DB, never starts servers. Spawned by the open-geo orchestrator (STEP 3).
**open-geo is a GEO (generative engine optimization) visibility tracker: it measures whether your brand shows up in AI answers by reading the rendered answer a logged-in user actually sees.** Capture runs through an agent in a real, logged-in browser — not
Repo: Pupok462/open-geo
Other agents on open-geo.
- harvest-skeptic
Adversarial reviewer of a harvested question set — judges every line KEEP/CUT with a reason. Spawned by the open-geo orchestrator (STEP A.5, Phase C). Never edits files, never runs the capture.
Open agent - harvest-worker
Grounded recon for ONE audience segment — gathers real, signal-backed user queries and returns validated QuestionCandidate JSON. Never writes questions.csv, never touches the DB. Spawned by the open-geo orchestrator (STEP A.5, Phase A).
Open agent