Menu

Individual skill

ai-visibility-prompt-research

0upvotes

Use this skill when you need to build the set of monitoring prompts for tracking a brand's visibility inside AI assistants (ChatGPT, Gemini, Perplexity, Copilot, AI overviews) — the questions a real buyer would ask where you want the brand to show up. Trigger phrases: "run prompt research", "generate monitoring prompts", "build a prompt set to upload to our AI-visibility platform". It runs as an interactive research session that deliberately holds the brand until the very end and anchors instead on the category, the competitors, and the personas' real language mined from keyword research, open-web discussion, and first-party sales calls. Produces one upload-ready file of non-branded category prompts plus an isolated branded set, each tagged with topic, awareness stage, persona, region/language, target engines, and honest provenance.

skills/elad-hefetz/ai-visibility-prompt-research/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AI visibility prompt research

A monitoring prompt set decides what you can even see. Anchor it on the brand's own marketing copy and you measure prompts nobody searches; anchor it on real market demand and you measure whether the brand wins the questions buyers actually ask an assistant. The whole discipline is holding the brand back until the end so the research stays grounded in the market.

## The play

1. **Frame — no brand yet.** Collect the category (plain description, no brand name), the named competitor set, the target regions and their languages, and which assistants you'll monitor. Say up front that you're withholding the brand on purpose.
2. **Harvest category language, brand last.** Pull real buyer phrasing from three wells: keyword and category terminology (ask for any existing keyword or targeting file, then expand from the open web); real questions and pain points mined from communities, forums, Q&A, and "alternatives / best-of" comparison content; and — asked *after* the open-web pass — first-party sales-call and pre-sales transcripts, the highest-signal source. Tag every item with honest provenance. (See `references/open-web-sourcing.md`.)
3. **Synthesize personas and the non-branded prompt set.** Merge all signals into 4–7 personas with their pain points and the solutions they seek, in category terms. Map each to an awareness stage, weighting consideration and decision over pure curiosity. Cluster into a handful of topics. Write each prompt the way a real buyer asks an assistant — a genuine question, not a keyword string — in the target region's language (translate, don't just localize).
4. **Brand pass — last, and isolated.** Only now introduce the brand. Add competitive comparisons, "alternatives to", pricing, and fit questions as their own dedicated branded topic, flagged branded, kept separate from the category topics.
5. **Assemble, validate, hand off.** Build one file to your platform's importer contract, validate it (valid enums, one language per row matching its regions, no duplicates, sane per-topic and per-engine spread), show the distributions, and hand it to the user to upload. Never auto-import. (See `references/prompt-file-contract.md`.)

## What good looks like
Back to top