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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/seo-audit/SKILL.md
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 audit framework that uses concrete thresholds and checklists effectively and assumes Claude's competence. The main gaps are the duplicated schema-detection caveat and the absence of explicit validation/error-recovery feedback loops in the workflow.

DimensionReasoningScore

Conciseness

Mostly lean checklist/bullet structure that assumes Claude's competence and avoids explaining SEO basics; the only redundancy is the schema-detection limitation being stated both in a dedicated section and repeated in the Tools note.

4 / 5

Actionability

Provides concrete thresholds (LCP < 2.5s, INP < 200ms, CLS < 0.1), specific checklists, and an executable JS snippet for schema detection, though much of the guidance is descriptive 'check for...' items rather than copy-paste-ready commands.

4 / 5

Workflow Clarity

Clear sequenced audit framework (priority order, then per-area checklists, then report structure and prioritized action plan) with implicit verification via the listed detection methods; explicit error-recovery feedback loops are not spelled out but the skill is diagnostic rather than destructive.

4 / 5

Progressive Disclosure

Well-sectioned body with one real one-level-deep reference (ai-writing-detection.md) clearly signaled with a one-line description; the body is long but appropriately so for a checklist framework, with only minor inline-vs-split organization gaps.

4 / 5

Total

16

/

20

Passed

Description

77%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 trigger-rich, well-scoped description that clearly signals when to invoke the skill and disambiguates it from related SEO skills. The 'what does it do' half is thinner than the 'when' half, listing only a couple of generic actions rather than a comprehensive concrete action set.

DimensionReasoningScore

Specificity

Names the SEO domain and 1-2 concrete actions ('audit, review, or diagnose SEO issues', 'improve organic search performance') but stops short of listing multiple specific concrete actions, leaning heavily on trigger phrases instead.

3 / 5

Completeness

Both 'what' and 'when' are explicit with concrete trigger phrases, but the 'what' is generic relative to the anchor-5 example which lists multiple distinct concrete actions.

4 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and vernacular phrases ('why am I not ranking', 'my traffic dropped', 'not showing up in Google', 'core web vitals', 'crawl errors', 'indexing issues') plus vague-user fallbacks like 'my SEO is bad'.

5 / 5

Distinctiveness Conflict Risk

Clear SEO-audit niche with explicit redirects to sibling skills (programmatic-seo, schema-markup, ai-seo) that reduce overlap risk, though minor overlap with those siblings remains.

4 / 5

Total

16

/

20

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.