seo-aeo-audit
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.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/seo-aeo-audit/SKILL.mdQuality
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 solid skill description that clearly communicates its purpose and includes an explicit 'Use when' clause with good trigger terms. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'optimize' — for example, listing specific tasks like auditing page titles, generating schema markup, or improving heading structure. Overall it performs well for skill selection purposes.
Suggestions
Expand the capability list with more concrete actions, e.g., 'audit page titles, generate schema markup, optimize heading structure, improve page speed recommendations' to increase specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO/AEO) and mentions some actions like 'fix meta tags' and 'add structured data', but the primary clause 'Optimize for search engine visibility, ranking, and AI citations' is fairly high-level rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize for search engine visibility, ranking, and AI citations) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'SEO', 'optimize for search', 'meta tags', 'structured data', 'AEO', 'AI visibility', 'search engine visibility', and 'ranking'. Good coverage of both common and emerging terms. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of SEO, AEO, meta tags, structured data, and AI citations creates a clear niche that is unlikely to conflict with other skills. The domain is well-defined and distinct. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent concrete examples and copy-paste ready code, but suffers significantly from verbosity — it's a comprehensive reference document rather than a lean skill file. Much of the content covers standard web development knowledge Claude already possesses (basic HTML meta tags, heading hierarchy, image alt text). The AEO section, while valuable in concept, adds substantial bulk with market statistics and platform-specific tone guidance that could be better served in a separate reference file.
Suggestions
Reduce the main file to ~100-150 lines by moving structured data templates, mobile SEO basics, and detailed AEO platform examples into separate reference files (e.g., references/structured-data.md, references/aeo-guide.md)
Remove explanations of concepts Claude already knows (what HTTPS is, why alt text matters, heading hierarchy basics) and keep only the project-specific guidelines and non-obvious patterns
Add explicit validation checkpoints to the audit workflow, e.g., 'Run Lighthouse SEO audit — if score < 90, address all red items before proceeding to structured data'
Cut the AEO market statistics (Gartner predictions, user counts) which are time-sensitive and don't provide actionable implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At ~500+ lines, this skill is extremely verbose. It explains basic concepts Claude already knows (what HTTPS is, what alt text is, what hyphens vs underscores are), includes extensive example markup that is largely standard knowledge, and the AEO section adds significant bulk with marketing-style explanations of market trends and platform differences that don't provide actionable implementation guidance. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout: complete robots.txt configurations, HTML meta tags, JSON-LD structured data templates, CSS examples, XML sitemaps, and bash script invocations. Every section includes concrete, specific examples rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The audit workflow section provides a 6-step sequence and the checklists are well-organized by priority, but there are no explicit validation checkpoints or feedback loops (e.g., 'if Lighthouse score is below X, fix Y before proceeding'). The workflow is more of a task list than a guided process with error recovery. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/json-ld-templates.md, scripts/, other SKILL.md files) which is good, but the main file itself is monolithic with enormous amounts of inline content that could be split into separate reference files. The structured data templates alone could be a separate reference document, significantly reducing the main file's length. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 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 | 10 / 11 Passed | |
- Repository
- warpdotdev/oz-skills
- Commit
6c08c49
- 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.