ai-visibility
Skill0 starsChanged 34 days agoMITView on GitHub
Check whether AI assistants name a local business when buyers ask, and why or why not. Builds a buyer question panel, records answers with dates, audits crawler access, structured data and llms.txt, and returns a score with fixes. Use for "does ChatGPT recommend us" or an AI search check.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- epicx-labs/keytomic-claude-plugintheir own version, first seen Nov 1, 2026
- akii-technologies-ltd/akii-seo-ai-search-optimizertheir own version, first seen Nov 1, 2026
- himoose/aeo-skillstheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- Ryze-AI-Adgent/open-seo-mcp-skillstheir own version, first seen Oct 27, 2026
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
Used with
Projects with it also use content-brief and seo-audit.
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.
LangChainSkillcontent-brief
Turn a vague or multi-asset design ask into a brief. Pull what is already known, ask at most two questions with reasons, decide the rest and say what you decided.
Also in 3 projects that use this
AnthropicSkillseo-audit
Run a comprehensive SEO audit — keyword research, on-page analysis, content gaps, technical checks, and competitor comparison. Use when assessing a site's SEO health, when finding keyword opportunities and content gaps competitors own, or when you need a prioritized action plan split into quick wins and strategic investments.
Also in 4 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 79same name
- drvoss/everything-copilot-cli★ 48same name
- searchfit/searchfit-seo★ 9same name
- sharozdawa/ai-visibility★ 9same name
- petar-nauka/ai-visibility-skill★ 8same name
- YepAPI/skills★ 8same name
- himoose/aeo-skills★ 2same name
- seoonpage/onpage-tools★ 2same name
- seoonpage/seo-mcp-server★ 2same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- domain-checkupSkill
- local-schemaSkill
- map-pack-gapSkill
- presence-auditSkill
- review-repliesSkill
- review-requestsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Write 8 to 12 buyer questions for the trade and town, the way a customer would ask an AI assistant.
- Very specific: line 12
Run the AI Search Kit audit_ai_readiness tool on the homepage, and check_entity_consistency on the website plus any profile URLs.
- Distinctive: line 16
Never promise that an AI engine will recommend the business.
“Common” is measured: kept by at least 6 in 10 of the 14 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.
Files
AI visibility check
Business: $ARGUMENTS
- Write 8 to 12 buyer questions for the trade and town, the way a customer would ask an AI assistant.
- Collect answers. Use web search where you have it. For any engine you cannot reach, such as ChatGPT, Perplexity, Gemini or Google AI Overviews, give the user the questions and ask them to paste the answers. Record the engine, the date, who is named, in what order, and which URLs are cited. Never write an answer you did not see.
- Run the AI Search Kit
audit_ai_readinesstool on the homepage, andcheck_entity_consistencyon the website plus any profile URLs. - Score it: for each question and engine checked, first position 1.0, second 0.7, third 0.5, named lower 0.3, not named 0. Average, then multiply by 100. State the formula and how many answers it covers.
- Report the evidence table, the score, and the fixes ranked by impact. Offer the
local-schemaskill to draft and validate JSON-LD and llms.txt.
Never promise that an AI engine will recommend the business. No em dashes.
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
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.