CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-audit

Audit technical, on-page, and AI-search SEO for pages, sites, and content. Use when the user asks for `/seo-audit`, `/ai-seo`, SEO review, keyword targeting, heading structure, metadata, internal linking, content gaps, AEO, GEO, LLMO, or competitor SEO comparisons.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-organized instruction-only skill with a clear workflow and output structure that wastes no tokens. Its main weakness is actionability: it specifies what to audit in concrete terms but provides no commands, tools, or procedures for how to inspect rendered HTML, verify structured data, or check robots directives.

Suggestions

Add concrete inspection methods to the workflow steps — e.g., a curl or tool command for fetching rendered HTML, a specific structured-data validator, and a way to check robots directives and redirects — so each step is executable rather than descriptive.

Define a severity or impact rubric for the 'prioritized fix list' (e.g., how to classify critical vs. minor findings) so the deliverable step produces consistent output.

Include one worked mini-example of an output finding (e.g., a weak title tag with a concrete suggested rewrite) to anchor the 'concrete edits' promised in step 7.

DimensionReasoningScore

Conciseness

The ~37-line body assumes Claude's competence: no explanation of what SEO is, why metadata matters, or how search engines work. Every section (Overview, Workflow, Output Pattern, Example Prompts) directs behavior rather than teaching background, matching the 'lean and efficient; every token earns its place' anchor. There is no padding to trim, so 4 or below is ruled out.

5 / 5

Actionability

The workflow names concrete audit items ("Title, meta description, H1/H2 structure, URL, canonical, alt text, schema, and internal links") and a defined output structure, which is genuine concrete guidance — but it gives no how: no commands, tools, or methods for fetching rendered HTML, checking robots directives, or validating structured data. This matches 'some concrete guidance but incomplete; missing key details'. It is above 2 because the checklists and output pattern are specific, not high-level hints, but below 4 because none of the steps are executable as written.

3 / 5

Workflow Clarity

Seven clearly sequenced steps run from target identification through inspection, on-page and technical audits, AI-search and competitor analysis, to a defined deliverable, plus an explicit output pattern — a clear sequence with only a minor gap (no checkpoint such as confirming rendered HTML was actually retrieved before auditing). It is below 5 because there are no explicit validation steps, and above 3 because the sequence is complete, ordered, and specific rather than merely listed with implicit checkpoints. The destructive/batch cap does not apply since this is a read-only audit.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed, and content is organized into four well-signaled sections — per the rubric guideline, this earns a 5 on well-organized sections alone. There are no buried or nested references, and no inlined content that belongs in a separate file, ruling out lower anchors.

5 / 5

Total

17

/

20

Passed

Description

91%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 in third-person voice that explicitly covers both what the skill does and when to use it, with an unusually comprehensive set of natural trigger terms including AI-search synonyms. The only gaps are unstated deliverables in the what-clause and minor trigger overlap with adjacent content-marketing skills.

DimensionReasoningScore

Specificity

"Audit technical, on-page, and AI-search SEO for pages, sites, and content" lists three concrete, parallel audit actions, matching the anchor 'lists several specific actions; minor gaps in coverage' (e.g. 'Extracts text, fills forms, converts pages'). It falls short of 5 because the what-clause stops at audit categories without naming deliverables or audit depth, and is above 3 because it names several specific actions rather than only 1-2.

4 / 5

Completeness

It explicitly answers what ("Audit technical, on-page, and AI-search SEO for pages, sites, and content") and when ("Use when the user asks for...") with concrete trigger phrases, exactly matching the level-5 anchor exemplar structure. Neither element is missing or only implied, ruling out 4 and below.

5 / 5

Trigger Term Quality

The when-clause packs natural user phrasing ("SEO review", "keyword targeting", "heading structure", "metadata", "internal linking", "content gaps", "competitor SEO comparisons"), slash commands (/seo-audit, /ai-seo), and acronym synonyms (AEO, GEO, LLMO) — comprehensive coverage including synonyms, matching the level-5 anchor. Only marginal terms like "SERP" or "search rankings" are absent, which does not drop it to the 'a few natural terms missing' level 4 anchor.

5 / 5

Distinctiveness Conflict Risk

SEO auditing is a clear niche with distinct triggers (/seo-audit, AEO, GEO, LLMO), but broadly applicable terms like "metadata", "content gaps", and "keyword targeting" create minor overlap risk with content-strategy or marketing skills — the level-4 anchor ('mostly distinct; minor overlap risk with closely related skills'). Not 5 because that overlap is real; not 3 because the core triggers would not fire for unrelated skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
eigent-ai/agent-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.