CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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

Quality

Content

57%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-structured orchestration overview with excellent progressive disclosure and concrete command/industry-detection detail. Its weaknesses are redundancy across the three overlapping sub-skill/subagent lists, an unspecified Health Score aggregation step (with an On-Page SEO 20% category that no delegate covers), and no validation checkpoint in the audit workflow.

Suggestions

Merge the Sub-Skills and Subagents lists into the Quick Reference table (or each other) to eliminate triple enumeration of the same names.

Specify how subagent outputs aggregate into the SEO Health Score and assign an owner for the On-Page SEO category (20% weight) in the delegation step.

Add an explicit validation step in the audit workflow (e.g., verify all seven subagent results returned before computing the Health Score) and move dated policy details (HowTo/FAQ restrictions, QRG update) into the relevant reference files.

DimensionReasoningScore

Conciseness

Three overlapping enumerations (Quick Reference table of 14 commands, Sub-Skills list of 14 items, Subagents list of 9) repeat largely the same names, and dated policy details ("deprecated Sept 2023", "Aug 2023 restriction", "Sept 2025 QRG update") sit inline in Hard rules rather than a dedicated deprecated section. Not 2 since there is no concept-explaining padding, but the duplication could clearly be tightened — anchor 3.

3 / 5

Actionability

Concrete commands (`/seo audit <url>`), specific industry signals ("pricing page, /features, 'add to cart'"), and a scoring weights table are present, but "Collect results and generate unified report with SEO Health Score" never specifies how subagent outputs map to the weighted categories — On-Page SEO carries 20% weight yet no sub-skill/subagent is assigned to it in the delegation step. Missing key executable details — anchor 3, not 4.

3 / 5

Workflow Clarity

The audit flow is a clear numbered sequence (detect type → spawn subagents → collect/report → action plan) and the Error Handling table gives recovery actions per failure mode. However, no validation checkpoint exists between spawning subagents and generating the report (e.g., confirming all subagent results are complete before scoring), leaving checkpoints implicit — anchor 3, not 4.

3 / 5

Progressive Disclosure

"Load these on-demand as needed (do NOT load all at startup)" with four described reference files, all of which exist in references/ and are one level deep. The body is a genuine overview that appropriately delegates detail (thresholds, schema types, E-E-A-T criteria, quality gates) — anchor 5.

5 / 5

Total

14

/

20

Passed

Description

83%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 strong description: third-person, concise, with an explicit trigger clause and specific enumerated scope. Its main limitation is that it describes one umbrella action rather than the range of concrete capabilities the skill orchestrates, and it lacks synonym variations of common user phrasings.

Suggestions

Mention 1-2 more concrete capabilities beyond "audit" (e.g., sitemap/schema generation, competitor comparison pages) to strengthen specificity.

Add a common synonym such as "search engine optimization" or "site audit" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO" names one concrete action with seven specific coverage areas. Not 3 because far more than 1-2 concrete actions' worth of scope is enumerated; not 5 because distinct capabilities (page analysis, sitemap/schema generation, strategic planning) are absent.

4 / 5

Completeness

Explicitly answers both: what ("Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO") and when ("Use as the umbrella skill when the user asks for a full SEO analysis or strategy") with a concrete trigger phrase, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present: "SEO audit", "full SEO analysis", "SEO strategy", "GEO". Good coverage but missing common synonyms like "search engine optimization" spelled out, "rankings", or "site audit", so below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The "umbrella skill… full SEO analysis or strategy" framing carves a clear niche versus narrower sub-skills. Not 5 because "SEO audit" alone is a broad trigger that overlaps the skill's own sub-skills (seo-technical, seo-page, etc.), keeping minor conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/seo/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.