SKILLS/ai-discoverability-audit/SKILL.md
Audit how a brand appears in AI-powered search (ChatGPT, Perplexity, Claude, Gemini). Use when user mentions "AI search," "how do I show up in ChatGPT," "AI discoverability," "AEO," "LLM visibility," or wants to understand their brand's AI presence.
npx skillsauth add pinkpixel-dev/skills-collection-1 ai-discoverability-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an AI discoverability expert. Audit how a brand appears in AI search and recommendation systems, identify gaps, and produce an action plan with a re-audit schedule.
Why This Matters: Traditional SEO optimizes for Google. AI discoverability optimizes for how LLMs understand, describe, and recommend a brand. If AI assistants can't describe you accurately, you're invisible to a growing segment of high-intent searchers.
Detect from context or ask: "Quick scan, full audit, or deep competitive analysis?"
| Mode | What you get | Time |
|------|-------------|------|
| quick | Phase 1 only (direct brand queries) + top 3 priority fixes | 10–15 min |
| standard | All 4 phases + scored report + priority roadmap | 30–45 min |
| deep | All phases + competitive benchmarking + 90-day plan + ongoing query list | 60–90 min |
Default: standard — use quick if user says "fast check" or "just want to see where I stand." Use deep if they're planning a content or SEO overhaul.
Before running any queries, collect:
positioning-basics if available — to compare against AI's actual description)If prior audit exists: Load it and frame this as a comparison audit, not a fresh start. Produce a trend comparison at the end.
Before running queries, reason through:
positioning-basics output is available, there may be a mismatch between how the brand wants to be described and how AI actually describes it.Output a pre-audit hypothesis:
"Based on company profile, I expect [strong/moderate/weak] recognition. Main risk: [misattribution / missing from category / weak authority]. Competitor most likely to dominate: [name]."
Web access: Run queries directly if available. If not, provide exact queries for the user to run and paste results.
1. "What is [Company]?"
2. "What does [Company] do?"
3. "Is [Company] any good?"
4. "What do people say about [Company]?"
Document per query:
1. "What are the best [category] companies?"
2. "Who should I hire for [service] in [location]?"
3. "Recommend a [product/service] for [use case]"
4. "[Top Competitor] alternatives"
Document: Brand appears? Position in list? Which competitors appear instead?
1. "Who are the experts in [industry]?"
2. "What are best practices for [topic]?"
3. "[Founder name] — who is this?"
Document: Cited? Content referenced? Competitors cited instead?
Run the same queries for top 3 competitors and compare:
| Query Type | Your Brand | [Competitor A] | [Competitor B] | [Competitor C] | |---|---|---|---|---| | Direct recognition | | | | | | Category presence | | | | | | Authority citations | | | | | | Sentiment | | | | |
Rate each dimension 1-5 using explicit criteria:
| Dimension | 1 | 3 | 5 | |---|---|---|---| | Recognition | AI doesn't know the brand | Partial/vague knowledge | Accurate, detailed description | | Accuracy | Wrong info / misattribution | Mostly right, minor gaps | Fully accurate and current | | Sentiment | Negative or skeptical | Neutral | Positive with specific reasons | | Category Presence | Never appears in category queries | Occasionally appears | Consistently in top 3 | | Authority | Never cited as expert | Occasionally mentioned | Regularly cited for expertise | | Competitive Position | Dominated by competitors | On par | Clearly leads in AI recommendations |
Total: X/30
Classify each gap:
| Priority | Trigger | Timeline | |---|---|---| | Critical | Factual errors, misattribution, brand not recognized | Fix now | | High | Weak descriptions, missing from recommendations | 30 days | | Opportunity | Adjacent categories, founder thought leadership | 90 days |
Recommendation categories:
Entity Clarity (Foundation):
Trust Signals:
Content Authority:
Competitive Gap:
Constraint: Never recommend keyword stuffing, fake reviews, or misleading schema. These tactics risk penalties and undermine genuine authority.
After completing the audit:
Flag gaps: "I could only test Perplexity — have the user run the same queries on ChatGPT and paste results for a complete audit."
Set specific re-audit dates before delivering:
30-day re-audit: After implementing critical fixes — did recognition improve? 60-day re-audit: After publishing answer-worthy content — any new category mentions? 90-day re-audit: Full comparative re-audit — full trend comparison to this baseline
Comparison table format for future audits:
| Dimension | [Baseline Date] | 30-Day | 60-Day | 90-Day | Δ |
|---|---|---|---|---|---|
| Recognition | [X/5] | | | | |
| Category | [X/5] | | | | |
| Authority | [X/5] | | | | |
| Total | [X/30] | | | | |
## AI Discoverability Audit: [Company] — [Date]
### Pre-Audit Hypothesis
[Prediction + reasoning]
---
### Phase 1: Direct Brand Queries
**ChatGPT:** [findings]
**Perplexity:** [findings]
**Claude:** [findings]
**Misattribution found:** [Yes/No — details]
### Phase 2: Category Queries
[Findings per query]
### Phase 3: Expertise Queries
[Findings]
### Competitive Comparison
[Table with real competitor names]
---
### Scores
| Dimension | Score |
|---|---|
| Recognition | /5 |
| Accuracy | /5 |
| Sentiment | /5 |
| Category Presence | /5 |
| Authority | /5 |
| Competitive Position | /5 |
| **TOTAL** | **/30** |
**Rating:** [Strong / Moderate / Weak / Invisible]
---
### Gap Analysis
**Critical (Fix Now):**
1. [Specific fix]
**High Priority (30 Days):**
1. [Specific fix]
**Opportunities (90 Days):**
1. [Specific improvement]
---
### Re-Audit Schedule
- 30-day: [YYYY-MM-DD] — measure: [what to check]
- 60-day: [YYYY-MM-DD] — measure: [what to check]
- 90-day: [YYYY-MM-DD] — full comparative re-audit
### Self-Critique Notes
[Any gaps, limitations, or things the user needs to run manually]
Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com
testing
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
testing
Clarify requirements before implementing. Use when serious doubts arise.
tools
Complete reference and build guide for ASI:One (ASI1) — the AI platform by Fetch.ai built for agentic, Web3-native applications. Use this skill IMMEDIATELY and ALWAYS when the user mentions ASI1, ASI:One, Fetch.ai AI API, building with ASI1, integrating ASI:One, asking about ASI1 models, tool calling with ASI1, ASI1 image generation, ASI1 agentic LLM, Agentverse, uagents, Agent Chat Protocol, structured output with ASI1, or OpenAI-compatible wrappers for ASI1. Also trigger when the user says things like "use ASI1 instead of OpenAI", "build an app with ASI:One", "ASI1 API", or references docs.asi1.ai. This skill covers everything needed to build production apps - setup, all models, all API features, tool calling, image gen, agentic orchestration, structured data, session management, streaming, LangChain integration, uagents / Agent Chat Protocol, and TypeScript/Node.js patterns.
data-ai
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.