aeo

Check and improve your brand's visibility across AI search engines (ChatGPT, Perplexity, Gemini, Grok, Claude, DeepSeek). Set up tracking, run visibility analyses, audit your website for AI readability, and get actionable recommendations. Uses the npx goose-aeo@latest CLI.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/seo/capabilities/aeo/SKILL.md

Quality

Content

77%

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

The body is highly actionable with executable commands and well-sequenced workflows that include validation checkpoints and error recovery, but it is a monolithic ~270-line file with no progressive disclosure to reference files and some conversational scripting that could be tightened.

Suggestions

Move the detailed Website Audit dimension breakdown and the Error Handling catalog into a reference file (e.g. references/audit-dimensions.md) and link to it from the body to improve progressive disclosure.

Tighten the repeated conversational prompts ('Show the user...', 'Ask:', 'Tell the user...') into a more compact convention to improve token efficiency.

Consider extracting the per-provider API-key prerequisite matrix into a reference, keeping the body focused on the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concepts Claude already knows (no explaining what AEO/CLIs are), but the repeated conversational scripting ('Have a natural conversation', 'Show the user...', 'Ask:', 'Tell the user:') across four workflows could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands with concrete flags throughout (e.g. 'npx goose-aeo@latest init --domain <domain> --providers ... --json', 'queries generate --limit 10 --dry-run --json'), matching the fully-executable anchor; placeholders like <domain> are justified flexibility.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit checkpoints — a top routing table, pre-flight status checks, a dry-run cost estimate with 'Ask for confirmation before proceeding', 'Do NOT proceed until you have at least the company domain', and an Error Handling feedback section — matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	There are no bundle files (references/scripts/assets absent) and the ~270-line skill is a single monolithic file; it is well-organized with clear headers, but content that could be split out (e.g. audit dimension breakdowns, error handling) is inline with no one-level-deep references, matching the 'some structure but content that should be separate is inline' anchor rather than the under-50-lines exception for a 3.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 specific and distinctive with good natural trigger terms, but it omits an explicit 'Use when...' trigger clause (capping completeness at 2) and uses second-person 'your' phrasing (triggering the specificity voice penalty).

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about brand visibility in AI search engines, AEO, or being mentioned by ChatGPT/Perplexity/Gemini.'

Rewrite in third person to avoid the voice penalty — e.g. 'Checks and improves a brand's visibility...' and 'audits a website for AI readability' instead of 'your'.

Consider including the terms 'AEO' and 'Answer Engine Optimization' explicitly, since users may use those exact phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Set up tracking, run visibility analyses, audit your website for AI readability, and get actionable recommendations'), which is anchor-3 quality, but the second-person phrasing ('your brand's visibility', 'your website') triggers the voice penalty that reduces specificity by one per the rubric guidelines.	2 / 3
Completeness	It clearly answers 'what' the skill does but lacks an explicit 'Use when...' clause or equivalent trigger guidance, so per the rubric guideline a missing explicit trigger caps completeness at 2 ('when' is only implied).	2 / 3
Trigger Term Quality	Good coverage of natural terms users would say — 'AI search engines' plus the named engines 'ChatGPT, Perplexity, Gemini, Grok, Claude, DeepSeek' and 'audit your website for AI readability' — matching the anchor for good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (AI-search-engine brand visibility) and names the specific 'goose-aeo@latest CLI', making it unlikely to trigger for the wrong skill, matching the clear-niche anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/seo/capabilities/aeo/SKILL.md
Commit: 8866b2a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.