seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
88
Quality
87%
Does it follow best practices?
Impact
88%
1.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 description with excellent trigger term coverage and clear differentiation from related skills. The main weakness is the lack of specific concrete actions - it describes the general purpose (audit/review/diagnose) but doesn't enumerate what specific SEO checks or analyses the skill performs.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Analyzes meta tags, checks page speed issues, identifies broken links, reviews heading hierarchy, evaluates mobile-friendliness'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO) and general actions ('audit, review, or diagnose SEO issues') but doesn't list specific concrete actions like 'analyze meta tags, check page speed, identify broken links, review heading structure.' | 2 / 3 |
Completeness | Clearly answers both what ('audit, review, or diagnose SEO issues') and when ('Use when the user mentions...' with explicit trigger list). Also helpfully distinguishes from related skills (programmatic-seo, schema-markup). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'SEO audit,' 'technical SEO,' 'why am I not ranking,' 'SEO issues,' 'on-page SEO,' 'meta tags review,' 'SEO health check' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly differentiates from related skills (programmatic-seo for building pages, schema-markup for structured data) and has distinct trigger terms focused specifically on SEO auditing/diagnosis rather than creation or implementation. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive SEO audit skill with excellent actionability and workflow clarity. The priority-ordered framework and specific checklists make it immediately usable. Minor improvements could come from trimming some explanatory content that Claude already knows (like what E-E-A-T stands for) to improve token efficiency.
Suggestions
Trim E-E-A-T section to just the checklist items without explaining what each letter means—Claude knows this
Consolidate repeated 'Common issues' patterns into a single reference section to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy and could be tightened. Lists like 'Common issues' repeat patterns, and some sections (e.g., E-E-A-T explanations) explain concepts Claude likely knows. However, it avoids excessive verbosity and most content is actionable. | 2 / 3 |
Actionability | Provides highly specific, actionable checklists with concrete metrics (LCP < 2.5s, CLS < 0.1), exact checks to perform (site:domain.com), specific tools to use, and clear output format structure. Each audit area has explicit items to verify. | 3 / 3 |
Workflow Clarity | Clear priority order (Crawlability → Technical → On-Page → Content → Authority) with explicit sequencing. The audit framework provides logical progression, and the output format section gives a structured approach with prioritized action plans including critical fixes first. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, references to external files (ai-writing-detection.md, aeo-geo-patterns.md), and related skills clearly signaled at the end. Content is appropriately structured with headers enabling easy navigation without deep nesting. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.