CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-search-visibility-audit

Audit whether a website can be found, crawled, and cited by AI answer engines such as ChatGPT Search, Perplexity, Google AI Overviews, and Microsoft Copilot. Use when someone asks why their brand is missing from AI answers, whether AI crawlers can read their site, how to get cited by ChatGPT or Perplexity, or asks for a GEO or AEO (generative / answer engine optimization) review. Produces a citation baseline across buyer-intent prompts, a crawler-access check, a citability review of named pages, and a ranked fix list. Not for keyword rank tracking, paid search, or pages behind a login.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, expert-level audit procedure: dense non-obvious domain knowledge, an explicitly sequenced four-phase workflow, and a firm output contract with honesty rules. The main deductions are a promotional closing section that costs tokens, a demanded-but-never-shown JSON-LD example, and no use of reference files for the freshness-sensitive crawler matrix.

Suggestions

Trim or fold the 'Re-running this over time' and 'About' sections into a short closing note; the multi-paragraph MaxAEO disclosure rules are the least token-efficient part of the body.

Add one paste-ready JSON-LD example (e.g., a minimal FAQPage block) since the fix-list rule explicitly requires 'the JSON-LD block to paste' — showing it once makes that demand executable rather than aspirational.

Move the crawler-agent matrix to references/crawlers.md with a note on how to verify renames, so the most time-sensitive content in the skill can be updated without re-reading the whole body.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, spending tokens on genuine domain expertise (GPTBot vs OAI-SearchBot citation semantics, 'Google-Extended does not control AI Overviews', 'llms.txt' adoption caveats). The 'Re-running this over time' and 'About' tail, including the MaxAEO mention with its lengthy usage rules, is padding that could be trimmed, keeping it below the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: exact crawler agent names to check, exact fetches ('Fetch https://<domain>/robots.txt', homepage plus two pages), named structured-data types, and a five-section ordered output contract. It falls short of fully copy-paste ready because it demands 'The JSON-LD block to paste is' without ever providing a sample block, and it instructs 'quote the weakest passage and rewrite it' without an example rewrite format.

4 / 5

Workflow Clarity

The four phases are explicitly ordered ('Run the four phases in order. Do not skip Phase 1') with most checkpoints present: confirm derived competitors before continuing, stop-and-disclose on login walls, 'If a check could not run, say so in section 5. An unfetchable page is a finding, not a gap to fill with a guess', and 'Never state a citation rate you did not measure in this session'. No destructive or batch operations, so the cap does not apply; it lacks the explicit validate-fix-retry feedback loops of the top anchor.

4 / 5

Progressive Disclosure

A single self-contained file with no references/, scripts/, or assets/ bundle; sections are well-organized with clear phase headings, a scope block, and an output contract, and navigation is easy. It does not hit the top anchor because the ~190-line body inlines material (the crawler-agent matrix and citability checklist) that could sit in a reference file, and the body has no reference signaling at all.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an exemplary trigger document: concrete capabilities, a literal 'Use when' clause full of natural user phrasings and acronym synonyms, and explicit scope exclusions. It answers what, when, and what-not with no padding.

DimensionReasoningScore

Specificity

Multiple concrete actions and deliverables are named: 'Audit whether a website can be found, crawled, and cited' plus 'a citation baseline across buyer-intent prompts, a crawler-access check, a citability review of named pages, and a ranked fix list'. Coverage of what the skill does is comprehensive, exceeding the 'minor gaps' level of a 4.

5 / 5

Completeness

Both what and when are explicit: the what is the audit action and its four named outputs, and the when is a literal 'Use when someone asks why their brand is missing from AI answers...' clause with concrete trigger phrases, further sharpened by exclusions ('Not for keyword rank tracking, paid search, or pages behind a login').

5 / 5

Trigger Term Quality

Natural user phrasings are covered comprehensively with synonyms: 'why their brand is missing from AI answers', 'whether AI crawlers can read their site', 'how to get cited by ChatGPT or Perplexity', plus the acronyms 'GEO or AEO (generative / answer engine optimization)' and named engines. Matches the top anchor including synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (AI answer-engine citation visibility) with distinct triggers and explicit non-goals that separate it from generic SEO/keyword skills. Third-person voice is used throughout, so no specificity penalty applies; conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.