seo-audit

Audit a website and deliver a one-page, plain-language SEO report anyone can act on, centered on a single do-this-week action.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/seo-audit/SKILL.md

Quality

Content

88%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 is a tightly written, highly actionable instruction skill with a well-sequenced, validated workflow and strong guardrails. Its only real weakness is progressive disclosure: it points to a template.html that is not present in the bundle.

Suggestions

Ship the referenced template.html (or remove the reference and inline the report skeleton) so the Output format section's navigation target actually resolves.

Tighten a few guardrail bullets that restate obvious rules to nudge conciseness from 4 to 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient and does not explain concepts Claude already knows (no definition of SEO, crawlers, or backlinks); nearly every line gives concrete tool or rule guidance, with only minor passages that could be trimmed, fitting the efficient-with-minor-over-explanation anchor rather than fully lean.	4 / 5
Actionability	It names exact tools (run_site_audit, get_backlinks_overview, research_keywords), exact parameters (runLighthouse: true, 1-3 seeds), and copy-paste-ready mechanics ("with a ready-to-send message", "the exact sentence to send them"), giving fully executable instruction-only guidance that covers the common cases.	5 / 5
Workflow Clarity	The 10-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops: investigate broken audits before writing (step 4), verify every finding against live HTML (step 5), and an adversarial review pass (step 9), matching the clear-sequence-with-explicit-validation anchor.	5 / 5
Progressive Disclosure	Sections are well organized (Goal, Required inputs, Project context, MCP tools, Workflow, Output format, Guardrails) and the template reference is one level deep, but template.html is referenced as a bundle file that does not exist on disk, leaving a minor navigation gap that keeps it below a 5.	4 / 5
	Total	18 / 20 Passed

Description

53%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 specific and plainspoken about what it produces, but it lacks an explicit trigger clause, which caps completeness. Adding a "Use when…" sentence with natural synonyms ("SEO audit", "SEO review") would lift the weaker dimensions.

Suggestions

Append a 'Use when…' clause naming natural triggers, e.g. 'Use when the user asks for an SEO audit or SEO review of a domain, especially for a shareable report a non-expert can act on.'

Add common synonyms such as 'SEO review' or 'ranking check' to broaden trigger-term coverage.

Mention one more concrete action (e.g. 'verifies findings against live page HTML') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (SEO) and two concrete actions — "Audit a website" and "deliver a one-page, plain-language SEO report" — but coverage is not comprehensive, matching the 1-2 concrete actions anchor; it is not a 4 because there are not several distinct actions listed.	3 / 5
Completeness	It has a clear "what" (audit a site and deliver a plain-language report) but no explicit "Use when…" trigger guidance in the description, so per the rubric guideline completeness is capped at 3; it cannot reach 4 without an explicit when clause.	3 / 5
Trigger Term Quality	Natural terms like "Audit a website", "SEO report", and the implied "SEO audit" are present, but common synonyms such as "SEO review" or "rank" are missing, placing it at the some-relevant-keywords-but-missing-variations anchor rather than full coverage.	3 / 5
Distinctiveness Conflict Risk	"SEO audit / one-page SEO report" is a clear niche with low conflict risk against unrelated skills, though closely related marketing skills (keyword-research, competitor-analysis) create minor overlap, keeping it just below a 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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: every-app/open-seo
Path: .agents/skills/seo-audit/SKILL.md
Commit: 7b9ee0e

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.