CtrlK
BlogDocsLog inGet started
Tessl Logo

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," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

56

Quality

62%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

35%

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

This skill functions more as a comprehensive SEO audit reference manual than a concise, actionable skill file. Its greatest strength is the schema markup detection limitation warning and the international SEO detail, which contain genuinely non-obvious information. However, the vast majority of content covers standard SEO knowledge that Claude already possesses, making it extremely token-inefficient. The checklist format provides structure but lacks executable commands, validation steps, and decision-tree logic that would make it truly actionable.

Suggestions

Reduce the body to ~100 lines focusing on: (1) the initial assessment workflow, (2) audit priority order with brief descriptions, (3) non-obvious gotchas like schema detection limitations, and (4) the output format. Move all detailed checklists (technical SEO, on-page, content quality, site-type issues) into reference files.

Add concrete executable examples — e.g., specific curl commands to check robots.txt, sitemap validation commands, or code snippets to parse Search Console data — rather than abstract checklists like 'check for unintentional blocks'.

Add validation checkpoints and decision logic to the workflow: e.g., 'After crawlability check, if >10% of pages are not indexed, STOP and prioritize indexation fixes before proceeding to on-page audit.'

Remove sections that explain concepts Claude already knows well (E-E-A-T definitions, what title tags are, what HTTPS is, what alt text is) and replace with only the non-obvious checks and common mistakes specific to each area.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines, with extensive checklist-style content that Claude already knows (what title tags are, what meta descriptions are, what E-E-A-T stands for, basic HTTPS concepts). Sections like 'Security & HTTPS', 'URL Structure', 'Mobile-Friendliness', and 'Content Quality Assessment' explain fundamental SEO concepts that add little value for an AI that already understands them. The international SEO section alone is massive and could be entirely in a reference file.

1 / 3

Actionability

The skill provides structured checklists and specific thresholds (e.g., LCP < 2.5s, CLS < 0.1) which are useful, and the schema markup detection limitation is a genuinely actionable insight. However, there are no executable code examples, no specific commands to run, and most guidance is checklist-style ('check for X') rather than concrete steps with tool invocations. The audit is more of a reference document than executable instructions.

2 / 3

Workflow Clarity

The priority order (Crawlability → Technical → On-Page → Content → Authority) provides a clear sequence, and the output format section gives good structure for deliverables. However, there are no validation checkpoints, no feedback loops for when issues are found, and no explicit decision points (e.g., 'if X then do Y, otherwise skip'). The initial assessment section is well-structured but the audit itself reads as a flat checklist rather than a guided workflow.

2 / 3

Progressive Disclosure

The skill references external files (references/international-seo.md, references/ai-writing-detection.md) and related skills appropriately, but the main body contains enormous amounts of detail that should be in reference files — particularly the full international SEO section, the complete on-page audit checklists, and the site-type-specific issues. The content that IS inline is far too much for a SKILL.md overview. No bundle files were provided to verify references exist.

2 / 3

Total

7

/

12

Passed

Description

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 description with exceptional trigger term coverage and completeness. The cross-references to related skills are a notable strength for distinctiveness. The main weakness is that the 'what' portion could be more specific about the concrete actions performed during an audit (e.g., checking meta tags, analyzing page speed, reviewing internal links) rather than staying at the high level of 'audit, review, diagnose.'

Suggestions

Add 2-3 more specific concrete actions to the 'what' portion, e.g., 'Audits meta tags, analyzes page speed and core web vitals, identifies crawl and indexing errors, reviews heading structure and internal linking.'

DimensionReasoningScore

Specificity

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.

2 / 3

Completeness

Clearly answers both 'what' (audit, review, diagnose SEO issues) and 'when' with an extensive explicit trigger list and a 'Use when' equivalent clause. Also includes helpful cross-references to related skills (programmatic-seo, schema, ai-seo) to clarify boundaries.

3 / 3

Trigger Term Quality

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,' plus technical terms like 'core web vitals,' 'crawl errors,' 'indexing issues,' and 'meta tags review.'

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with explicit boundary-setting via cross-references to related skills (programmatic-seo for page building, schema for structured data, ai-seo for AI search). The specific trigger terms clearly carve out the audit/diagnostic niche and reduce conflict risk.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.