CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-backlink-audit

Audit a backlink profile using Ahrefs MCP data: profile health, anchor text distribution, toxic link identification, lost link reclamation, and gap analysis against competitors. Use this skill when reviewing backlink health, scoping a disavow project, recovering from a manual action, planning link building, or doing M&A due diligence on a property's link equity. Triggers on backlink audit, link profile, toxic links, disavow, anchor text analysis, lost links, link reclamation, referring domains, link gap. Also triggers when traffic decline correlates with link loss or when an unnatural link warning appears in Search Console.

Quality

92%

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 analysis-framework skill: lean, expert-calibrated, with a clear workflow, defined output format, and proper use of a single reference file. The main gaps are the absence of concrete MCP tool invocations and explicit validation checkpoints inside the workflow steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes domain competence: no basic-concept explanation, dense bullets, and expert-calibrated judgment calls ('DR is a relative metric, not a quality signal. A DR-30 niche site can be more valuable than a DR-80 generalist'). Every section adds non-obvious guidance — matching the 'every token earns its place' anchor, not the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is largely executable: a 10-step workflow, specific per-dimension Ahrefs pulls, six anchor-text categories, and a concrete 8-section output format. It falls short of the 5 anchor because the pulls are described at the data level ('Total referring domains (current and trended)') without naming the actual MCP tools/parameters to invoke, leaving minor gaps in copy-paste executability.

4 / 5

Workflow Clarity

The 10-step sequence is clear and well-ordered, and the disavow risk is mitigated via the failure patterns ('Disavow happy') and referenced criteria file. But explicit validation checkpoints are absent from the workflow itself — Search Console triangulation and pull-date documentation appear in 'Failure patterns' and the output 'Methodology' section rather than as verification steps — fitting 'clear sequence with most checkpoints present; minor validation gaps'. Not 5, because validation is implicit rather than a step like 'verify toxic list against Search Console before finalizing'.

4 / 5

Progressive Disclosure

The body is an appropriately sized overview, and the one detailed sub-procedure (toxic-link classification) is correctly split into a single one-level-deep reference that is clearly signaled twice and exists on disk (references/toxic-link-criteria.md). This matches the 'clear overview with well-signaled one-level-deep references' anchor; the 4 anchor would require organization gaps, which are absent.

5 / 5

Total

18

/

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: concrete capability list, explicit dual trigger guidance, and natural keyword coverage. The only weakness is a minor overlap risk with sibling SEO-suite skills via the 'planning link building' use case.

DimensionReasoningScore

Specificity

The description lists five concrete actions — 'profile health, anchor text distribution, toxic link identification, lost link reclamation, and gap analysis against competitors' — comprehensively covering the skill's scope, matching the top anchor's 'multiple specific concrete actions; comprehensive coverage'.

5 / 5

Completeness

Both halves are explicit: the 'what' is stated in the first sentence and the 'when' is stated twice ('Use this skill when reviewing backlink health, scoping a disavow project...' and 'Triggers on...'), with concrete trigger phrases — the exact pattern of the 5 anchor. Not 4, because the 'when' clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

It enumerates natural trigger phrases users would actually say ('backlink audit, link profile, toxic links, disavow, anchor text analysis, lost links, link reclamation, referring domains, link gap') plus two situational triggers (traffic decline correlating with link loss, unnatural link warning in Search Console), giving comprehensive natural-term coverage. It does not sit between anchors: 4 would require noticeable missing common terms, which is not the case.

5 / 5

Distinctiveness Conflict Risk

The backlink-audit niche is clear and its triggers (disavow, referring domains, link gap) are largely distinct, but the use-when clause 'planning link building' overlaps with a closely related sibling skill (seo-offpage handles building new links), fitting the 4 anchor 'mostly distinct; minor overlap risk with closely related skills'. Not 5, because that sibling overlap is real; not 3, because the core triggers are unmistakably about link-profile analysis.

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

rampstackco/claude-skills

Path

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