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

94%

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

92%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: exact executable commands, clearly sequenced workflows with validation and thorough error-recovery guidance, and proper deferral of the 17-rule detail to a verified one-level reference. The only deductions are minor conciseness issues, chiefly the time-sensitive "(April 2026)" date in the title and mild step/execution redundancy.

Suggestions

Remove the time-sensitive "(April 2026)" from the H1 (or move date/version notes to a dedicated metadata or old-patterns section) so the body carries no stale-prone temporal markers.

Drop the redundant "Source" column from the capture-elements table and collapse the per-command "Steps" lists where they merely restate what the single Execution command does, keeping steps only where they add decision points (e.g., when to use --skip-cwv).

DimensionReasoningScore

Conciseness

The body is table-driven and dense with no explanations of concepts Claude already knows, but carries minor trimmable overhead: the time-sensitive "(April 2026)" date in the H1 (outside any deprecated/old-patterns section), a redundant "Source" column in the capture table, and steps that repeat what the single Execution command already shows. Not 5 due to those instances; not 3 because the padding is minor relative to genuinely lean overall content.

4 / 5

Actionability

Every command is copy-paste ready with exact invocations ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_baseline.py <url>) including flags (--skip-cwv, --baseline-id 5, --limit 10), expected JSON outputs, and a concrete error-action table. Specific examples cover all three commands and the common cases; matches the fully-executable 5 anchor.

5 / 5

Workflow Clarity

Baseline and compare are clearly sequenced as numbered steps with an explicit validation checkpoint (step 1 URL/SSRF validation), and the 7-scenario Error Handling table provides feedback loops for error recovery (e.g., CWV fetch fails → store null, skip CWV rules; no baseline → suggest baseline first). Not 4: checkpoints and recovery paths are explicit rather than implicit; the operations are read-only monitoring, so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

The body is a clear overview that defers the 17-rule detail set to a real, explicitly signaled, one-level-deep reference ("Load references/comparison-rules.md for the full rule set"), which exists in the bundle and contains exactly that detail. Severity summaries and cross-skill tables sit appropriately in the body while per-rule thresholds live in the reference; matches the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

96%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 that clearly states capabilities, includes an explicit 'Use when' clause with abundant natural trigger phrases, and anchors itself in a distinct SEO-drift niche. The only weakness is a handful of unqualified generic triggers (e.g., "baseline", "deployment check") that could collide with non-SEO skills.

DimensionReasoningScore

Specificity

"capture baselines of SEO-critical elements, detect changes, and track regressions over time" plus "baseline, diff, and track changes to your on-page SEO" lists multiple concrete actions that comprehensively cover the skill's three commands (baseline, compare, history). Not 4: no meaningful coverage gap; not below since every named action is concrete rather than generic.

5 / 5

Completeness

Explicitly answers what ("capture baselines... detect changes, and track regressions over time") and when ("Use when user says 'SEO drift', 'baseline', ...") with concrete trigger phrases. Matches the 5 anchor exactly; the 4 anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Nine quoted trigger phrases — "SEO drift", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", "deployment check" — comprehensively cover natural user phrasing including synonyms. Not 4: no obviously missing natural variation for this domain (the domain has no file extensions to enumerate).

5 / 5

Distinctiveness Conflict Risk

Mostly SEO-qualified triggers ("SEO drift", "SEO regression", "compare SEO", "monitor SEO changes") establish a clear niche, but unqualified generic phrases ("baseline", "track changes", "did anything break", "before and after", "deployment check") create minor overlap risk with git-diff or deployment-verification skills. Not 5 because those unqualified terms could fire for the wrong skill; not 3 since the majority of triggers are distinctly SEO-scoped.

4 / 5

Total

19

/

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.