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.

87

1.06x
Quality

85%

Does it follow best practices?

Impact

88%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A well-organized, actionable SEO audit checklist with specific thresholds, a clear priority-ordered workflow, and properly signaled one-level-deep references. Main improvement areas are tightening auxiliary sections and making verification of findings more explicit.

Suggestions

Trim or relocate the 'Tools Referenced' and 'Task-Specific Questions' sections, which add length without advancing the audit itself.

Add an explicit verification step (e.g., cross-check findings against Search Console data before reporting) to strengthen workflow checkpoints.

Consider moving the 'Common Issues by Site Type' detail into a reference file to reduce inline length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a dense, bullet-style checklist that assumes Claude knows what Core Web Vitals, robots.txt, and canonicals are without explaining them; minor trim opportunities exist in 'Tools Referenced' and 'Task-Specific Questions' sections.

4 / 5

Actionability

Concrete, specific guidance with numeric thresholds ('LCP < 2.5s', '50-60 characters', 'One H1 per page') and a structured report format, but it tells Claude what to check rather than providing runnable commands for most checks.

4 / 5

Workflow Clarity

Clear sequence via 'Initial Assessment' → priority-ordered 'Audit Framework' → structured 'Output Format' with a prioritized action plan; validation checkpoints are implicit rather than explicit, which is acceptable for a read-only diagnostic skill.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references to real bundle files (ai-writing-detection.md, aeo-geo-patterns.md) with descriptive labels, and clear section headers throughout; the large inlined checklist could split some detail (e.g., per-site-type issues) into references.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 what/when structure, rich natural trigger terms, and clear disambiguation from sibling skills. The only minor weakness is that the named actions are somewhat synonymous rather than a set of distinct capabilities.

DimensionReasoningScore

Specificity

Names the SEO domain and several concrete actions ('audit, review, or diagnose SEO issues'), though the three verbs overlap as near-synonyms rather than distinct capabilities, leaving minor gaps versus a comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ('audit, review, or diagnose SEO issues') and when ('Also use when the user mentions...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including 'SEO audit,' 'technical SEO,' 'why am I not ranking,' 'on-page SEO,' and 'SEO health check' — terms a user would genuinely say, with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche with explicit boundary clauses ('For building pages at scale... see programmatic-seo'; 'For adding structured data... see schema-markup') that minimize conflict with adjacent skills.

5 / 5

Total

19

/

20

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.