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.

1.06x

Quality

62%

Does it follow best practices?

Impact

88%

1.06x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/seo-audit/SKILL.md

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 strong skill description with excellent trigger term coverage and clear differentiation from related skills. The cross-references to programmatic-seo and schema-markup are a notable strength. The main weakness is that the 'what' portion could be more specific about the concrete actions performed during an SEO audit.

Suggestions

Add more specific concrete actions to the 'what' portion, e.g., 'Audits meta tags, checks crawlability, analyzes page speed, reviews internal linking, and identifies on-page SEO issues' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (SEO) and some actions ('audit, review, or diagnose SEO issues'), but does not list multiple specific concrete actions like checking meta tags, analyzing page speed, reviewing crawlability, etc. The actions remain somewhat high-level.	2 / 3
Completeness	Clearly answers both 'what' (audit, review, diagnose SEO issues) and 'when' (explicit 'Use when' equivalent with detailed trigger terms). It also includes helpful cross-references to related skills (programmatic-seo, schema-markup) to reduce confusion.	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.' The phrase 'why am I not ranking' is particularly good as a natural user query.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche (SEO auditing/diagnosis) and explicitly differentiates itself from related skills like programmatic-seo and schema-markup, significantly reducing conflict risk.	3 / 3
	Total	11 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads like a comprehensive SEO textbook rather than a targeted skill for Claude. It is heavily padded with concepts Claude already understands (what title tags are, what HTTPS is, what alt text does) and lacks executable code, concrete examples of audit output, or specific tool commands. The structure is reasonable but the content-to-signal ratio is very low — most of this could be condensed to ~50 lines of genuinely novel guidance.

Suggestions

Drastically reduce content to only what Claude doesn't already know — remove explanations of basic SEO concepts (meta descriptions, HTTPS, alt text) and focus on the specific audit methodology, decision trees, and output format.

Add concrete, executable examples: a sample audit output for a specific page, example commands for checking robots.txt or running PageSpeed API calls, or a template showing exactly what the final report should look like.

Move the 'Common Issues by Site Type' and detailed checklists (Technical SEO, On-Page SEO) into separate reference files and link to them from the main skill, keeping only the priority framework and workflow inline.

Add validation checkpoints to the workflow — e.g., 'After crawlability check, confirm X before proceeding to technical foundations' — to create a proper feedback loop rather than a flat checklist.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines, largely consisting of checklist items and concepts Claude already knows well (what meta descriptions are, what HTTPS is, what alt text is). Most of the content reads like a generic SEO textbook rather than adding novel, Claude-specific guidance. Sections like 'Security & HTTPS' and 'Mobile-Friendliness' explain basic web concepts that don't need enumeration.	1 / 3
Actionability	The skill provides structured checklists and specific metrics (e.g., LCP < 2.5s, 50-60 character titles), which is somewhat actionable. However, there are no executable code snippets, no concrete commands to run, and no specific examples of audit output. It describes what to check rather than how to check it programmatically.	2 / 3
Workflow Clarity	There is a clear priority order (Crawlability → Technical → On-Page → Content → Authority) and a structured output format. However, there are no validation checkpoints, no feedback loops for error recovery, and no explicit sequencing of steps within each audit phase. The workflow is more of a checklist than a guided process.	2 / 3
Progressive Disclosure	The skill references two files in a 'References' section (ai-writing-detection.md, aeo-geo-patterns.md) and links to related skills, showing some progressive disclosure. However, the massive amount of inline content (common issues by site type, E-E-A-T signals, detailed on-page checklists) should be split into separate reference files rather than included in the main SKILL.md. No bundle files were provided to verify reference accuracy.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: tibelf/ai_project_init
Commit: 56f4516

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

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.