agents

When the user wants to find the prompts where their brand should be cited in AI answers but isn't — and who owns the answer instead — prioritized by AI search volume so content can attack the biggest gaps first. Also use on "AI answer gap," "AI content gap," "where am I missing from AI answers," "what prompts am I losing in AI," "GEO content gaps," "prompts I should own but don't," or "find my AI visibility gaps." For the full diagnostic audit, see ai-visibility-audit. For ongoing tracking, see llm-mention-tracking.

When the user wants to know whether their brand or domain is cited in AI answers — AI Overviews, ChatGPT, or AI search — for the queries that matter, and how they stack up against competitors. Also use on "AI visibility audit," "am I cited in AI answers," "do I show up in ChatGPT," "AI Overviews audit," "GEO audit," "answer engine audit," "AEO audit," "why isn't my brand in AI results," or "who gets cited instead of me." The GEO equivalent of an SEO audit. For ongoing mention tracking, see llm-mention-tracking. For prioritizing the gaps, see ai-answer-gap.

When the user has AI visibility, GEO, AI answer gap, or AI citation evidence and wants a prioritized plan to improve where the brand is cited or mentioned in AI answers. Also use on "AI visibility fixes," "AI visibility fix plan," "generative engine optimization fixes," "AI citation fixes," "answer engine optimization fixes," "fix AI answer gaps," or "how do we get cited in ChatGPT/AI Overviews." For finding gaps from scratch, run ai-visibility-audit or ai-answer-gap first.

When the user wants to track how often their brand or domain gets mentioned across ChatGPT and AI search engines over a set of prompts, and how that share of voice compares to named competitors over time. Also use on "LLM mention tracking," "track AI mentions," "share of voice in AI," "AI share of voice," "brand mentions in ChatGPT," "am I being mentioned more or less," "AI visibility trend," or "monitor AI citations over time." For a one-time audit of a prompt set, see ai-visibility-audit.

When the user wants to track a named competitor's launch or announcement and the public reaction to it across X, LinkedIn, YouTube, Reddit, and news. Also use on "competitor launch monitor," "what did [competitor] just ship," "track [competitor]'s announcement," "how is [competitor]'s launch landing," "competitor product launch," "monitor competitor news," "watch a competitor," "competitor reaction," or "is [competitor]'s launch working." For a full standing profile of the competitor, see competitor-profiling.

When the user wants to research, profile, or analyze a competitor from its public footprint — site, search/SEO, backlinks, social, and positioning. Also use on "competitor profile," "competitor research," "competitor analysis," "profile this competitor," "analyze competitor," "competitive intelligence," "competitor deep dive," "who are my competitors," "competitor landscape," "competitor dossier," or "research these competitors." Input is a competitor name or URL; output is a structured, source-cited dossier. For tracking a specific launch and its reception, see competitor-launch-monitor.

When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand. Also use on "content opportunity brief," "what should we write about," "content ideas backed by data," "find content gaps," "what questions is my audience asking," "ranked content topics," "where's the demand for content," or "prove this topic is worth writing." Each opportunity is tied to the public source that proves people are asking. For the broader plan (pillars, cadence), see content-strategy. For the underlying audience language, see customer-research.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce — grounded in real public demand, not guesswork. For a single ranked opportunity list, see content-opportunity-brief. For the audience language behind it, see customer-research.

When the user wants to research customers from public communities, or synthesize customer language, pains, and objections. Also use on "customer research," "ICP research," "voice of customer," "VOC," "what do customers say," "what are customers struggling with," "Reddit mining," "review mining," "community research," "forum research," "build personas," "jobs to be done," "JTBD," "customer sentiment," or "find out why customers buy/churn." Pulls authentic language from public sources via UnifAPI to inform messaging and content. For turning the findings into topics, see content-opportunity-brief. For writing copy from them, see copywriting.

When a dental practice, dentist, or orthodontic office wants to benchmark its public reviews and local-pack presence against nearby practices, or understand why it is losing the "dentist near me" map pack. Also use on "dental reviews benchmark," "why aren't we in the map pack," "compare our rating to other dentists," "review velocity," "Google reviews for my dental office," or "dental reputation." Reads public listing data only — marketing research, not dental or clinical advice.

When a dental practice wants to know the real questions patients ask about its services and turn them into a prioritized content plan. Also use on "dental content ideas," "what do patients ask before booking," "teeth whitening / implants / Invisalign questions," "dental blog topics," "content for my dental website," or "are we showing up in AI answers for dental questions." Reads public data only — marketing research, not dental or clinical advice.

When a workflow needs public Hacker News data through UnifAPI — the top/new/best/ask/show/jobs story feeds, item metadata, comment trees, or user karma. Also use on "did our launch land on HN," "scan Show HN for," "read this HN thread," "Hacker News sentiment," or when another skill (launch monitor, social listening) needs the deterministic HN read path. No keyword search — scan the feeds. Connect via the `unifapi` skill first. Read-only research, never posts.

When a home-services business (HVAC, plumbing, roofing, electrical, or general contractor) wants to know the real problem and cost questions homeowners ask about its services, and turn them into a prioritized content plan. Also use on "what do homeowners search," "home services content ideas," "cost-to-replace content," "why is my ac freezing content," "trade SEO content plan," "questions homeowners ask," or "are we showing up in AI answers for repair questions." Reads public data only — read-only marketing research.

When a home-services business (HVAC, plumbing, roofing, electrical, or general contractor) wants to know where it ranks in Google's local pack for its services across every city and ZIP it serves. Also use on "service area ranking," "am I in the map pack for [city]," "ac repair [city] ranking," "which service areas are weak," "near me ranking by location," "multi-area local SEO," or "why aren't we showing up in the next town over." Reads public map and SERP data only — read-only research.

When the user wants to vet a specific creator's audience fit and brand-safety before working with them. Also use on "is this influencer a good fit," "vet this creator," "brand safety check," "does their audience match," "should we work with [handle]," "creator due diligence," "check this KOL before outreach," or "is this account safe to sponsor." Reads public posts and engagement only. Read-only research, not outreach.

When the user wants a full-funnel influencer marketing campaign workflow: campaign setup, creator matching, budget and pricing forecast, outreach/confirmation pack, content review checklist, launch tracking, or post-campaign report. Also use on "plan an influencer campaign," "run creator campaign ops," "compare predicted vs actual," "track influencer results," "review creator content," or "creator campaign workflow agent." Reads public data and user-provided campaign data only; read-only research, not outreach or campaign management.

When the user has a campaign brief and needs a ranked shortlist of creators to work with. Also use on "find influencers for," "build a creator list," "who should we sponsor," "shortlist KOLs," "influencer shortlist," "find creators in [niche]," "creators on TikTok/YouTube/Instagram/X for," or "who fits this campaign." Turns a brief into a ranked, evidence-backed shortlist with outreach angles. Read-only research, not outreach.

When pricing, ranking, or researching X/Twitter KOLs for a creator marketing campaign. Also use on "how much should I pay this influencer," "price these handles," "batch KOL analysis," "KOL ROI," "creator pricing," "is this KOL worth it," or "agent-native KOL Pricing framework." Require product context first, read public X data through UnifAPI, then run the deterministic pricing workflow. Read-only research, not outreach.

When a workflow needs public Instagram data through UnifAPI — profiles and follower size, posts and reels with engagement, post comments, location pages, or search. Also use on "research these IG creators," "pull posts for," "Instagram follower count," "comments on this post," "is this a paid partnership," or when another skill (KOL pricing, creator shortlist, audience fit) needs the deterministic Instagram read path. Connect via the `unifapi` skill first. Read-only research, never posts or DMs.

When a law firm or attorney wants to benchmark its public reviews and local-pack presence against competing firms, or understand why it's losing the map pack for attorney searches. Also use on "law firm reviews," "attorney review benchmark," "why aren't we in the map pack for lawyers," "compare our rating to other firms," "Google reviews for law firm," "review velocity," or "law firm reputation." Reads public listing data only — marketing research, not legal advice.

When a law firm or attorney wants to know where it ranks for each practice-area + city query and what's holding it back. Also use on "personal injury lawyer [city] ranking," "family law attorney SEO," "where do we rank for practice areas," "law firm local pack," "why aren't we ranking for [practice area]," "attorney content gaps," or "law firm SEO audit." Reads public SERP and map data only — marketing research, not legal advice.

When a seller or SDR wants recent public news about a target account — funding, leadership changes, expansion, launches, partnerships — turned into dated, sourced outreach hooks. Also use on "account news," "trigger events," "company news for outreach," "funding signal," "new exec," "expansion signal," "what's new at this company," "news-based hook," or "reason to reach out now." Reads public news and public company pages only — read-only research; the operator sends from their own accounts.

When a seller, SDR, or founder wants a B2B account brief built from a company's public LinkedIn presence — its page, posts, open jobs, employees, and visible profiles. Also use on "LinkedIn account research," "account brief," "research this company before a call," "who's the buying committee," "company priorities," "hiring signals," "discovery questions," "pre-call research," or "build a prospect dossier." Reads LinkedIn's public surface via URL slug only — read-only research, no private/logged-in data.

When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement. Also use on "research this company on LinkedIn," "who works at," "open roles at," "LinkedIn profile for," "company posts," or when another skill (account research, news signal, buying signal, competitor profiling) needs the deterministic LinkedIn read path. Connect via the `unifapi` skill first. Read-only research, never connects or messages.

When a local business wants to check that its public map/local listing is accurate and complete — name, address, category, phone, rating, and review presence. Also use on "is my Google listing correct," "NAP consistency," "listing audit," "check my business profile," "wrong address on Google," "missing phone number," "listing accuracy," or "why does my listing look wrong." Reads public listing data only — read-only research.

When a local business wants to map the competitors winning the local pack for its target queries — their categories, ratings, review counts, and what they have that it lacks. Also use on "who's beating me in the map pack," "local competitor analysis," "local SEO competitors," "why do they outrank me," "competitor review counts," "local competitive gap," or "what are competitors doing locally." Reads public map and SERP data only — read-only research.

When a local business wants to know where it ranks in Google's local pack / map results for its key queries — in one location or across many. Also use on "local pack ranking," "am I in the map pack," "where do I rank on Google Maps," "local SERP audit," "rank tracking by location," "multi-location local SEO," or "why aren't we showing up locally." Reads public map and SERP data only — read-only research.

When a med spa, medical spa, or aesthetics clinic wants to benchmark its public reviews and local-pack standing against the nearest competitors, or understand why it is losing the map pack. Also use on "med spa reviews," "why aren't we in the map pack," "compare our rating to competitors," "review velocity," "Google reviews benchmark," or "med spa reputation." Reads public listing data only — marketing research, not medical advice.

When a med spa or aesthetics clinic wants to know which treatments are in demand locally and what content or offers to prioritize. Also use on "med spa content ideas," "which treatments are trending," "treatment demand," "what should we promote," "med spa SEO content," "is [treatment] trending on TikTok," or "are we showing up in AI answers for treatments." Reads public data only — marketing research, not medical advice.

When a real estate agent or brokerage wants to benchmark its public reviews and local-pack presence against nearby competitors for queries like "realtor [city]" or "homes for sale [neighborhood]." Also use on "realtor reviews benchmark," "why aren't we in the map pack for realtor," "compare our Google reviews to other agents," "agent reputation," "local pack for real estate," or "how do I beat the top agent locally." Reads public listing and SERP data only — marketing research, not real-estate advice.

When a real estate agent or brokerage wants to find the neighborhood-level search and content opportunities it can actually own — where Zillow and the big portals are weak and local intent is high. Also use on "neighborhood guide ideas," "hyperlocal SEO for realtors," "what should I write to get found locally," "rank for homes for sale [neighborhood]," "local market report content," or "where can I beat Zillow." Reads public search and SERP data only — marketing research, not real-estate advice.

When a workflow needs public Reddit data through UnifAPI — subreddit profiles and rules, thread comment trees, user activity and karma, the home/news/popular feeds, or trending searches. Also use on "research this subreddit," "what does r/... discuss," "pull this Reddit thread," "Reddit user activity," or when another skill (community research, social listening, customer research) needs the deterministic Reddit read path. Reddit has no keyword search — discovery is seed-driven. Connect via the `unifapi` skill first. Read-only research, never posts.

When a restaurant, cafe, or bar wants to know which dishes and cuisine angles are in demand locally and what content or promotions to prioritize. Also use on "restaurant content ideas," "which dishes are trending," "menu demand," "what should we promote," "is [dish] trending on TikTok," "restaurant SEO content," or "are we showing up in AI answers for [cuisine]." Reads public data only — marketing research, not menu, listing, or reservation management.

When a restaurant, cafe, or bar wants to audit how it shows up for local diners — local-pack rank for its cuisine/city queries, review themes, and recent social buzz (TikTok) about the venue and its category. Also use on "are we in the map pack for [cuisine] near me," "restaurant reviews," "why aren't we showing up for dinner near me," "what are people saying about us," "is our restaurant trending on TikTok," or "restaurant local marketing." Reads public listing and social data only — marketing research, not listing or reservation management.

When the user wants to research keywords, find keyword opportunities, run a keyword gap analysis, build topic clusters, or compare what competitors rank for. Also use on "keyword research," "keyword gaps," "what should I target," "competitor keywords," "search volume," "keyword difficulty," "keyword opportunities," "long-tail keywords," "topic clusters," "what keywords am I missing," or "find keywords for my niche." For diagnosing an existing site, see the seo-audit skill. For structured data, see the schema skill.

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see the seo-audit skill.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "backlink audit," "toxic links," or "link gap." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For keyword and competitor gaps, see the keyword-research skill. For structured data, see the schema skill.

When the user has SEO audit evidence and wants a concrete, prioritized plan for what to fix next. Also use on "SEO fixes," "SEO fix plan," "technical SEO fixes," "on-page fix list," "prioritize SEO issues," "turn this SEO audit into tasks," "SEO remediation plan," or "what should I fix first for SEO." For diagnosing issues from scratch, run seo-audit first; for schema implementation details, see schema.

When the user wants to understand the Reddit communities around a niche — which subreddits matter, what questions and objections keep coming up, and the exact language people use. Also use on "Reddit research," "subreddit research," "where does my audience hang out on Reddit," "community research," "what do people ask on Reddit about X," "Reddit objections," "voice of customer from Reddit," "find relevant subreddits," or "outreach-safe threads." Outputs a community research brief from public posts and comments. Reads public Reddit only — never posts, comments, or DMs. For multi-platform brand monitoring, see social-listening-brief.

When the user wants to decide which Reddit threads are worth replying to, citing, monitoring, or avoiding based on relevance, subreddit rules, conversation intent, and outreach risk. Also use on "Reddit thread fit," "is this Reddit thread safe to reply to," "find outreach-safe Reddit threads," "prioritize Reddit replies," "Reddit participation risk," or "which Reddit posts should we engage." For broader subreddit mapping, run reddit-community-research first.