
Diagnose AI Visibility
Find out why AI search engines leave your brand out of an answer, and pick the one fix...
Install
npx skills add ParadevAI/Paradev --skill diagnose-ai-visibility -g -a claude-code -y- Repository
- ParadevAI/Paradev15.8k
- Category
- Marketing
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 721 tokens
- Runs scripts
- No, instructions only
What it does
Find out why AI search engines leave your brand out of an answer, and pick the one fix that matches the cause, read the answers and the sources they cite, map the question to your own page, then decide if the page is broken, missing, weak, or outweighed by third-party sources. Use when the user asks why ChatGPT, Gemini, Perplexity or Google AI Overviews do not mention them, which prompts they lose, what content to write next, or how to improve AI visibility.
Diagnose before you create
A lost prompt has one of four causes, and each cause has a different fix. A new page is the right fix for only one of them. Find the cause first.
1. Pick the prompts to diagnose
Run list_projects, then list_brands to find the brand with is_own: true.
If the user named no prompt, run get_brand_report for the last 14 days,
broken down by prompt, and take the 10 non-branded prompts with the lowest
visibility. Skip branded prompts: they measure recognition, not demand.
2. Read what the engines actually answered
For each prompt, run list_chats for the same window and get_chat on two or
three of them, from different engines. Record:
- the brands the answer named, and their order
- the
sourcesit retrieved and thelinksit wrote into its text - the
queriesit searched: these are the words the engine uses for the topic
list_search_queries for the prompt shows the same searches across all chats.
3. Decide the cause, in this order
Stop at the first one that applies.
- Technical. Find your page that answers this question. Check that it
loads, is in the sitemap, and is not blocked in
robots.txt.get_agent_visitsgrouped byrequest_pathandresponse_statusshows if AI crawlers reach it and what status they get (it needs connected access logs). A failure here is the cause. - Missing. No page of yours answers this question directly. A page that mentions the topic in passing does not count.
- Weak. Your page exists and crawlers reach it, but it does not answer the
question in its first screen, has no direct comparison or steps, or has
facts that are out of date.
get_url_reportshows if engines retrieve it but do not cite it. Name the exact gap. - Third-party. Your page is fine, but the answer is built from other
sites. Run
get_url_contenton the top cited sources to see what each one says about you: absent, wrong, out of date, or fair.
