aeo-optimization

AI Engine Optimization - semantic triples, page templates, content clusters for AI citations

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/aeo-optimization/SKILL.md

Quality

Discovery

32%

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 identifies a specific domain (AI Engine Optimization) and lists relevant concepts, but lacks action verbs describing what the skill does and entirely omits a 'Use when...' clause. It reads more like a tag list than a functional description, making it difficult for Claude to confidently select this skill at the right time.

Suggestions

Add action verbs to describe concrete capabilities, e.g., 'Generates semantic triples, creates optimized page templates, and builds content clusters to improve AI citation likelihood.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about optimizing content for AI search engines, getting cited by AI assistants, AEO strategy, or structured content for LLMs.'

Include common user-facing synonyms and variations such as 'AEO', 'AI search optimization', 'get cited by ChatGPT/Perplexity', or 'LLM-friendly content' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names a domain ('AI Engine Optimization') and lists some specific concepts ('semantic triples, page templates, content clusters for AI citations'), but these read more like a list of topics than concrete actions. No verbs describe what the skill actually does (e.g., 'generates', 'creates', 'optimizes').	2 / 3
Completeness	The description loosely addresses 'what' (AI Engine Optimization involving semantic triples, page templates, content clusters) but provides no 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (no verbs/actions), so this falls to 1.	1 / 3
Trigger Term Quality	Terms like 'semantic triples', 'content clusters', and 'AI citations' are somewhat relevant but fairly technical. Common user phrases like 'optimize for AI search', 'AEO', 'get cited by AI', or 'AI search visibility' are missing, reducing natural keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The niche of 'AI Engine Optimization' is relatively distinct, and terms like 'semantic triples' and 'AI citations' help differentiate it. However, 'content clusters' and 'page templates' could overlap with general SEO or content strategy skills, creating some conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill is comprehensive in coverage but severely over-engineered for a SKILL.md file. It reads more like a complete marketing playbook or blog post than concise instructions for Claude. The templates and checklists provide genuine value, but they're buried in excessive context, motivational framing, and conceptual explanations that Claude doesn't need. The entire file should be restructured with a lean overview pointing to separate template and reference files.

Suggestions

Reduce the SKILL.md to ~80 lines: a brief purpose statement, the semantic triple pattern, the paragraph pattern, and links to separate files for each template (TEMPLATES.md), checklists (CHECKLIST.md), and schema examples (SCHEMA.md).

Remove the 'Why AEO Matters Now' section entirely—Claude doesn't need market stats or motivational framing to follow instructions.

Remove the 'AEO vs Traditional SEO' and 'How AI Engines Choose Answers' sections, which explain concepts rather than instruct action.

Add a clear sequential workflow: e.g., '1. Identify content type needed → 2. Select template → 3. Draft using paragraph pattern → 4. Validate against per-page checklist → 5. Verify cluster links exist.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Includes extensive background information Claude already knows (what AI engines are, why AEO matters, market stats, SEO vs AEO comparisons). The ASCII art diagrams, motivational framing ('THE GREAT DECOUPLING'), and conceptual explanations consume significant tokens without adding actionable value. Much of this is educational content for humans, not instructions for Claude.	1 / 3
Actionability	The templates are concrete and fill-in-the-blank ready, the semantic triple pattern is clear with good/bad examples, and the checklists are actionable. However, the skill is primarily template-based rather than executable—there are no specific commands or scripts to run, and the schema markup examples are placeholder-heavy. The guidance is structural rather than precisely executable.	2 / 3
Workflow Clarity	The content provides clear templates and checklists but lacks a sequenced workflow for actually creating AEO-optimized content. There's no step-by-step process like 'first audit existing content, then create category explainer, then build product pages.' The checklists serve as validation but there's no explicit ordering or feedback loop for iterating on content quality.	2 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to supporting files. The five page templates, schema examples, cluster architecture, checklists, metrics, and comparison tables could easily be split into separate referenced files. The result is a wall of content that's difficult to navigate and consumes excessive context window space.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (556 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 7e5f7a2

Reviewed: 3 days 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.