agentleFS
howseen-aihowseen-ai/howseen-geo-skills/buyer-questions/SKILL.md

buyer-questions

Skill1 starsChanged 57 days agoMITView on GitHub

Surface the real questions a company's buyers ask AI about its category, mined from where people actually ask them. Use this whenever the user wants to know what their customers ask ChatGPT/Perplexity, what prompts they should be visible for, what content to write, or what questions their category gets. Give Claude a brand, product, or industry — it mines real questions from public discussion and returns a prioritized, trackable set.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. codebywater/WB-OZON-AI-TEAM★ 2same name
    2. elementera/aeo-ai-search-visibility★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only include questions you actually found in real sources.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

buyer-questions

You can't optimize for AI answers until you know the questions being asked. This skill mines the real questions buyers ask about a category — the ones worth being the recommended answer to.

Steps

  1. Frame the category. From the brand/product/industry given, define what buyers are actually trying to do (e.g. "choose a tool for X", "understand whether Y is worth it", "compare A vs B").
  2. Mine real sources with web search. Look where people ask out loud: Reddit threads, forums, Quora, Hacker News, "people also ask", comparison and review pages, community discussions. Pull the questions people actually phrase — verbatim where possible — not made-up ones. Cite the source for each cluster so the list is grounded, not invented.
  3. Cluster and classify the questions by buyer stage:
    • Problem-aware ("why does X keep happening")
    • Solution-aware ("what's the best way to do X")
    • Comparison ("A vs B", "alternatives to A")
    • Decision ("is A worth it", "does A do Y")
  4. Turn each cluster into a trackable prompt — the way a buyer would actually type it into ChatGPT ("what's the best tool for X for a small team"). These are the prompts to be visible for.
  5. Prioritize: which questions are highest-intent (closest to a buying decision) and highest-volume. Mark the top ones.

Output format

## Buyer questions — [category]

### Comparison / decision (highest intent)
- "[real question]"  — source: [where], trackable prompt: "[how a buyer types it]"

### Solution-aware
- "[real question]"  — source: [...]

### Problem-aware
- "[real question]"  — source: [...]

### Track these first
1. "[prompt]" — why: [intent + volume]

Honest note

Only include questions you actually found in real sources. If a cluster is thin, say the signal is thin rather than padding it with plausible-sounding invented questions.


Built by Raphaël Aubry, founder of Howseen (https://howseen.ai). This gives you the questions. Whether AI recommends you as the answer to them — today and as it shifts — is what Howseen tracks, prompt by prompt. → https://howseen.ai

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.