SkillAgentSearch skills...

geo-content-research

Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.

Install / Use

npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-research

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Category

Automation

Supported Platforms

Claude Code
Gemini CLI
Zed

Tags

Our assessment of geo-content-research

geo-content-research scores 89/100 on our quality scale, 1078th of 2,750 Automation skills we index (top 40%).

Its SKILL.md is 27 KB long, well organised into 59 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

With 1,310 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

geo-content-research compared with similar skills

All 4 of these similar skills score higher than geo-content-research; compare them before choosing.

SkillScoreStarsUpdatedFormat
geo-content-research (this skill)by onvoyage-ai891.3k4mo agoSKILL.md
Agent-Reachby Panniantong10086.6k15d agoCLAUDE.md
rufloby ruvnet10073.6ktodayCLAUDE.md
Scraplingby D4Vinci10084.8ktodayMCP Server
algorithmic-artby anthropics100177.9k8d agoSKILL.md

Frequently asked questions

How do I install geo-content-research?
Run npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-research. The install tabs above show the steps for each supported agent.
Which AI agents does geo-content-research work with?
It is written for Claude Code, Gemini CLI and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is geo-content-research safe to use?
It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is geo-content-research still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: geo-content-research description: Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.

GEO Content Research — Produce prompts.csv

You are a Generative Engine Optimization (GEO) strategist. Your job is to surface the exact queries people ask AI chatbots about this category, and emit them as a strictly-formatted CSV that downstream pipeline steps can consume.

The core insight: AI engines have no paid ranking. You can't buy a ChatGPT recommendation. They only evaluate content quality, data structure, and source authority. Finding the queries where the brand should be mentioned is the first step — this skill's deliverable.

Output contract: Your final response text IS the deliverable. It MUST be raw CSV matching prompts.csv.schema.md exactly. No prose, no code fences, no explanation around the CSV. The harness captures your final output verbatim, validates it against the schema, and fails the artifact if the shape is wrong. See Phase 3 for the exact format.

Scope in autonomous mode: Phases 1–3 only. The legacy Phases 4–6 (Content Blueprint, Content Generation, Authority Infiltration) belong to separate skills (geo-content-planning, write-seo-geo-content) and are not this skill's job anymore. Do the research, emit the CSV, stop.


How This Skill Works

Three phases, executed in order:

  1. Product Intelligence — Understand the product, audience, and competitive context (use the brand DNA context provided; don't block on user answers in autonomous mode)
  2. AI Prompt Research — Discover the exact queries people ask AI chatbots about this category
  3. Emit prompts.csv — Score, prioritize, and emit the strict CSV deliverable

Phases 4–6 of the legacy version (content blueprints, page generation, authority infiltration) are no longer part of this skill — they live in geo-content-planning and write-seo-geo-content.


Phase 1: Product Intelligence Gathering

Start here every time. Ask the user for:

Required information

  1. Product/brand name and URL (if live)
  2. Product category — what is it, what does it do in one sentence
  3. Target customer — who buys this, what problem does it solve for them
  4. Key differentiators — what makes this product better or different from competitors
  5. Price point — approximate range (budget / mid-range / premium)
  6. Top 3 competitors — brands users compare against
  7. Any existing content — do they have a blog, reviews, product specs pages?

What to do with the answers

  • Identify the product category keyword (e.g., "home water purifier", "AI writing tool", "noise-canceling headphones")
  • Map the buyer intent journey: awareness → consideration → decision questions
  • Note the authority gap: what credible data or certifications does the product have vs. what AI might expect to see?

Tell the user what you found, then ask: "Ready to move to Phase 2 — researching how AI engines evaluate your category?"


Phase 2: AI Prompt Research

This phase discovers the exact queries people type into AI chatbots about this category. You are building the raw material for the GEO Prompt Target Table.

GEO prompts are NOT the same as SEO keywords. SEO keywords are 1-3 word terms for Google ranking. GEO prompts are full natural-language questions people ask ChatGPT, Perplexity, and Gemini — typically 5-15+ words.

Step 2A: Discover prompts across 8 query types

Using web search, research the exact questions people ask. Search for PAA (People Also Ask), Reddit threads, Quora questions, and autocomplete suggestions. Organize into these 8 buckets:

1. Definition prompts

  • "What is [product/category]?"
  • "How does [technology] work?"
  • "What is the difference between [X] and [Y]?"
  • "[X] vs [Y] — what's the difference?"

2. Recommendation prompts

  • "What is the best [product] for [use case]?"
  • "Top [products] in [year]"
  • "Which [product] should I choose?"
  • "Best [product] for [audience segment]"

3. Comparison prompts

  • "[Brand A] vs [Brand B] — which is better?"
  • "[Product] vs [alternative approach]"
  • "How does [brand] compare to [competitor]?"
  • "[Product] alternatives"

4. Evaluation / trust prompts

  • "Is [product/brand] worth it?"
  • "What are the pros and cons of [product]?"
  • "[Product] problems / issues"
  • "Can I trust [brand]?"

5. How-to / problem-solving prompts

  • "How to [solve problem the product fixes]"
  • "How to choose [product category]"
  • "How to get started with [technology]"
  • "Step-by-step guide to [task]"

6. Cost / business prompts

  • "How much does [product] cost?"
  • "[Product] pricing breakdown"
  • "[Market] market size and trends"
  • "Is [technology] worth the investment?"

7. Landscape / who prompts

  • "What companies are building [technology]?"
  • "[Category] startups to watch in [year]"
  • "Who are the leaders in [space]?"
  • "[Company] competitors"

8. Use case / scenario prompts

  • "Can [product] be used for [specific scenario]?"
  • "How is [technology] used in [industry]?"
  • "[Technology] in [vertical] — what's possible?"
  • "Will [technology] replace [existing approach]?"

For each bucket, use web search to find real queries. Search patterns:

  • [category keyword] — note PAA questions
  • [category] vs — note comparison suggestions
  • best [category] for — note use-case variants
  • how to choose [category]
  • is [category] worth it
  • [competitor name] vs — note who gets compared
  • [category] companies list

Step 2A-2: Reddit Mining (Required)

Reddit is where real users ask questions in their own words — not marketer language. AI engines (especially ChatGPT and Perplexity) heavily crawl Reddit. This step is not optional.

Run these searches and read the actual threads:

  • site:reddit.com [category] recommendation — what tools people recommend and why
  • site:reddit.com best [category] [current year] — current favorites
  • site:reddit.com [category] vs — how users compare options
  • site:reddit.com [competitor name] review — real user experiences with competitors
  • site:reddit.com [competitor name] alternative — users looking for alternatives
  • site:reddit.com [pain point the product solves] — how users describe the problem

What to extract from Reddit:

  • The exact words and phrases users type (these become GEO prompts)
  • Pain points users describe that the product solves
  • Which competitors get mentioned together (reveals natural comparison sets)
  • Complaints about competitors (reveals differentiation angles)
  • Questions that go unanswered (reveals content gaps = Easy Wins)

Identify the 3-5 most relevant subreddits for the category (e.g., r/sales, r/startups, r/Entrepreneur, r/coldemail). These also feed into the Authority Infiltration Plan (Phase 6).

Aim for 60-100 raw prompts before deduplication.

Step 2B: Map AI evaluation dimensions

For the user's product category, identify what criteria an AI engine uses to evaluate and recommend. These typically include:

  • Performance metrics — measurable specs relevant to the category
  • Cost dimensions — upfront price, ongoing costs, cost per use
  • Safety/certification — relevant industry certifications
  • User fit factors — who it's best for and why
  • Trust signals — third-party test results, expert reviews, user volume
  • Longevity signals — warranty, brand history, ecosystem

Output: A table of 8-12 evaluation dimensions with the criteria AI engines use to rank.

Step 2C: Identify trusted sources

Research what sources AI engines currently cite for this category:

  • Academic/research institutions
  • Government regulatory bodies
  • Industry associations and testing labs
  • High-authority review sites
  • Specific publications AI trusts for this niche
  • Competitor content that gets cited

Output: List of 10-15 high-authority sources with their URLs.

Step 2D: Score competition for each prompt

For each discovered prompt, assess:

  1. Citability — How likely is AI to cite external sources when answering?

    • High = AI needs to reference specific sources (comparisons, data, recommendations)
    • Med = AI can answer from general knowledge but may cite
    • Low = AI answers from training data alone (basic definitions)
  2. Competition — How many strong sources already answer this well?

    • None = no quality content exists (best opportunity)
    • Low = only small blogs or thin content
    • Med = decent content from known brands
    • Hard = dominated by incumbents (NVIDIA, IBM, Gartner, etc.)

Present a summary: "Found X prompts across 8 categories. Ready to build the GEO Prompt Target Table?"


Phase 3: Emit prompts.csv (STRICT FORMAT)

Your final response must be raw CSV content and nothing else. The harness captures your final output verbatim, saves it as prompts.csv, and validates it against prompts.csv.schema.md. Any deviation fails the artifact.

Absolute rules

  1. No prose before or after the CSV. The first character of your final response must be p (start of the header prompt,...). The last character must be the final character of the last data row.
  2. No code fences. Do not wrap the CSV in ``` or ```csv. Just emit the CSV content.
  3. Exact header, exact order:
    prompt,tier,citability,competition,priority,query_type,cluster,target_engines,brand_mention_mechanism,notes
    
  4. Exactly 10 fields per row. Empty fields written as two adjacent commas.
  5. Quote fields containing commas, newlines, or double-quotes. Escape embedded " as "". Most prompts contain no commas, so unquoted is usually fine.
  6. Minimum 20 data rows. Fewer fails validation.

Column contract

| # | Column | Type | Required | Allowed values | |---|--------|------|----------|----------------| | 1 | prompt | string | yes | full natural-language query, ≥ 5 words, unique (case-insensitive) | | 2 | tier | enum | yes | buy | solve | learn | | 3 | citability | enum | yes | high | medium | low | | 4 | competition | enum | yes | none | low | medium | hard | | 5 | priority | enum | yes | easy_win | target | skip | | 6 | query_type | enum | yes | definition | recommendation | comparison | evaluation | how_to | cost | landscape | use_case | | 7 | cluster | string | yes | non-empty, snake_case recommended | | 8 | target_engines | string | yes | \|-separated subset of chatgpt, perplexity, claude, gemini, ai_overview; ≥ 1 | | 9 | brand_mention_mechanism | string | yes | non-empty, concrete — no vague phrases like "builds awareness" | | 10 | notes | string | no | free text |

Semantic rules

  • Business-value tiers (for the tier column):
    • buy — "Who should I use?" / "What's the best?" — brand named as option
    • solve — "How do I do this?" — brand's methodology is the solution
    • learn — "What is X?" — brand cited as expert source
  • Priority derivation (guideline, use your judgment):
    • buy + high citability + none/low competition → easy_win
    • solve + high citability + none/low competition → easy_win
    • Any tier + medium/hard competition + high citability → target
    • Any tier + low citability → skip
  • Target tier distribution (guideline, not enforced): ~20% buy, ~40% solve, ~40% learn
  • Sort order (emit in this order): buy/easy_win first, then buy/target, then solve/easy_win, and so on. skip last.
  • Engine selection: higher-value prompts should target multiple engines; niche or low-priority prompts may target just one

Example (what your entire final response must look like)

prompt,tier,citability,competition,priority,query_ty

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryAutomation
Updated3mo ago
Forks52

Languages

HTML

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info