CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-audit

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body delivers a genuinely useful, concrete audit methodology — a fully specified scoring model with worked example, mandatory evidence-based finding fields, and a derived action plan. Its weaknesses are restating standard SEO knowledge at length in a monolithic file with inconsistent heading structure, and leaving evidence-gathering guidance at the tool-name level.

Suggestions

Trim the standard-SEO checklist sections that restate knowledge Claude already has (Core Web Vitals thresholds, title/meta/heading best practices), keeping only what defines audit scope, and remove the filler trailing "When to Use" section.

Split the ~170-line scoring layer (weights, deductions, bands, output template) into a reference file (e.g., references/scoring.md) and keep SKILL.md as a lean overview, fixing the inconsistent heading hierarchy.

Define the Executive Summary the output ordering depends on, and add one or two concrete evidence-gathering checks per category (e.g., how to verify robots.txt blocking or inspect canonical tags) instead of tool names alone.

DimensionReasoningScore

Conciseness

The custom scoring model, deduction rules, and mandatory findings fields earn their tokens, but large checklist stretches restate standard SEO knowledge Claude already has ("LCP < 2.5s", "INP < 200ms", "CLS < 0.1", "Title Tags: Unique per page, Keyword-aligned", "Proper viewport configuration"), and the trailing "This skill is applicable to execute the workflow or actions described in the overview" is pure filler. Mostly efficient, but could be tightened significantly.

3 / 5

Actionability

As an instruction-only skill it gives concrete, executable guidance: exact category weights (30/25/20/15/10), severity deduction ranges (−15 to −30), confidence modifiers (50%/25%), a fully worked numeric example ("100 − 29.5 = 70.5", "70.5 × 0.30 = 21.15"), mandatory finding fields, and an output template. Minor gaps remain: evidence gathering stops at tool names with no concrete checks, and the "Executive Summary" referenced in output ordering is never defined.

4 / 5

Workflow Clarity

A coherent multi-step sequence is present (scope gate → priority-ordered audit framework → classified findings → derived action plan → output requirements) with checkpoints such as "state assumptions explicitly" and "A high score with unresolved Critical issues is invalid → flag inconsistency". It falls short of a 5 because there is no explicit feedback/validation loop for the audit process itself and the output section ordering is only partially specified.

4 / 5

Progressive Disclosure

The skill is a single ~480-line monolith with no bundle files; the ~170-line scoring layer and per-category checklists clearly belong in separate reference files. Internal section structure is clear and nothing is nested or buried, but content that should be split out is inlined and heading hierarchy is inconsistent (### sections with no ## parent, a trailing filler "When to Use" section).

3 / 5

Total

14

/

20

Passed

Description

61%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.

The description is concise, domain-specific, and names the key SEO areas affected, but it omits any "Use when..." trigger guidance and relies on two generic verbs. Adding an explicit trigger clause and enumerating more of the skill's concrete outputs (health index, prioritized findings, action plan) would lift both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to audit, diagnose, or improve a site's SEO, rankings, or organic traffic, or mentions crawlability or indexation problems."

Enumerate the skill's concrete deliverables in the description (SEO Health Index score, evidence-based findings, prioritized action plan) instead of the generic verbs "diagnose and audit".

Include common user phrasings such as "site audit", "organic traffic", and "search visibility" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Diagnose and audit" are two fairly generic verbs, though the affected areas "crawlability, indexation, rankings, and organic performance" are concretely named. It does not list the multiple specific actions the skill actually performs (prioritizing, scoring, action planning, reporting), so it sits at the 1-2 concrete actions level rather than the several-specific-actions level.

3 / 5

Completeness

The description clearly answers "what" (diagnose and audit SEO issues) but contains no "Use when..." clause or any equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural keywords like "SEO", "crawlability", "indexation", "rankings", and "organic performance" cover the domain well. A few common user phrasings are missing (e.g., "SEO audit", "site audit", "organic traffic", "search visibility"), which keeps it below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The diagnostic/audit niche is mostly distinct from implementation-oriented SEO skills, but the description's generic SEO vocabulary alone could trigger sibling skills such as programmatic-seo or schema-markup, leaving minor overlap risk rather than a clear niche with distinct triggers.

4 / 5

Total

14

/

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/seo-audit/SKILL.md

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.