CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-backlinks

Analyze a site's backlink profile, anchors, toxic signals, competitors, gaps, and disavow candidates. Use only when links or referring domains are the requested focus.

Quality

83%

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

81%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 dense, highly actionable operational skill: every step has an exact command, thresholds are tabulated, and the workflow includes a mandatory validation gate with a fix-and-rerun loop and a pre-delivery checklist. Its main weaknesses are repetition of the data-sufficiency rule across three sections and Pre-Delivery checklist items copied from a sibling on-page audit skill that are irrelevant to backlink analysis.

Suggestions

Consolidate the data-sufficiency rule: it is stated in the Health Score gate, repeated in the 'MUST NOT: score what you did not measure' section, and again in the Pre-Delivery checklist. State it once and reference it elsewhere.

Remove off-topic Pre-Delivery checklist items (JSON-LD `@type`/`@graph` checks, H1 findings, platform detection like wp-content/shopify CDN) that belong to an on-page SEO audit skill, not backlink analysis; keep only backlink-relevant checks (link_removed vs unverifiable_js, reciprocal links, health-score factors, source labels).

Drop the editorial meta-commentary ('This rule has been stated in this skill before and was violated anyway') and unify the two reference path formats for backlink-quality.md to a single consistent style.

DimensionReasoningScore

Conciseness

The bulk is dense, domain-specific operational data (benchmark thresholds, confidence weights, exact commands) Claude does not already know, but the data-sufficiency rule is repeated three times (the 4-factor gate, the "MUST NOT: score what you did not measure" section, and the Pre-Delivery checklist), and the checklist imports off-topic on-page audit items ("parse_html return `@type`", "`@graph` wrapper", "H1 findings", "wp-content, shopify CDN"). This matches anchor 3 (mostly efficient but could be tightened) rather than 4, since the repetition and mis-scoped content exceed minor over-explanation.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout ("run backlinks_auth.py --check --json", "run moz_api.py metrics <url> --json", "run verify_backlinks.py --target <url> --links <file> --json"), plus exact scoring tables, anchor benchmarks, a fallback cascade with confidence values, and a concrete output format. Matches anchor 5's fully executable coverage of common cases.

5 / 5

Workflow Clarity

Clear multi-step sequence (source detection, 7-section framework with per-section source preference order, health-score computation, output format) with explicit validation checkpoints: a data-sufficiency gate, a mandatory validator with a fix-and-rerun feedback loop ("If the validator returns `status: FAIL`... re-run until it passes"), and a pre-delivery checklist. Matches anchor 5 (explicit validation steps, feedback loops, checklists).

5 / 5

Progressive Disclosure

Good structure with well-signaled, one-level-deep on-demand references ("Load on demand (do NOT load at startup)" for backlink-quality.md and free-backlink-sources.md; no local bundle directories exist). Minor gaps keep it below anchor 5: the body is long with substantial inline detail, and the same reference file is cited with two inconsistent path styles ("../seo/references/backlink-quality.md" in the Toxic Links section versus "${CLAUDE_PLUGIN_ROOT}/skills/seo/references/backlink-quality.md" in Reference Documentation).

4 / 5

Total

17

/

20

Passed

Description

78%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 in third-person voice that names a specific niche, enumerates concrete deliverables, and includes an explicit use-restriction that minimizes conflict with sibling SEO skills. It falls just short of top marks because the when-clause is a boundary condition rather than concrete trigger phrases, and a few natural synonyms (inbound links, link building, domain authority) are absent.

DimensionReasoningScore

Specificity

Enumerates concrete analysis objects ("backlink profile, anchors, toxic signals, competitors, gaps, and disavow candidates") but relies on a single verb "Analyze" and omits scoring/health-report outputs. Matches anchor 4 (several specific items, minor gaps) rather than 5's multi-action comprehensive coverage or 3's 1-2 concrete actions.

4 / 5

Completeness

Both parts are explicit: what ("Analyze a site's backlink profile, anchors, toxic signals...") and when ("Use only when links or referring domains are the requested focus"). The when-clause is a boundary condition rather than concrete user-mention trigger phrases, so it fits anchor 4, not the explicit trigger-phrase enumeration of anchor 5, and is clearly above anchor 3's merely implied when.

4 / 5

Trigger Term Quality

"backlink profile", "anchors", "toxic", "disavow", and "referring domains" are natural phrases SEO users say, but common synonyms like "inbound links", "link building", or "domain authority" are missing. Good coverage (anchor 4), short of the comprehensive synonym/extension sweep of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"backlink profile", "disavow candidates", and "referring domains" carve a distinct off-page SEO niche, and the restriction "Use only when links or referring domains are the requested focus" is an explicit anti-conflict guard against sibling SEO skills. Clear niche with minimal conflict risk (anchor 5).

5 / 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-backlinks/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.