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-markup. For AI search optimization, see ai-seo.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

An actionable, well-structured audit playbook with strong concrete thresholds and a clear report format, plus good progressive disclosure via one well-signaled reference. It loses points on conciseness from duplicated content and on workflow clarity, since it is organized as a topical checklist rather than an explicitly sequenced procedure with validation checkpoints.

Suggestions

Remove the duplicated schema-detection-limitation content — keep it in one place (the Audit Framework section) and have the Tools section reference it once.

Delete or fold the 'Task-Specific Questions' section, which restates the Initial Assessment questions, to reduce redundancy.

Reframe the audit as an explicitly numbered procedure (gather context → run priority-ordered checks → produce prioritized action plan) with a verification step confirming findings before reporting, to raise workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient checklists with valuable specifics Claude would not reliably recall (LCP <2.5s, title 50-60 chars), but the schema-detection limitation is explained twice and 'Task-Specific Questions' repeats the Initial Assessment content, so it could be tightened.

2 / 3

Actionability

Provides concrete thresholds, executable commands like document.querySelectorAll('script[type="application/ld+json"]') and site:domain.com, named tools, and a copy-ready Issue/Impact/Evidence/Fix/Priority report format.

3 / 3

Workflow Clarity

A priority-ordered audit framework and structured output format give a usable sequence, but the body reads more as a topical reference checklist than a numbered procedure with explicit checkpoints; validation feedback loops are not articulated.

2 / 3

Progressive Disclosure

The single references/ai-writing-detection.md file is linked once in the body with a clear inline description and is one level deep; the Related Skills section cleanly routes to sibling skills, matching the actual bundle structure.

3 / 3

Total

10

/

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 excellent trigger-term coverage, clear when/what guidance, and good disambiguation from sibling skills. Its only weakness is that the stated actions are near-synonyms (audit/review/diagnose) rather than a richer set of distinct concrete capabilities.

Suggestions

Add a few more distinct concrete actions beyond audit/review/diagnose (e.g., 'prioritize fixes,' 'generate a remediation plan,' 'benchmark against competitors') to strengthen the specificity dimension.

Consider trimming the long quoted trigger list slightly to avoid verbosity without losing natural coverage.

DimensionReasoningScore

Specificity

Names the SEO domain and the actions 'audit, review, or diagnose SEO issues,' but these are near-synonyms rather than multiple distinct concrete actions, so it falls short of the comprehensive multi-action anchor.

2 / 3

Completeness

Explicitly states what it does (audit/review/diagnose SEO issues) and when to use it via a 'Use when...' clause with many triggers, including handling of vague phrasings.

3 / 3

Trigger Term Quality

Broad, natural coverage of phrases users actually say — 'SEO audit,' 'why am I not ranking,' 'my traffic dropped,' 'page speed,' 'crawl errors,' plus vague 'my SEO is bad'/'help with SEO.'

3 / 3

Distinctiveness Conflict Risk

Clear SEO niche with distinct triggers and explicit disambiguation against adjacent skills (programmatic-seo, schema-markup, ai-seo), making misfiring unlikely.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
databricks/devhub
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.