ai-crawler-visibility
Skill from MerqryLabs/ai-crawler-visibility
Install
npx skills add MerqryLabs/ai-crawler-visibility --skill ai-crawler-visibility
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
What does the ai-crawler-visibility skill do?
Description from the SKILL.md in the source repository.
Questions about ai-crawler-visibility
What does the ai-crawler-visibility skill do?
Diagnose whether a website's content is visible to AI crawlers (ClaudeBot, GPTBot, PerplexityBot, Bytespider, Meta-ExternalAgent) that do NOT execute JavaScript, and prescribe framework-specific fixes. Use this skill whenever the user asks why their site isn't showing up in ChatGPT / Claude / Perplexity / AI search, mentions an AI crawler or AEO/GEO, suspects their single-page app (SPA), React/Vite/Vue/Svelte site, or "vibe-coded" site is invisible to AI, asks whether their content is in the raw HTML, or reports zero GPTBot/AI traffic — even if they don't use the exact words "AI crawler."
How do I install ai-crawler-visibility?
In a terminal: npx skills add MerqryLabs/ai-crawler-visibility --skill ai-crawler-visibility. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use ai-crawler-visibility?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is ai-crawler-visibility safe to use?
Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.
Related skills in Frontend & UI
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
No description in the SKILL.md.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com and x.ai: plain copy in a voice of its own, one system, one section per screen, equal …
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs.
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts …