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," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

57

Quality

67%

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 ./.gemini/skills/seo-audit/SKILL.md

The canonical home for this skill is seo-audit in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, actionable audit framework with concrete tooling and output templates, but it suffers from internal redundancy and references bundle files that are not present in the skill bundle.

Suggestions

Consolidate the redundant "Initial Assessment"/"Task-Specific Questions" sections and the "Audit Report Structure"/"Output Artifacts" sections to remove duplicated guidance.

Add explicit validation checkpoints to the workflow (e.g., confirm crawl/index data is complete before running seo_health_scorer.py, sanity-check scores against raw findings).

Either ship the referenced bundle files (references/seo-audit-reference.md, references/cwv-thresholds.md, references/eeat-framework.md, references/schema-types.md, and the two scripts) or remove the dangling references so navigation is not broken.

DimensionReasoningScore

Conciseness

Mostly efficient structured guidance, but redundancy between "Initial Assessment" and "Task-Specific Questions," and between "Audit Report Structure" and "Output Artifacts," plus a list of well-known free/paid tools, could be trimmed.

3 / 5

Actionability

Concrete executable commands with flags (`seo_checker.py --file page.html`, `seo_health_scorer.py --checks checks.json --industry saas`) and a specific Issue/Impact/Evidence/Fix/Priority output template; held at 4 because the report is a template rather than fully copy-paste-ready code.

4 / 5

Workflow Clarity

A clear three-layer sequence (technical → on-page → content → score → action plan) is present, but explicit validation/checkpoint steps (e.g., verify crawl completeness before scoring) are missing or implicit.

3 / 5

Progressive Disclosure

Well-organized sections with a clear one-level-deep References list and overview-level inline content (CWV summary table) that points to detail files; held at 4 because the referenced bundle files (references/*.md, scripts/*.py) do not actually exist, breaking navigation.

4 / 5

Total

14

/

20

Passed

Description

73%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 well-constructed with explicit trigger guidance and good boundary disambiguation against sibling skills. Its main weakness is that the capability statement relies on synonymous verbs rather than distinct concrete actions.

DimensionReasoningScore

Specificity

Names the SEO domain with actions "audit, review, or diagnose SEO issues," but these are near-synonyms rather than multiple distinct concrete capabilities, leaving coverage non-comprehensive.

3 / 5

Completeness

Explicitly answers both what ("audit, review, or diagnose SEO issues") and when (concrete "Use when the user mentions..." trigger list); held at 4 because the "what" is thin/synonymous rather than a rich capability list.

4 / 5

Trigger Term Quality

Strong natural trigger phrases ("SEO audit," "technical SEO," "why am I not ranking," "SEO health check") users would actually say, but a few common variations like "organic traffic" or "search rankings" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear SEO-auditing niche with explicit boundary disambiguation ("see programmatic-seo," "see schema-markup") and distinct trigger terms, minimizing conflict risk with adjacent skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-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.