CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-audit

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

55

Quality

62%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-audit/SKILL.md

The canonical home for this skill is seo-audit in administrakt0r/AI-Agents-Safe-Coding-Skills

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 concrete, well-sequenced audit framework with a precise scoring model and required output format, scoring well on actionability and workflow clarity. Its main weaknesses are verbosity from repeated category listings and a monolithic structure with no reference files for a skill of this length.

Suggestions

De-duplicate the category list and category-breakdown table (define them once and reference them), and consider moving the full scoring model into a references/ file to reduce the SKILL.md footprint.

Add an explicit validation feedback loop for the batch audit (e.g. 'reconcile each finding's evidence before scoring; if the final score conflicts with unresolved Critical issues, re-check deductions').

Tighten the basic-knowledge checklists (Core Web Vitals thresholds, mobile-friendliness, canonical rules) to the non-obvious thresholds and edge cases Claude would not reliably recall.

DimensionReasoningScore

Conciseness

Content is organized as audit checklists rather than concept lectures, but it is notably long (~470 lines) with repetition — the category list appears ~4 times and the category breakdown table is duplicated in the Output Requirements — so it could be tightened; not severely verbose enough for a 2.

3 / 5

Actionability

Highly actionable for an instruction-only skill: exact severity deductions (Critical -15 to -30, High -10), confidence modifiers (Medium 50%, Low 25%), a worked calculation example, and mandatory output fields; minor gaps are in how to concretely gather evidence (no specific commands/API calls), keeping it at 4 rather than 5.

4 / 5

Workflow Clarity

A clear sequence runs Scope Gate -> priority-ordered Audit Framework -> per-category scoring -> Health Index -> band -> findings -> action plan, with checkpoints ('state assumptions', 'flag inconsistency if high score with unresolved Critical issues'); the batch/analysis context lacks an explicit validate->fix->retry loop, so it stops short of 5.

4 / 5

Progressive Disclosure

Internal section structure is well organized with clear headers, but the skill is a monolithic ~470-line file with no bundle references, and content that could be externalized (the ~130-line scoring model, exhaustive checklists) is inlined, fitting 'some structure but content that should be separate is inline'.

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 clearly states what the skill does and uses natural SEO terminology, but it omits any explicit "when to use" trigger clause and relies on only two action verbs. Adding a Use-when clause with concrete triggers would lift completeness and specificity.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to audit SEO health, diagnose ranking or indexing problems, or review crawlability and Core Web Vitals.'

Add one or two more concrete actions (e.g. 'prioritize', 'score') to raise specificity beyond two verbs.

Include common synonyms users say ('SEO audit', 'indexing', 'search ranking', 'organic traffic') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the SEO domain and two concrete actions ("Diagnose and audit") plus four affected areas (crawlability, indexation, rankings, organic performance), but only two verbs are present, fitting '1-2 concrete actions' rather than the 'several' required for a 4.

3 / 5

Completeness

A clear "what" is present ("Diagnose and audit SEO issues affecting...") but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Strong natural keywords a user would say — "SEO", "SEO issues", "crawlability", "indexation", "rankings", "organic performance" — with good coverage; a few synonyms (e.g. "search engine optimization", "indexing", "traffic") are missing, so it stops short of a 5.

4 / 5

Distinctiveness Conflict Risk

"SEO audit" is a mostly distinct niche with low conflict risk against non-SEO skills, though it has minor overlap with closely related SEO sub-skills (programmatic-seo, schema-markup, page-cro) mentioned in the body.

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.

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.