CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-visibility-audit

Audit how a brand shows up in AI answers about its market and deliver a short report on the few changes most likely to get it mentioned or cited, such as a third-party page to get onto, an owned page to improve, or an access problem to fix. Use when the user asks for an AI visibility audit, a GEO or AEO audit, why AI recommends competitors instead of them, or how to show up in ChatGPT, Gemini or Google AI answers.

Quality

95%

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

The canonical home for this skill is ai-visibility-audit in every-app/open-seo

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An unusually tight operational skill: it assumes Claude's intelligence (zero concept explanations), gives fully executable tool-level instructions with parameters and exact counts, and sequences a conditional five-state workflow with explicit approval, polling, pagination, and error-recovery checkpoints. The only soft spots are a few sentences that could be shortened and a single-file layout that is slightly past the size where splitting out the report template would help.

Suggestions

Tighten the longest sentences (e.g. the tracker brand-name rule in Project context item 3) by splitting them into a short rule plus one example.

Consider moving the detailed report-format spec in "What to return" (section list, table columns, evidence block) into a one-level-deep reference file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and operational throughout — no paragraphs explaining what GEO/AEO or AI crawlers are, and every tool mention carries its parameters ("limit: 50", "runNowCostUsd as maxCostUsd"). It is efficient with only minor instances that could be tightened, e.g. the long brand-name-confirmation sentence in Project context item 3 and some multi-clause sentences in step 3, matching the 4 anchor rather than 5 (not every token is minimal).

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact tool names per decision point, concrete counts ("10–15 neutral prompts across two or three topics", "Read the five or six that decide the recommendations"), exact parameters and payloads ("{brandName: \"Acme\"}", "appendResearchLog: { summary: ... }"), and a fully specified report template down to table columns. This matches the 5 anchor's coverage of common cases with copy-paste-ready specifics; not 4 because no key execution detail is missing.

5 / 5

Workflow Clarity

The five-step workflow (Get evidence → Read where the brand stands → Follow the citations → Check the owned side → Shortlist) has explicit validation and recovery: approval gating before any spend, "get approval once", following a pending run "respecting pollAfterSeconds", pagination checks ("follow nextCursor before counting"), and the error loop "If it returns an error, such as no paid plan, continue without it and say so". Checkpoints and failure paths ("A failed or partial run still supplies whatever answers it completed; report its coverage") match the 5 anchor; not 4 because validation is explicit at each risky step rather than mostly present.

5 / 5

Progressive Disclosure

No bundle files exist, so structure rests on the single SKILL.md: clear sections (Goal, Project context, MCP tools, numbered Workflow, What to return, Guardrails) that are easy to navigate, with no nested or buried references. It matches the 4 anchor (good structure, appropriately placed content, minor organization gaps) rather than 5 because at ~110 lines some self-contained blocks — the detailed report-format spec in "What to return" or the tool catalog — could arguably live in one-level-deep reference files, and the rubric's simple-skill 5 exception only covers skills under 50 lines.

4 / 5

Total

18

/

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.

A model description: third-person voice, concrete actions with a concrete deliverable shape, an explicit "Use when" clause rich in natural trigger phrases including the GEO/AEO synonyms, and a distinct niche that will not fire for the wrong skill. Nothing vague or overstated.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audit how a brand shows up in AI answers", "deliver a short report on the few changes most likely to get it mentioned or cited" — and concretizes the deliverable with "a third-party page to get onto, an owned page to improve, or an access problem to fix". This matches the 5 anchor (multiple specific concrete actions, comprehensive within the domain) rather than 4, since no meaningful action in the skill's scope is missing.

5 / 5

Completeness

It explicitly answers both what ("Audit how a brand shows up in AI answers... and deliver a short report on the few changes most likely to get it mentioned or cited") and when (an explicit "Use when the user asks for..." clause with concrete trigger phrases), exactly matching the 5 anchor's good example pattern. Not 4, because the when-clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

The "Use when" clause covers the natural phrases a user would actually say: "AI visibility audit, a GEO or AEO audit, why AI recommends competitors instead of them, or how to show up in ChatGPT, Gemini or Google AI answers" — including the GEO/AEO synonyms and named engines. Coverage is comprehensive with synonyms; not 4 because no common variation (e.g., "AI search visibility", engine names) is missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (AI answer visibility auditing) with distinct triggers (GEO/AEO audit, competitor mentions in AI answers) that no adjacent skill (e.g., general SEO or prompt research) would claim; it even names its sibling boundary implicitly via the body. Minimal conflict risk, matching the 5 anchor; not 4 because no closely related skill's triggers overlap with these phrases.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

every-app/open-seo

Path

.agents/skills/ai-visibility-audit/SKILL.md

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.