CtrlK
BlogDocsLog inGet started
Tessl Logo

seo

Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO. Use as the umbrella skill when the user asks for a full SEO analysis or strategy.

59

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo/SKILL.md

The canonical home for this skill is seo in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%Scale 1-5

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

This is a well-structured orchestration skill that clearly defines commands, delegation patterns, and error handling for a comprehensive SEO audit system. Its main weaknesses are redundancy between the sub-skills and subagents sections, and a lack of concrete executable examples or sample outputs that would make the skill more actionable. The quality gates and scoring methodology add genuine value that Claude wouldn't know independently.

Suggestions

Consolidate the Sub-Skills and Subagents sections into a single table with columns for name, purpose, and whether it runs as a subagent during audits—this eliminates significant redundancy.

Add a concrete example of what a unified audit report output should look like (even abbreviated), including the SEO Health Score breakdown and prioritized action plan format.

Add a validation step in the orchestration logic between steps 3 and 4, e.g., 'Verify all subagent results are complete and consistent before generating the unified report; if any conflict, flag for user review.'

DimensionReasoningScore

Conciseness

The skill is reasonably structured but contains some redundancy—the sub-skills list and subagents list overlap significantly, and the 'When to Use' section explains things Claude could infer. The Quick Reference table and scoring methodology are useful but the sub-skills enumeration is repeated in slightly different forms across multiple sections.

3 / 5

Actionability

The skill provides a clear command table and orchestration logic, but lacks executable code or concrete examples of actual output. The instructions are procedural ('detect business type', 'spawn subagents') but don't show how to actually perform these steps—no code snippets, no example audit output, no sample report structure. Industry detection gives signal patterns but no implementation.

3 / 5

Workflow Clarity

The orchestration logic provides a clear 4-step sequence for the audit command, and error handling covers key failure scenarios with specific recovery actions. The quality gates serve as validation checkpoints (hard stops, warnings). However, there's no explicit validate-then-proceed feedback loop for the overall audit workflow—e.g., no step to verify subagent results before generating the unified report.

4 / 5

Progressive Disclosure

The skill correctly references external files on-demand (references/cwv-thresholds.md, references/schema-types.md, etc.) with an explicit instruction not to load all at startup. It delegates to 12+ sub-skills appropriately. However, no bundle files were provided to verify these references exist, and the references section could be more clearly signaled with descriptions of when each file is needed.

4 / 5

Total

14

/

20

Passed

Description

78%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 effectively communicates its role as a comprehensive SEO audit skill and includes a clear 'when to use' clause that positions it as the umbrella skill for full analyses. Its main weakness is that it lists SEO sub-domains rather than concrete actions, making it read more like a category list than a capability description. The trigger terms are solid but could benefit from a few more natural user synonyms.

Suggestions

Replace or supplement the sub-domain list with concrete actions, e.g., 'Checks meta tags, validates robots.txt, analyzes page speed, reviews schema markup, audits sitemap structure' to increase specificity.

Add common user synonyms like 'search engine optimization', 'site audit', 'SEO review', or 'ranking check' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (SEO audit) and lists several sub-domains (technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, GEO), but these are categories rather than concrete actions. It doesn't describe specific actions like 'checks meta tags', 'validates robots.txt', or 'analyzes page speed'.

3 / 5

Completeness

Clearly answers both 'what' (run a broad SEO audit across multiple areas) and 'when' ('Use as the umbrella skill when the user asks for a full SEO analysis or strategy'). The trigger guidance is explicit and concrete.

5 / 5

Trigger Term Quality

Includes good natural keywords like 'SEO audit', 'technical SEO', 'on-page SEO', 'schema', 'sitemaps', 'content quality', 'full SEO analysis', and 'strategy'. Missing some common user phrases like 'search engine optimization', 'site audit', 'SEO review', or 'ranking analysis'.

4 / 5

Distinctiveness Conflict Risk

Positions itself clearly as the 'umbrella' skill for full SEO audits, which helps distinguish it from narrower SEO sub-skills. However, the broad scope (technical SEO, on-page SEO, schema, etc.) could overlap with more specialized SEO skills covering those individual areas.

4 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.