CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-drift

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, highly actionable command reference: concrete executable invocations, thorough error handling, and a correctly sized body that externalizes rule detail to a real one-level-deep reference file. The only trims needed are the stale date in the title and some duplication between the step lists and execution blocks.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanations of concepts Claude already knows, but the time-sensitive '(April 2026)' date in the H1 and partial duplication between the per-command 'Steps' lists, 'Execution' blocks, and the top-level Commands table are tokens that could be trimmed.

4 / 5

Actionability

Every command has copy-paste-ready invocations with concrete flags ('--skip-cwv', '--baseline-id 5', '--limit 10'), expected JSON outputs, a seven-scenario error-handling table with explicit actions, and worked workflow examples covering the common pre/post-deploy and monitoring cases.

5 / 5

Workflow Clarity

Each command is a clearly ordered numbered sequence starting with URL validation, and the Error Handling table specifies recovery per failure mode ('Do not guess state', 'Store null for CWV fields'), but there are no inline validate-then-proceed checkpoints (e.g. verify the fetch/parse succeeded before storing), falling just short of the explicit feedback-loop level-5 anchor.

4 / 5

Progressive Disclosure

The 17-rule detail is properly externalized to a verified one-level-deep reference (references/comparison-rules.md exists and contains the full rule set), clearly signaled once ('Load references/comparison-rules.md for the full rule set with thresholds, recommended actions, and cross-skill references'), leaving SKILL.md as a navigable overview.

5 / 5

Total

18

/

20

Passed

Description

87%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 with explicit what/when structure and a rich set of natural trigger phrases. Its main weaknesses are that the captured SEO elements are left unnamed and several generic trigger terms ('baseline', 'did anything break', 'deployment check') could route non-SEO requests to this skill.

Suggestions

Qualify the generic trigger terms with SEO context, e.g. 'SEO baseline', 'track SEO changes over time', 'SEO deployment check', to reduce false triggers from unrelated baseline/change-tracking requests.

Name one or two concrete tracked elements (e.g. 'title tags, meta descriptions, canonicals, schema, Core Web Vitals') so the 'what' is specific rather than the abstract 'SEO-critical elements'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('capture baselines of SEO-critical elements, detect changes, and track regressions over time', 'baseline, diff, and track changes') matching the skill's three commands, but never enumerates what the SEO-critical elements are, leaving a minor coverage gap versus the comprehensive level-5 anchor.

4 / 5

Completeness

It explicitly answers both what ('capture baselines of SEO-critical elements, detect changes, and track regressions over time') and when ('Use when user says...') with concrete trigger phrases, matching the level-5 anchor structure.

5 / 5

Trigger Term Quality

Nine natural, quoted trigger phrases ('SEO drift', 'baseline', 'track changes', 'did anything break', 'SEO regression', 'compare SEO', 'before and after', 'monitor SEO changes', 'deployment check') give comprehensive coverage including synonyms of what a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The SEO framing carves out a niche, but several triggers ('baseline', 'track changes', 'did anything break', 'before and after', 'deployment check') are generic enough to fire in non-SEO contexts, creating overlap risk with unrelated skills rather than only closely related ones.

3 / 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

AgriciDaniel/claude-seo

Path

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