CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-drift

SEO drift monitoring — snapshot a site's SEO state and detect regressions over time. Captures a baseline (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence, key on-page elements) and on later runs diffs against it to surface what changed: ranking drops, pages that fell out of the index, titles/metas that were accidentally overwritten (a CMS/redeploy classic), canonicals or noindex flipped, schema that disappeared. Use this skill when the user wants to monitor SEO over time, catch regressions after a site change / migration / redeploy, set a baseline, diff against a previous state, or asks "what changed on my site's SEO" or "did my redesign break SEO". Trigger on: "SEO drift", "SEO monitoring", "track SEO over time", "did my site change break SEO", "after migration SEO", "SEO regression", "baseline my SEO", "compare SEO to last month", "my titles changed", "pages fell out of the index". For a one-time full audit use /seo-analysis.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, instruction-only skill body that assumes domain knowledge and sequences capture, diff, and report phases clearly with helpful guardrails. It is efficient and actionable with only minor gaps around data-collection mechanics and explicit validation checkpoints.

Suggestions

Add a brief validation checkpoint in Phase 1 (e.g., confirm GSC is actually connected and the crawl returned data before stamping the snapshot) to strengthen workflow_clarity.

Either move the 'Credit' blockquote into a comment/README or cut it, and tighten editorializing parentheticals like 'the redeploy-overwrite signature' to improve conciseness.

Give a one-line pointer for how the on-page crawl is performed (tool or approach) or explicitly defer it to ../shared/preamble.md so actionability does not depend on an unstated mechanism.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explanations of SEO, GSC, canonicals, or schema), but the 'Credit' blockquote and a few editorializing parentheticals are trimmable, keeping it just below the lean/efficient top anchor.

4 / 5

Actionability

Concrete, specific guidance on what to capture (per-query position & impressions, indexed page count, H1, canonical URL, robots/meta-robots, schema types, word count) and what to surface in the diff, but the actual data-gathering mechanics are deferred to ../shared/preamble.md and GSC connection is left to the reader.

4 / 5

Workflow Clarity

Work is clearly sequenced across Step 0 and Phases 0-3 with an explicit baseline-vs-compare gate and a 'do not invent a date' guardrail; however, explicit validate->fix->retry checkpoints for the GSC/crawl data step are only implicit, so it sits below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into labeled sections with a single clearly-signaled one-level reference to ../shared/preamble.md; no nested references and no inlined material that belongs elsewhere, though there are no in-bundle reference files to navigate and the body slightly exceeds the under-50-line simple-skill threshold.

4 / 5

Total

16

/

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 clearly states capabilities, provides an explicit Use-when clause plus a rich trigger-phrase list, and disambiguates from the related /seo-analysis skill. It is comprehensive without being padded.

DimensionReasoningScore

Specificity

Lists multiple concrete capture actions (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence) and concrete drift signals (ranking drops, pages out of index, titles/metas overwritten, noindex flipped, schema disappeared), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (snapshot + diff capabilities) and when ('Use this skill when the user wants to monitor SEO over time, catch regressions after a site change / migration / redeploy...') with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

A dedicated 'Trigger on:' list supplies many natural phrases a user would actually say ('SEO drift', 'did my site change break SEO', 'baseline my SEO', 'compare SEO to last month', 'my titles changed', 'pages fell out of the index'), giving comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (SEO drift over time vs. one-time audit) with distinct triggers, and explicitly redirects one-off full audits to '/seo-analysis', minimizing overlap risk.

5 / 5

Total

20

/

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.

Validation15 / 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
nowork-studio/NotFair
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.