CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-auditor

Scan and optimize documentation files for SEO. Audits README.md files and docs/ pages for meta tags, headings, keywords, readability, duplicate content, and broken links. Applies fixes, updates sitemap.xml, and generates a report. Usage: /seo-auditor [path]

60

Quality

73%

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

Quality

Content

75%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 content is a well-sequenced, actionable 7-phase SEO audit workflow with concrete commands, thresholds, and validation scripts, scoring consistently across dimensions. Its main limitations are external-script dependencies, some redundancy, and a single-file structure without bundle references.

DimensionReasoningScore

Conciseness

The body is mostly lean actionable rules and commands rather than concept padding, with only minor trimmable redundancy (preserve-ranking guidance appears in both Phase 3 and Phase 7) and a large ASCII report template.

4 / 5

Actionability

Concrete executable bash commands and specific thresholds throughout, but most rely on external cross-skill scripts (marketing-skill/skills/.../scripts/*.py) that are not present as bundle files, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 7-phase sequence with validation scripts (seo_checker, content_scorer, sitemap_analyzer), but because fixes are batch and in-place, the mostly-implicit validate→fix→re-validate feedback loops keep it just below 5.

4 / 5

Progressive Disclosure

Well-organized phases plus 'Skill References' and 'Reference Docs' tables with one-level-deep external references, though no bundle files exist and all content lives in a single ~330-line SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

71%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 conveys what the skill does with comprehensive, specific actions and mostly natural trigger terms, but it lacks an explicit 'Use when…' trigger clause, capping completeness. It is distinct and low-conflict.

Suggestions

Add an explicit 'Use when…' trigger clause (e.g., 'Use when auditing documentation for SEO, fixing meta tags or broken links, or updating the sitemap') to raise completeness above 3.

Include a few more natural synonyms users say ('search ranking', 'Google', 'optimize docs') to broaden trigger-term coverage.

Keep the third-person voice (already correct) and trim the trailing 'Usage: /seo-auditor [path]' into the trigger clause for a tighter what-and-when statement.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — audits README.md/docs/ for meta tags, headings, keywords, readability, duplicate content, and broken links, then 'Applies fixes, updates sitemap.xml, and generates a report' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is explicit, but the only 'when' is the invocation hint 'Usage: /seo-auditor [path]' rather than an explicit 'Use when…' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('SEO', 'README.md', 'docs/', 'meta tags', 'broken links', 'sitemap.xml') with a few common synonyms missing (e.g. 'search ranking', 'Google'); fits the good-coverage anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear SEO-audit niche with distinct triggers (SEO, sitemap.xml, meta tags, broken links) giving minimal conflict risk, though it slightly overlaps with general content/doc skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

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.