seo-ahrefs

Ahrefs API analyst (extension). Reads referring domains, backlinks, organic keywords, and content explorer data via the tested @ahrefs/mcp@0.0.11 server. Pairs with seo-backlinks for multi-source confidence weighting.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extensions/ahrefs/skills/seo-ahrefs/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and well-organized with concrete commands and clean sectioning, scoring well on actionability and progressive disclosure. It loses points for time-sensitive version/date content outside a deprecated section and for a batch workflow that lacks an explicit validation checkpoint.

Suggestions

Move the "2026-07-10" package-check note and the "@ahrefs/mcp@0.0.11" pin into a clearly labeled maintenance/version section so they don't penalize everyday conciseness.

Add an explicit validation step to the cost-guardrails batch workflow, e.g. "If the logged spend exceeds the estimate, pause and confirm with the orchestrator before continuing."

State concretely how to verify MCP connection (e.g. a specific check command) rather than the abstract "check that any Ahrefs MCP tool is available".

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but it embeds time-sensitive info ("Package check (2026-07-10)" and a repeated "@ahrefs/mcp@0.0.11" pin) outside any deprecated/old-patterns section, which the guidelines say should penalize conciseness; it is not a 1 because most tokens still earn their place.	2 / 3
Actionability	It gives concrete, copy-paste-ready commands — the routing table ("/seo ahrefs metrics <url>"), install paths, and "claude-seo run dataforseo_costs.py" — rather than abstract direction; it is not a 2 because the guidance is executable, not pseudocode.	3 / 3
Workflow Clarity	The cost-guardrails section lists a numbered batch sequence (estimate, surface, log) and the prerequisites include an MCP-connection check, but the batch (>= 50 URLs) workflow has no explicit validation/retry checkpoint, which the scoring notes say caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files, and the body is well-organized into clearly labeled sections (Prerequisites, Routing, Output conventions, Cross-skill delegation, Cost guardrails), satisfying the simple-skill allowance for a 3 without external references.	3 / 3
	Total	10 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly scoped to Ahrefs, but it omits any explicit "Use when..." trigger guidance, which caps completeness and weakens trigger-term naturalness. The repeated version pin and "extension" framing add minor jargon.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs Ahrefs backlink, referring-domain, organic-keyword, or content-explorer data."

Move the "@ahrefs/mcp@0.0.11" version pin out of the description (it already lives in the compatibility field) to reduce jargon.

Reframe "(extension)" in plainer terms so the description reads as natural trigger language rather than packaging metadata.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Reads referring domains, backlinks, organic keywords, and content explorer data" — matching the score-3 anchor for several specific actions; it is not the level below because it is comprehensive rather than naming only some actions.	3 / 3
Completeness	It clearly answers "what" the skill does, but there is no "Use when..." or equivalent explicit trigger for "when", which per the judging guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Relevant SEO terms ("backlinks", "referring domains", "organic keywords") appear, but they are wrapped in jargon ("@ahrefs/mcp@0.0.11 server", "extension") with no natural "Use when..." phrasing, so it lacks the full coverage of a 3.	2 / 3
Distinctiveness Conflict Risk	It carves a clear Ahrefs-specific niche ("Ahrefs API analyst") and names its sibling ("Pairs with seo-backlinks"), making it unlikely to trigger for the wrong skill; not a 2 because the source is unambiguous rather than merely "somewhat specific".	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: AgriciDaniel/claude-seo
Path: extensions/ahrefs/skills/seo-ahrefs/SKILL.md
Commit: 09d37c7

Reviewed: 4 days 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.