Names the domain (SEO and AI discovery/GEO) and mentions some specific areas like 'schema' and 'ChatGPT/Perplexity optimization', but doesn't list concrete actions (e.g., 'generate structured data markup', 'optimize content for AI citation').

Provides a partial 'what' (SEO and AI discovery optimization) but has no 'when' clause or explicit trigger guidance. The description reads more like a label than a functional description, and the missing 'Use when...' clause caps this at 2 per the rubric, but the 'what' is also weak enough to warrant a 1.

Includes some relevant keywords like 'SEO', 'schema', 'ChatGPT', 'Perplexity', and 'GEO', which users might naturally mention. However, it's missing common variations like 'search engine optimization', 'structured data', 'rich snippets', 'AI search', 'generative engine optimization', or 'LLM visibility'.

The combination of SEO + AI discovery (GEO) + specific platforms (ChatGPT/Perplexity) provides some distinctiveness, but 'SEO' alone is broad and could overlap with general content writing or marketing skills. The mention of specific AI platforms helps narrow it somewhat.

This skill is extremely verbose at ~400+ lines. It explains basic concepts Claude already knows (what SEO is, what E-E-A-T stands for, what a homepage structure looks like, how to write meta descriptions). Much of this is general web content marketing knowledge that doesn't need to be spelled out. The philosophy section, E-E-A-T breakdown, and platform-specific optimization sections are largely common knowledge for Claude. The content could be reduced by 60-70% while preserving all actionable value.

The skill provides concrete schema JSON examples that are copy-paste ready, HTML snippets for stat boxes and TL;DR sections, and a useful analytics tracking script. However, much of the content is template/structural guidance (e.g., 'put a headline here, put a CTA here') rather than executable instructions. The page type templates are more like checklists than actionable code. The schema examples are the strongest actionable element.

The content checklist at the end provides a reasonable workflow for publishing, and the page type templates give a sequence of sections. However, there's no clear end-to-end workflow for creating a page from scratch — no 'Step 1: Choose page type, Step 2: Generate schema, Step 3: Validate schema, Step 4: Write content sections.' The schema validation step is mentioned but only as external URLs with no feedback loop for fixing issues.

This is a monolithic wall of content with no references to supporting files. All schema examples, all page templates, all platform-specific guidance, analytics code, and checklists are inlined in a single massive document. The schema examples alone could be in a separate SCHEMAS.md, page templates in TEMPLATES.md, and platform-specific tips in PLATFORMS.md. The external source links at the top are references, not structured bundle files.