Optimize for search engine visibility, ranking, and AI citations. Use when asked to improve SEO, optimize for search, fix meta tags, add structured data, or improve AEO and AI visibility.
85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong trigger terms and explicit 'Use when' guidance. The main weakness is that the capabilities could be more specific - listing concrete actions like 'analyze page titles, optimize headings, generate schema markup' would strengthen the specificity dimension. Overall, it effectively communicates when Claude should select this skill.
Suggestions
Expand the capabilities section with more concrete actions like 'analyze page titles, optimize headings, generate schema markup, audit internal links' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO/search optimization) and mentions some actions like 'fix meta tags, add structured data', but doesn't comprehensively list concrete capabilities like keyword research, content optimization, sitemap generation, etc. | 2 / 3 |
Completeness | Clearly answers both what ('Optimize for search engine visibility, ranking, and AI citations') and when ('Use when asked to improve SEO, optimize for search, fix meta tags, add structured data, or improve AEO and AI visibility') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'SEO', 'optimize for search', 'meta tags', 'structured data', 'AEO', 'AI visibility', 'search engine visibility', 'ranking'. These are terms users naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on SEO and AEO optimization with distinct triggers like 'meta tags', 'structured data', 'AI citations' that are unlikely to conflict with other skills. The combination of SEO and AEO focus creates a unique scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable SEO/AEO skill with excellent concrete examples and clear workflows. The main weakness is length—the skill tries to be both a quick reference and a complete guide, resulting in a document that could be better organized with progressive disclosure. The content quality is high but token efficiency suffers from the monolithic structure.
Suggestions
Extract JSON-LD schema templates to a separate 'references/json-ld-templates.md' file as the content already references, keeping only one example inline
Move the detailed AEO platform-specific optimization section to a separate 'AEO.md' file, keeping a brief summary and link in the main skill
Remove some of the ❌/✅ comparison examples where the 'bad' pattern is obvious to Claude (e.g., generic titles, missing alt text)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what good/bad URLs look like when Claude knows URL best practices). The AEO section adds valuable new content but could be tighter in places with repetitive platform-specific examples. | 2 / 3 |
Actionability | Excellent actionability with copy-paste ready code examples throughout: robots.txt, meta tags, JSON-LD schemas, CSS snippets, and shell commands. Every section provides concrete, executable guidance rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | Clear audit workflow with numbered steps (baseline → crawl → fix → on-page → structured data → re-verify). Multiple checklists organized by priority (Critical/High/Medium/Ongoing) provide explicit validation checkpoints. The AEO audit checklist follows the same clear pattern. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~600 lines) and could benefit from splitting detailed schema templates and platform-specific AEO guidance into separate reference files. References to external tools and other skills are present, but inline content is dense. The mention of 'references/json-ld-templates.md' suggests intended structure but templates are inline anyway. | 2 / 3 |
Total | 10 / 12 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.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (753 lines); consider splitting into references/ and linking | Warning |
Total | 15 / 16 Passed | |
Table of Contents
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.