CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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]

Quality

72%

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

63%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 well-sequenced, highly actionable seven-phase audit workflow with concrete commands, thresholds, and validation checkpoints throughout. Its weaknesses are repetition of the preserve-rules guidance, reliance on external repo scripts not bundled with the skill, and a monolithic structure with no progressive-disclosure layer.

Suggestions

State the preserve-list once (e.g., in Phase 1 or a dedicated section) and reference it from other phases instead of repeating the guidance three times; replace the ASCII report box with a compact bullet-list template.

Add a re-validation step after auto-fixes (re-run seo_checker/content_scorer to confirm scores improved) and an explicit fallback if `mkdocs build` fails.

Split the keyword-placement table, reference-doc tables, and detailed rules into a references/ file within the skill, keeping SKILL.md as a lean overview — and bundle or inline replacements for the external marketing-skill scripts the workflow depends on.

DimensionReasoningScore

Conciseness

Largely rule-dense and efficient, but the "preserve high-ranking pages" guidance is repeated three times (intro, Phase 3's Important note, Phase 7's preserve section) and the 40-line ASCII report box could be a compact list. Fits "mostly efficient but could be tightened" better than the minor-trims anchor at 4.

3 / 5

Actionability

Mostly executable: copy-paste-ready commands (`find docs/ -name '*.md'`, `grep -rh '^description:' ... | sort | uniq -d`, `mkdocs build`, python script invocations) and concrete thresholds (50–60 char titles, readability ≥70). Minor gaps: "enrich it with domain context using the DOMAIN_SEO_SUFFIX pattern" and "check via git log" are high-level, and every scoring script lives outside the skill bundle.

4 / 5

Workflow Clarity

Seven phases are explicitly sequenced with validation checkpoints (flag pages scoring below 60, readability/structure/engagement thresholds, sitemap verification, orphan detection), so the batch-operation cap at 3 does not apply. Not 5 because there is no re-validation loop after auto-fixes and no handling for a failed `mkdocs build`.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ bundle exists; this is a monolithic ~330-line SKILL.md with the keyword-placement table, ASCII report template, and preserve list all inlined. Section structure is good, but content that could live in one-level-deep reference files is inline, matching anchor 3 rather than 4.

3 / 5

Total

14

/

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.

A specific, action-dense description that clearly conveys what the skill does across its audit scope. Its main weakness is the absence of any "Use when..." trigger guidance, which caps completeness and leaves invocation conditions to inference.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to improve SEO, search rankings, or visibility of documentation pages, or when auditing docs/ or README.md files for meta tags, keywords, or broken links."

Include natural synonyms users would say — "search rankings", "Google visibility", "search engine optimization" — to broaden trigger term coverage.

Clarify the boundary with general content-editing skills by stating it targets published documentation sites (MkDocs) rather than arbitrary markdown files.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Audits README.md files and docs/ pages for meta tags, headings, keywords, readability, duplicate content, and broken links" plus "Applies fixes, updates sitemap.xml, and generates a report" — with comprehensive coverage of the audit scope. Not 4 because there are no meaningful coverage gaps.

5 / 5

Completeness

The "what" is clearly and specifically answered, but there is no "Use when..." clause or equivalent trigger guidance — "Usage: /seo-auditor [path]" is invocation syntax, not a trigger condition, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keywords users would say: "SEO", "README.md", "docs/ pages", "meta tags", "broken links", "sitemap.xml". Not 5 because common synonyms and variations like "search rankings", "Google visibility", or "search engine" are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to documentation/README SEO auditing with sitemap regeneration — a distinct niche with minimal conflict risk; only minor overlap with generic content-editing or documentation-maintenance skills. Not 5 because "optimize documentation files" alone could pull in general docs-editing requests.

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.

Validation — 13 / 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

Path

.gemini/skills/seo-auditor/SKILL.md

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.