Agent skill
geo-query-finder
Find which ChatGPT search queries mention a given brand.
Filed under Content and SEO.
From OpenClaudia/openclaudia-skills · 61 skills · 664 · pushed 2026-08-25
What it does when it runs
Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand. Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- DATAFORSEO_PASSWORD
- OPENAI_API_KEY
- Hosts it reaches
- api.dataforseo.com
- api.openai.com
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- shell
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/OpenClaudia/openclaudia-skills.git /tmp/openclaudia-skills git -C /tmp/openclaudia-skills sparse-checkout set "skills/geo-query-finder" mkdir -p ~/.claude/skills/geo-query-finder cp -R "/tmp/openclaudia-skills/skills/geo-query-finder/." ~/.claude/skills/geo-query-finder/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
Before you install: this skill will not complete its job on a bare agent. It needs DATAFORSEO_PASSWORD, OPENAI_API_KEY, which you have to obtain separately.
The skill
Source on GitHub ↗Reproduced in full from OpenClaudia/openclaudia-skills/blob/221b37d7ab95c14d5343c7b24fd9f9367a3fb400/skills/geo-query-finder/SKILL.md, which is licensed MIT (repository). 808 words, 18 headings.
GEO Query Finder
Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand.
Trigger
Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".
Usage
/geo-query-finder <brand_name> [--industry <industry>] [--features <feature1,feature2,...>] [--queries <custom_query1;custom_query2;...>]
Examples:
/geo-query-finder "Acme Corp"— auto-researches the brand and generates queries/geo-query-finder "Acme Corp" --industry "smart TV OS" --features "white-label,voice-control,OEM licensing"/geo-query-finder "Acme Corp" --queries "best regulatory AI;eCTD validation tool;pharma compliance software"
How It Works
Step 0: Pull pre-indexed LLM mentions (DataForSEO) — do this FIRST
Before generating speculative queries, check if DataForSEO already has indexed mentions for the brand's domain. If it does, you get ground-truth queries with search volume in one call instead of burning OpenAI dollars guessing.
Auth via DATAFORSEO_LOGIN / DATAFORSEO_PASSWORD environment variables.
AUTH=$(printf '%s' "$DATAFORSEO_LOGIN:$DATAFORSEO_PASSWORD" | base64)
# Google AI Overview citations
curl -s -X POST "https://api.dataforseo.com/v3/ai_optimization/llm_mentions/search/live" \
-H "Authorization: Basic $AUTH" -H "Content-Type: application/json" \
-d '[{"target":[{"domain":"<DOMAIN>","search_filter":"include","include_subdomains":true}],"platform":"google","limit":700}]'
# ChatGPT citations (substitute "platform":"chat_gpt")
Critical flags:
"include_subdomains": true— without it, apex domains return 0 results (www.X treated as a different domain).- Omit
location_codeto get global results; add"location_code": 2840only to scope to US. platformoptions:"google"(AI Overview),"chat_gpt". Perplexity is NOT supported via this dataset.
Extract from each items[]:
question— the real search query where the brand was citedai_search_volume— monthly AI search volume (use to prioritize)sources[]— entries withdomainmatching the brand have the exact cited URLlocation_code,language_code,model_name— for geo/locale breakdownanswer— the LLM answer text (for context)
Decision rule:
- If ≥20 queries returned → skip Steps 1–4 entirely; report these as ground-truth mentions and focus Step 5 on gap analysis (sort by volume, find URL-section winners like
/guides/vs/tools/). - If <20 queries → use them as seed input for Step 2 (generate variations of the query themes DataForSEO already confirmed), then run Steps 3–4 only on the gaps.
- If 0 queries → the domain has no AI citations; proceed with the original Steps 1–5 (speculative testing) as fallback.
Step 1: Research the Brand
If no --industry or --features provided, use web search to understand:
- What the brand does / what industry it's in
- Key differentiators vs competitors
- Unique features that competitors DON'T have
Step 2: Generate Long-Tail Queries
Generate 15-20 long-tail queries across these categories:
- Feature-specific (unique capabilities only this brand has)
- B2B/decision-maker (queries from buyers, not consumers)
- Problem-solving ("how to X without Y")
- Comparison/alternative ("alternative to [dominant player]")
- Use-case specific (niche scenarios where the brand excels)
Avoid generic queries where dominant players will always win.
Step 3: Query ChatGPT via OpenAI Search API
Use OpenAI's gpt-4o-search-preview model with web search enabled:
OPENAI_API_KEY from environment variable
import json, os, urllib.request, ssl
OPENAI_API_KEY = os.environ["OPENAI_API_KEY"]
data = json.dumps({
"model": "gpt-4o-search-preview",
"web_search_options": {"search_context_size": "medium"},
"messages": [{"role": "user", "content": "<query>"}],
"max_tokens": 1000
}).encode()
req = urllib.request.Request(
"https://api.openai.com/v1/chat/completions",
data=data,
headers={
"Authorization": f"Bearer {OPENAI_API_KEY}",
"Content-Type": "application/json"
}
)
resp = urllib.request.urlopen(req, context=ssl.create_default_context(), timeout=45)
result = json.loads(resp.read())
answer = result["choices"][0]["message"]["content"]
Step 4: Check Mentions
For each query, check if the brand name (or known aliases) appears in ChatGPT's response:
- Check case-insensitive match
- Check variations (with/without spaces, dots, hyphens)
- If mentioned, extract the surrounding context (200 chars around the mention)
- Note the position (is it #1 recommended? listed among many? mentioned in passing?)
Step 5: Report Results
Output a summary table:
## GEO Query Finder Results: [Brand Name]
### Mentioned (X/N queries)
| Query | Position | Context |
|-------|----------|---------|
| ... | #1 | "Brand is the leading..." |
### Not Mentioned (Y/N queries)
| Query | What ChatGPT Recommended Instead |
|-------|----------------------------------|
| ... | Competitor A, Competitor B |
### Recommendations
- Queries where brand is ALREADY mentioned: create more authoritative content to maintain/improve position
- Queries where brand is NOT mentioned but SHOULD be: these are content gaps — create targeted pages
- Queries to AVOID: too generic, dominated by big players, not worth the effort
Rate Limiting
- Run queries sequentially with 1-2 second delays to avoid rate limits
- Each query costs ~$0.01 via OpenAI API
- Default: 15-20 queries per run (~$0.15-0.20 per run)
Notes
- Results reflect ChatGPT with web search enabled (grounded in real-time web results)
- Results may vary slightly between runs due to search freshness
- This tests ChatGPT specifically — Gemini and Copilot may give different results
- For ongoing monitoring, consider scheduling periodic runs to track visibility changes over time
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- create-geo-charts by onvoyage-ai · 1,291
- geo-content-planning by onvoyage-ai · 1,291
- geo-content-research by onvoyage-ai · 1,291
- improve-aeo-geo by onvoyage-ai · 1,291
- write-seo-geo-content by onvoyage-ai · 1,291
- aeo-geo-optimizer by thatrebeccarae · 119
- wasted-spend-finder by thatrebeccarae · 119
- trade-show-contact-finder by LensmorOfficial · 48
Need help setting it up?
This page tells you what geo-query-finder does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.