agentleFS
joaoguirunasjoaoguirunas/team-os/.claude/skills/seo-ahrefs/SKILL.md

seo-ahrefs

Skill6 starsChanged 2 days agoMITView on GitHub

Analista da API Ahrefs via MCP @ahrefs/mcp — referring domains, backlinks, keywords orgânicas e Content Explorer. Combina com seo-backlinks para ponderação de confiança multi-fonte. Use ao pedir dados Ahrefs, DR/UR ou backlinks ao vivo.

  • Reads credentials

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before calling any Ahrefs tool, verify the MCP is connected by checking that any Ahrefs MCP tool is available in this session.

    line 24
  2. Distinctive:

    When Ahrefs and Moz disagree on the same metric, trust Ahrefs and note the discrepancy in the report.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

seo-ahrefs

Live Ahrefs data via the tested @ahrefs/mcp@0.0.11 server. Package check (2026-07-10): verify the current Ahrefs MCP package source before changing this tested version.

Prerequisites

  • An Ahrefs API token (https://ahrefs.com/api).
  • Register the Ahrefs MCP server in the project's .mcp.json (or claude mcp add ahrefs -e API_KEY=<token> -- npx -y @ahrefs/mcp@0.0.11), passing the token through the API_KEY environment variable. No installer script ships with this pack.
  • Node 18+ on $PATH for the MCP server.

Before calling any Ahrefs tool, verify the MCP is connected by checking that any Ahrefs MCP tool is available in this session. If tools are not available, tell the user the Ahrefs MCP server is not configured and point to the .mcp.json / claude mcp add setup above.

Routing

CommandAction
/seo ahrefs metrics <url>Domain / URL rating, referring domain count, organic traffic estimate
/seo ahrefs backlinks <url>Top referring domains, anchor distribution, follow/nofollow ratio
/seo ahrefs organic <url>Organic keywords, ranking distribution, traffic by country
/seo ahrefs content <topic>Content Explorer top results, social shares, referring domains

Output conventions

  • Cite the data source on every metric: "Ahrefs (live, confidence 1.00)".
  • When Ahrefs and Moz disagree on the same metric, trust Ahrefs and note the discrepancy in the report.
  • Toxic link assessment: combine Ahrefs backlink quality signals with the existing seo-backlinks Common Crawl + verify crawler signals.

Cross-skill delegation

  • For multi-source confidence weighting across Moz + Bing + Common Crawl + Ahrefs, hand back to seo-backlinks.
  • For SERP-feature analysis where Ahrefs and DataForSEO overlap, prefer DataForSEO for live SERP data.

Cost guardrails

Ahrefs API usage is metered per unit. Before running a batch (>= 50 URLs):

  1. Estimate cost with "${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.claude/skills/seo/scripts/claude-seo" run dataforseo_costs.py (the cost-tracker module is generic and supports Ahrefs unit accounting).
  2. Surface the estimate to the orchestrator.
  3. Log actual cost after each call.

This is the same workflow the seo-dataforseo skill uses.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.