agentleFS
Sign inStart free
retracnretracn/automationnation-data-tools/skills/ai-visibility-audit/SKILL.md

ai-visibility-audit

Skill0 starsChanged 39 days agoMITView on GitHub

Check whether AI assistants and Google AI Overviews mention and cite a brand or website. Use when the user asks about AI search visibility, GEO or AEO, whether ChatGPT-style answers recommend them, share of voice in AI answers, which competitors AI recommends, or whether Google AI Overviews cite their site.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use local-seo.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • huiferSkill

    local-seo

    本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO，分析 NAP（Name, Address, Phone）一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议，包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run check_ai_visibility with those prompts and competitors, and check_ai_overview_citations for the user's key searches and domain.

    line 9
  2. Very specific:

    If these tools aren't available, the AutomationNation connector isn't connected: ask the user to add …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use the AutomationNation connector's check_ai_visibility (Google AI Overviews, Gemini and Claude) and check_ai_overview_citations (Google AI Overviews for given searches) tools. Through Apify's hosted connector each tool name carries a prefix and a short suffix, for example automati--data-tools-mcp-server--search_flights-9279; match tools by the name in the middle.

  1. Collect the brand, its website, 3–5 competitors and 5–10 questions real customers ask ("best CRM for small business", "X vs Y"). Suggest questions if the user has none.
  2. Run check_ai_visibility with those prompts and competitors, and check_ai_overview_citations for the user's key searches and domain.
  3. Report: how often the brand is mentioned and cited per engine, its rank against competitors, which competitors are named instead, the sentiment, and the sources the engines cite.
  4. Turn it into actions: the sources the engines lean on (review sites, listicles, YouTube, Reddit) where the brand should appear, and the questions where it is absent.
  5. Suggest re-running the same prompts monthly to track the trend.

Each answer checked costs $0.05; AI Overview keyword checks cost $0.04 each (plus $2 per run from 17 November 2026), on the user's Apify account.

If these tools aren't available, the AutomationNation connector isn't connected: ask the user to add https://mcp.apify.com/?tools=automationnation/data-tools-mcp-server as an MCP server or connector and sign in with a free Apify account, then continue.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free