CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

78%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.

The body is a lean, well-structured routing skill with concrete install and cost commands, an explicit pre-flight MCP check with failure handling, and clear cross-skill delegation rules. Weaknesses are minor: pinned version/date maintenance details sit in the main flow, and no example MCP tool invocations or API-error handling steps are provided. All four dimensions land at 4–5 with no actionable gaps worth flagging.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a routing table, terse conventions, and guardrails with no padding. Minor trimmable tokens remain: the "Package check (2026-07-10)" date line and repeated pinned version "@ahrefs/mcp@0.0.11" are time-sensitive details that penalize conciseness per the guidelines, keeping it below 5.

4 / 5

Actionability

Concrete executable guidance throughout: "extensions/ahrefs/install.sh" / "install.ps1", the API token URL, a routing table mapping exact commands to actions, and the copy-pasteable cost command "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_costs.py. It stops short of 5 because no example MCP tool invocation or parameter details are shown for the four data lookups.

4 / 5

Workflow Clarity

A pre-flight check ("verify the MCP is connected... If tools are not available, tell the user the extension is not installed") provides explicit error recovery, and the cost-guardrail batch workflow has pre-batch validation (estimate, surface, log). Not 5 because checkpoints for API errors, rate limits, or empty results are missing.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the ~50-line body is organized into clear single-purpose sections (Prerequisites, Routing, Output conventions, Cross-skill delegation, Cost guardrails, Security) with no nested references. Per the simple-skill guidance, this earns the top score with well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

66%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.

The description communicates concrete, domain-specific capabilities and carves out a distinct Ahrefs-only niche within the SEO tool suite. Its main weakness is the complete absence of explicit "use when" trigger guidance, which caps completeness and limits discoverability. Adding natural synonyms for backlink/keyword analysis would strengthen trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs Ahrefs backlink data, referring domain counts, organic keyword rankings, or Content Explorer results" — its absence currently caps completeness at 3.

Include natural trigger synonyms users would say — "backlink analysis", "link profile", "domain rating", "competitor keywords" — to broaden trigger-term coverage toward the top anchor.

Mention the metric outputs the body actually covers (Domain/URL rating, organic traffic estimates) to close the minor specificity gap.

DimensionReasoningScore

Specificity

"Reads referring domains, backlinks, organic keywords, and content explorer data" names four concrete data types, matching the several-specific-actions level. It falls short of 5 because verbs are limited to "Reads"/"Pairs with" and body-covered metrics (Domain/URL rating, organic traffic estimates) are omitted — minor coverage gaps.

4 / 5

Completeness

The "what" is clear (reads four Ahrefs data types via the MCP server) but there is no "Use when..." clause or equivalent trigger guidance; "Pairs with seo-backlinks for multi-source confidence weighting" describes collaboration, not when to invoke this skill. Per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"backlinks", "referring domains", "organic keywords", and "Ahrefs" are terms SEO users naturally say, giving good keyword coverage. Not 5 because common synonyms like "link profile", "domain rating", "link building", or "competitor keywords" are missing.

4 / 5

Distinctiveness Conflict Risk

"Ahrefs API analyst" scoped "via the tested @ahrefs/mcp@0.0.11 server" carves out a clear source-specific niche with distinct triggers. Minor overlap risk remains with closely related suite skills (seo-backlinks, seo-dataforseo) covering adjacent SEO data, so it does not reach 5's minimal conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

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.