aeo-optimization
AI Engine Optimization - semantic triples, page templates, content clusters for AI citations
42
30%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aeo-optimization/SKILL.mdQuality
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 clear domain (AI Engine Optimization) and lists some relevant technical concepts, but it lacks action verbs describing what the skill does and has no 'Use when...' clause to guide skill selection. 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 concrete action verbs describing what the skill does, e.g., 'Generates semantic triples, designs page templates, and builds content cluster strategies to optimize web content for AI engine citations.'
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 ChatGPT/Perplexity, AEO strategy, or structuring content for AI crawlers.'
Include common user-facing synonyms and variations such as 'AEO', 'AI search optimization', 'generative engine optimization', 'GEO', or 'get cited by AI' 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 keyword list than concrete actions. No verbs describe what the skill actually does. | 2 / 3 |
Completeness | The description partially addresses 'what' through listed concepts but lacks any explicit 'when' clause or 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 relevant to the domain but are fairly technical. Common user phrases like 'optimize for AI search', 'get cited by AI', or 'AEO' are missing, reducing natural trigger 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, 'page templates' and 'content clusters' could overlap with general SEO or content strategy skills. | 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 contains genuinely useful AEO frameworks—semantic triples, page templates, and content cluster architecture—but suffers severely from verbosity and poor information architecture. Significant portions explain concepts Claude already knows (what AEO is, why it matters, market statistics, how AI engines work), and all content is crammed into a single massive file rather than being split into referenced sub-files. The templates are the strongest element but would benefit from being extracted into separate files with the SKILL.md serving as a concise overview.
Suggestions
Remove the 'Why AEO Matters Now' section, key stats, 'How AI Engines Choose Answers' conceptual explanation, and 'AEO vs Traditional SEO' comparison—Claude already knows these concepts.
Extract the 5 page templates into a separate TEMPLATES.md file and the schema markup examples into a SCHEMA.md file, keeping only a brief overview and links in the main skill file.
Add an explicit creation workflow: e.g., '1. Identify content type → 2. Select template → 3. Draft using triple pattern → 4. Validate against per-page checklist → 5. Verify cluster links exist.'
Consolidate the Quick Reference section and checklists into the primary content rather than repeating patterns that appear earlier in the document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~400+ lines. It includes extensive explanatory content about why AEO matters, market stats, how AI engines work, and AEO vs SEO comparisons—all conceptual knowledge Claude already possesses. The ASCII art boxes, lengthy tables of common mistakes, and repeated pattern explanations significantly inflate token usage without adding actionable value. | 1 / 3 |
Actionability | The templates provide concrete structural patterns (Feature → How → Outcome, semantic triples) and the schema markup examples are copy-paste ready HTML. However, most templates use placeholder brackets rather than fully worked examples, and the guidance is more about content strategy frameworks than executable steps Claude can directly implement. | 2 / 3 |
Workflow Clarity | The checklists (per-paragraph, per-section, per-page, site-wide) provide a clear sequence of validation steps, and the content cluster architecture shows relationships. However, there's no explicit workflow for actually creating AEO content—no step-by-step process like 'first do X, then validate Y, then proceed to Z.' The checklists are verification tools but lack a creation workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with everything inline. Five full page templates, schema examples, comparison tables, measurement guidance, and checklists are all in one file. The templates alone should be in separate referenced files. The header mentions loading with 'base.md + web-content.md + site-architecture.md' but doesn't reference any downstream files for the detailed templates or examples. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%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 (557 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
d4ddb03
- 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.