sales-ai-visibility
AI visibility monitoring strategy — tracking what ChatGPT, Claude, Perplexity, Gemini, and other LLMs say about your brand. Covers manual monitoring (prompt templates), tool selection (BrandJet AI, Otterly.ai, Topify, Sight AI, LLMrefs, Serplock, Semrush, Ahrefs Brand Radar, Meltwater), keyword and competitor tracking, understanding AI citations, improving AI visibility (content strategy, Reddit/forum presence, entity optimization), and measuring impact over time. Use when you don't know what ChatGPT or Perplexity says about your brand, competitors are showing up in AI answers but you're not, unsure which AI visibility tool to use, or want to improve how LLMs describe your product. Do NOT use for traditional social listening (use /sales-social-listening), SEO-specific help (use /sales-semrush), BrandJet platform help (use /sales-brandjet), Serplock platform help (use /sales-serplock), or Meltwater platform help (use /sales-meltwater).
What this skill does
# AI Visibility Monitoring Strategy
Helps the user monitor and improve what AI models (ChatGPT, Claude, Perplexity, Gemini, and others) say about their brand — from manual prompt checks through tool selection, citation analysis, content strategy, and ongoing measurement. This skill is tool-agnostic and applies whether the user has no monitoring in place or is evaluating dedicated AI visibility platforms.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What do you need help with?**
- A) Checking what AI models currently say about my brand
- B) Choosing an AI visibility monitoring tool
- C) Improving my brand's presence in AI answers
- D) Tracking competitors in AI search results
- E) Understanding how LLM citations and mentions work
- F) Setting up ongoing monitoring and measurement
- G) Something else — describe it
2. **What's your current situation?**
- A) Haven't checked AI models yet — starting from zero
- B) Manually checking occasionally (copy-paste prompts)
- C) Using a monitoring tool — which one?
- D) Evaluating tools / comparing options
3. **What's your industry and brand type?**
- A) B2B SaaS / tech
- B) E-commerce / DTC
- C) Agency / consultancy
- D) Local business
- E) Enterprise / large brand
- F) Other — describe it
4. **Budget range?**
- A) Free / manual only
- B) Under $200/mo
- C) $200-1,000/mo
- D) Enterprise ($1,000+/mo)
- E) Not sure yet
**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
## Step 2 — Route or answer directly
If the request maps to a platform-specific skill, route:
- BrandJet AI setup, config, or features → `/sales-brandjet`
- Serplock Prompt Rank, Brand Wiki, Topic Graph, Content Engineering → `/sales-serplock`
- Semrush AI Visibility Toolkit → `/sales-semrush`
- Meltwater ChatGPT monitoring → `/sales-meltwater`
- ReddGrow setup, Reddit GEO, AI Visibility Scanning, AI comment drafting, or Chrome extension → `/sales-reddgrow [question]`
- CrowdReply setup, AI search visibility tracking, engagement credits, managed Reddit posting, citation intelligence, or prompt tracking → `/sales-crowdreply [question]`
- Traditional social listening (not AI-specific) → `/sales-social-listening`
Otherwise, answer directly from the strategy knowledge below.
## Step 3 — AI visibility strategy reference
**Read `references/platform-guide.md`** for detailed monitoring frameworks, tool comparisons, citation analysis, improvement strategies, and measurement metrics.
*You no longer need the platform guide details — focus on the user's specific situation.*
## Step 4 — Actionable guidance
Based on the user's specific question:
1. **Brand audit** — run the manual prompt templates across models, document findings, identify gaps
2. **Tool selection** — recommend the best tool for their use case, budget, and existing stack
3. **Monitoring setup** — design keyword strategy, configure competitor tracking, set measurement cadence
4. **Improvement plan** — content strategy, third-party presence, entity optimization, timeline
5. **Reporting** — design a quarterly AI visibility report for stakeholders
6. **Competitive analysis** — compare brand vs competitors across AI models, identify where competitors are mentioned and you are not
Provide specific, step-by-step recommendations. Include prompt templates where relevant. Set realistic expectations about timelines (months, not weeks) and the inherent variability of AI answers.
## Gotchas
*Best-effort from research — review these, especially items about pricing and capabilities that may change.*
- **AI visibility tools are a nascent category.** Most launched in 2024-2025. Features, pricing, and even company survival are in flux. Evaluate carefully and avoid long contracts.
- **No tool covers every model.** Most tools focus on ChatGPT and Perplexity. Coverage of Claude, Gemini, and others varies. Check which models a tool actually monitors before committing.
- **Manual checks are unreliable for trending.** Because AI answers vary per session, a single manual check does not represent what most users see. Tools that run hundreds of prompts and average results give a more accurate picture.
- **AI visibility and SEO are related but different.** Ranking #1 on Google does not guarantee AI models mention your brand. Conversely, AI models may mention brands that do not rank well in traditional search. Treat AI visibility as a separate channel.
- **Reddit presence matters more than you think.** Reddit is a retrieval source for ChatGPT, Perplexity, and Google AI Overviews. Genuine Reddit presence (not astroturfing) can directly influence what AI models say about your brand.
- **Do not expect click-through.** Most AI mentions do not include links. The value of AI visibility is brand awareness and consideration, not direct traffic. Measure accordingly.
- **Accuracy of AI responses about your brand is a real risk.** LLMs can hallucinate facts, attribute wrong features, or confuse your brand with a competitor. Regular audits catch errors before customers see them.
- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.
## Before recommending a specific platform skill
This skill covers a strategy domain across many platforms. **Before pointing the user to any specific platform skill** (any `/sales-{platform}` listed in `## Related skills`, e.g., `/sales-mailshake`, `/sales-klaviyo`, `/sales-apollo`), read that platform skill's actual `SKILL.md` first. The 1-line description in `## Related skills` is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.
**How to read it:**
- If `~/.claude/skills/{skill-name}/SKILL.md` exists locally, `Read` it.
- For `sales-*` skills, `WebFetch` directly from this repo: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md` — e.g., for `sales-mailshake`: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md`.
- For non-`sales-*` skills (third-party), look up `{org}/{repo}` in `~/.claude/skills/sales-do/references/skill-sources.md` if installed and fetch the same `skills/{skill-name}/SKILL.md` path under that repo.
**After reading,** ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its `argument-hint` shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's `argument-hint`. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
## Related skills
- `/sales-brandjet` — BrandJet AI platform help — outreach, brand intelligence, AI monitoring
- `/sales-social-listening` — Social listening and brand monitoring strategy
- `/sales-semrush` — Semrush platform help — SEO, AI Visibility Toolkit
- `/sales-meltwater` — Meltwater platform help — media intelligence
- `/sales-yoast` — Yoast SEO platform help — llms.txt generation (Shopify), Schema Aggregation for AI. Install: `npx skills add sales-skills/sales --skill sales-yoast`
- `/sales-reddgrow` — ReddGrow — Reddit marketing for AI search visibility (GEO) with AI Visibility Scanning, AI comment drafting, Chrome extension, REST API
- `/sales-crowdreply` — CrowdReply — AI search visibility tracking + managed Reddit engagement via trusted community profiles, citation source intelligence, $99-499+/mo
- `/sales-serplock` — Serplock platform help — AI search visibility with Prompt Rank, Brand Wiki, Topic Graph, Content Engineering
- `/sales-do` — Not sure which skill to use? The router matches any sales Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".