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," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

77

1.06x
Quality

70%

Does it follow best practices?

Impact

88%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./config/claude/skills/seo-audit/SKILL.md

The canonical home for this skill is seo-audit in coreyhaines31/marketingskills

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

A well-organized, comprehensive SEO audit checklist with concrete criteria and a clear prioritized workflow, but it is token-heavy with largely standard SEO knowledge, lacks executable procedures, and keeps most detail inline rather than progressively disclosed.

Suggestions

Tighten the body by pruning basic SEO best-practice bullets Claude already knows (e.g., generic title-tag and alt-text advice), retaining only skill-specific thresholds and non-obvious checks to improve conciseness.

Add explicit verification checkpoints to the workflow (e.g., 'confirm findings against Search Console evidence before reporting') to lift workflow_clarity above 2.

Move the per-site-type common issues and tools lists into reference files (linked one level deep) so SKILL.md reads as an overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Structured as tight checklists rather than prose padding, but ~390 lines largely restate standard SEO basics Claude already knows (title tag lengths, heading hierarchy, alt text); it could be tightened without losing value.

2 / 3

Actionability

Provides concrete audit thresholds (LCP < 2.5s, INP < 200ms, 50-60 char titles) and specific checks, but stays at the 'what to check' level with no executable commands or scripts, matching the score-2 anchor's incomplete-but-concrete guidance.

2 / 3

Workflow Clarity

A clear prioritized framework (1-5 priority order), an initial-assessment phase, and a defined output format with an action plan are present, but there are no explicit validation/verification checkpoints, capping it at 2.

2 / 3

Progressive Disclosure

Two real, one-level-deep references are clearly signaled with descriptions, and the body is well-organized by headings, but the bulk of the detailed checklist content remains inline in SKILL.md rather than being split into reference files.

2 / 3

Total

8

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit trigger terms, clear what/when coverage, and effective disambiguation from neighboring skills. The only weakness is that its action verbs are variations of one general activity rather than a list of distinct concrete operations.

DimensionReasoningScore

Specificity

Names the SEO domain and several actions ('audit, review, or diagnose SEO issues'), but these are variations of a single general action rather than multiple distinct concrete actions as in the score-3 anchor.

2 / 3

Completeness

Explicitly answers both what ('audit, review, or diagnose SEO issues') and when ('Use when the user mentions...') with explicit triggers, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases users would say — 'SEO audit,' 'technical SEO,' 'why am I not ranking,' 'on-page SEO,' 'meta tags review,' 'SEO health check' — matching the score-3 anchor's breadth.

3 / 3

Distinctiveness Conflict Risk

Clear SEO-audit niche with explicit boundary-setting ('For building pages at scale... see programmatic-seo. For adding structured data, see schema-markup.'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
freekmurze/dotfiles
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.