CtrlK
BlogDocsLog inGet started
Tessl Logo

aeo

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/aeo/SKILL.md

The canonical home for this skill is aeo in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is action-oriented with concrete CLI commands and a clear workflow, but it over-inlines content that belongs in references and is missing the referenced bundle files. A post-optimization validation checkpoint would lift workflow clarity above its batch-operation cap.

Suggestions

Add a validation/review checkpoint to the workflow after optimization (e.g., verify the optimized variant renders and that injected JSON-LD validates) so destructive/batch operations are no longer uncapped at 3.

Move the inlined industry-thresholds table and anti-patterns list into the referenced files and ensure references/ actually exists with aeo_eeat_canon.md, llm_citation_patterns.md, aeo_vs_seo.md, bot_access_and_monitoring.md, and extractable_content_patterns.md present.

Trim repeated trigger phrases and the full markdown audit-report template, or relocate them, to tighten token usage; the triggers already appear in the frontmatter description.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but the inlined audit-report template, the SEO comparison table, the anti-patterns section, and repeated trigger phrases add padding that could move to references or be trimmed.

3 / 5

Actionability

Provides concrete, copy-pasteable CLI commands with specific flags and modes across all three tools, plus a full example report format, with only minor gaps.

4 / 5

Workflow Clarity

A clearly numbered workflow with commands is present, but it involves batch/rewrite operations (content optimization, schema injection) with no validation checkpoint after optimization, capping it at 3 per the destructive/batch rule.

3 / 5

Progressive Disclosure

Five reference files are clearly signaled with one-line descriptions, but the references/ directory is absent so the referenced paths are missing, and sizable content (industry thresholds, anti-patterns) is inlined rather than moved out.

3 / 5

Total

13

/

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 specific, comprehensive, and well-structured with clear trigger phrases and explicit when-to-use guidance. It is notably distinct from SEO with explicit disambiguation, making it a strong, low-conflict skill description.

DimensionReasoningScore

Specificity

Names the AEO domain and multiple concrete actions (audit, optimize E-E-A-T, track citations) across named LLMs, matching the comprehensive coverage anchor.

5 / 5

Completeness

Explicitly answers both what (optimize content for LLM citation, audit E-E-A-T, track citations) and when via an explicit 'Use when' clause with concrete triggers, matching the top anchor.

5 / 5

Trigger Term Quality

Includes a rich set of natural user phrases ('AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'content for AI search') plus product names, matching the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Explicitly disambiguates AEO from SEO ('distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings') giving it a clear niche with minimal conflict risk.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.