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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 skill body that uses concrete executable commands, numbered steps with validation, and a properly signaled reference file. Its main weaknesses are a time-sensitive date stamp in the title and the absence of explicit validate-retry feedback loops in the per-command workflows.

Suggestions

Remove the time-sensitive '(April 2026)' from the H1 (or move version/date information to a dedicated metadata or changelog section) to avoid penalizing conciseness.

Add explicit validate->fix->retry feedback loops inside the baseline and compare step lists (e.g., 'If fetch/parse fails, report the error and re-run after the user verifies the URL') to reach the top workflow-clarity anchor.

Consider moving the large cross-skill integration and error-handling tables into a reference file to tighten the SKILL.md overview and strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Content is dense and table-driven with little padding and no over-explanation of concepts Claude already knows, but the time-sensitive '(April 2026)' stamp in the H1 sits outside a deprecated/old-patterns section, a minor conciseness ding that keeps it just below the top anchor.	4 / 5
Actionability	Every command ships copy-paste-ready executable bash using the validated plugin-root pipeline with concrete flags (--skip-cwv, --baseline-id, --limit), covering the common cases fully.	5 / 5
Workflow Clarity	Each command has numbered steps with an explicit SSRF validation checkpoint first and a thorough error-handling table, but the workflows lack explicit validate->fix->retry feedback loops, so they sit just below the top anchor.	4 / 5
Progressive Disclosure	The 17-rule detail is cleanly split into a real, well-signaled one-level reference (references/comparison-rules.md) and the body is sectioned for navigation, but the body itself is fairly long for an overview and disclosure is used only lightly, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

100%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, third-person description that concretely states capabilities and supplies an extensive set of natural trigger phrases for when to invoke it. It cleanly answers both what the skill does and when to use it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'capture baselines of SEO-critical elements, detect changes, and track regressions over time' plus 'baseline, diff, and track changes to your on-page SEO' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (capture baselines, detect changes, track regressions) and 'when' via a clear 'Use when user says...' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides nine natural trigger phrases users would actually say ('SEO drift', 'baseline', 'track changes', 'did anything break', 'SEO regression', 'compare SEO', 'before and after', 'monitor SEO changes', 'deployment check'), covering synonyms and phrasings comprehensively.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear SEO-drift niche with distinctive triggers unlikely to fire for unrelated skills, presenting minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 9279553

Reviewed: 15 hours ago

Table of Contents

Discovery Implementation Validation

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.