The description names the domain (SEO auditing) and some actions like 'audit, review, or diagnose SEO issues,' but doesn't list specific concrete actions such as 'check meta tags, analyze page speed scores, identify crawl errors, review heading structure.' The actions remain somewhat high-level.

Clearly answers both 'what' (audit, review, diagnose SEO issues) and 'when' with an extensive explicit trigger list. It also helpfully distinguishes itself from related skills (programmatic-seo, schema-markup, ai-seo) with cross-references.

Excellent coverage of natural trigger terms users would actually say, including conversational phrases like 'why am I not ranking,' 'my traffic dropped,' 'not showing up in Google,' 'my SEO is bad,' alongside technical terms like 'core web vitals,' 'crawl errors,' and 'indexing issues.'

Explicitly differentiates itself from related skills (programmatic-seo, schema-markup, ai-seo) with clear boundary statements. The focus on auditing/diagnosing creates a distinct niche, and the cross-references reduce conflict risk significantly.

The skill is extremely verbose at ~350+ lines, with extensive lists of things Claude already knows (what E-E-A-T stands for, what meta descriptions are, what HTTPS is, basic image optimization concepts). Much of this is textbook SEO knowledge that doesn't need to be spelled out — Claude already knows what title tags, heading hierarchy, and canonical tags are. The 'Common Issues by Site Type' section alone is largely general knowledge.

The skill provides checklists and structured categories but lacks executable code or commands. There are no concrete examples of how to actually perform checks (e.g., curl commands to check robots.txt, scripts to validate sitemaps, specific Search Console API calls). The Schema Markup Detection Limitation section is one of the few genuinely actionable parts with a specific JS snippet. Most guidance is 'check for X' without showing how.

The audit framework provides a priority order (Crawlability → Technical → On-Page → Content → Authority) and the output format section gives a clear report structure with a prioritized action plan. However, there are no validation checkpoints, no feedback loops for verifying fixes, and no explicit sequencing of how to actually conduct the audit step-by-step. The 'Initial Assessment' section is a good starting point but the rest reads more like a reference checklist than a workflow.

The skill references two external files (references/ai-writing-detection.md and related skills like ai-seo, programmatic-seo, etc.), which is good. However, the massive amount of inline content (E-E-A-T details, common issues by site type, full on-page audit checklists) could easily be split into separate reference files. The skill tries to be both an overview and a comprehensive reference, resulting in a monolithic document.