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.

64

Quality

75%

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 ./.agents/skills/seo-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized SEO audit framework with a useful report template and concrete thresholds, but it leans on generic checklist knowledge Claude already has and lacks executable tooling, validation checkpoints, and progressive disclosure. It is competent but not distilled or split for token efficiency.

Suggestions

Move the per-site-type issue lists (SaaS, e-commerce, blog, local) and the full output-format template into a separate reference file referenced one level deep, keeping SKILL.md as a lean overview.

Add executable, copy-paste-ready checks where possible (e.g. site:domain.com query, specific Search Console report paths, or a Screaming Frog command-line invocation) instead of descriptive bullets like "Check for unintentional blocks."

Add explicit validation/verification checkpoints to the workflow (e.g. "Confirm findings against live Search Console data before reporting" and a re-check loop after fixes) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body avoids concept-explanation padding, but much of it is a generic SEO checklist (e.g. "Responsive design," "Tap target sizes," "Keyword cannibalization") that restates standard knowledge Claude already has rather than distilling specialized guidance; it could be tightened.

2 / 3

Actionability

It provides a concrete report template (Issue/Impact/Evidence/Fix/Priority) and specific thresholds (LCP < 2.5s, titles 50-60 chars), but most checks are descriptive bullet lists ("Check for unintentional blocks") with no executable commands or copy-paste-ready tool invocations.

2 / 3

Workflow Clarity

A clear priority-ordered framework and output structure exist, but there are no explicit validation checkpoints or verify-before-reporting feedback loops, so the sequence is present yet checkpoints are only implicit.

2 / 3

Progressive Disclosure

No bundle files exist or are referenced and the entire ~415-line guide is a single monolithic SKILL.md; sections are headed but per-site-type issues and full output templates that could be split out remain inline with no navigation to deeper material.

2 / 3

Total

8

/

12

Passed

Description

100%

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 strong across all dimensions: it states concrete actions, includes a rich set of natural trigger phrases, explicitly covers both what and when, and cleanly distinguishes itself from related skills. No changes needed.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "audit, review, or diagnose SEO issues" — matching the score-3 anchor that lists several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("audit, review, or diagnose SEO issues") and when ("Also use when the user mentions...") with explicit trigger guidance, satisfying the score-3 anchor; voice is third person.

3 / 3

Trigger Term Quality

Covers natural user phrases users would actually say — "SEO audit," "technical SEO," "why am I not ranking," "on-page SEO," "meta tags review," "SEO health check" — which matches the good coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Has a clear SEO-audit niche with distinct triggers and explicitly disambiguates from sibling skills ("see programmatic-seo," "see schema-markup"), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
quran/quran.com-frontend-next
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.