ahrefs
Ahrefs integration. Manage Projects. Use when the user wants to interact with Ahrefs data.
53
60%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ahrefs/SKILL.mdQuality
Discovery
57%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 minimal and lacks specificity about what Ahrefs capabilities are actually supported. While it has the correct structure with a 'Use when' clause and the brand name 'Ahrefs' provides some distinctiveness, the vague actions ('Manage Projects', 'interact with data') give Claude very little information to make informed skill selection decisions.
Suggestions
Replace 'Manage Projects' with specific concrete actions like 'pull backlink profiles, analyze keyword rankings, run site audits, check domain ratings, and monitor organic traffic'.
Add natural trigger terms users would say, such as 'SEO', 'backlinks', 'keyword research', 'domain authority', 'organic search', 'referring domains'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions Ahrefs, SEO analysis, backlink checking, keyword research, or competitive domain analysis'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage Projects' which is a vague action, and 'interact with Ahrefs data' is abstract. No concrete actions like 'pull backlink reports', 'analyze keyword rankings', or 'export site audit data' are listed. | 1 / 3 |
Completeness | It does answer both 'what' (Ahrefs integration, manage projects) and 'when' (Use when the user wants to interact with Ahrefs data), with an explicit 'Use when...' clause, though both parts are quite thin. | 3 / 3 |
Trigger Term Quality | It includes 'Ahrefs' which is a strong brand-specific trigger term, but lacks natural keywords users would say like 'backlinks', 'SEO', 'keyword research', 'domain rating', 'site audit', or 'organic traffic'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Ahrefs' is a distinctive brand name that reduces conflict risk, but 'Manage Projects' and 'interact with data' are generic enough that they could overlap with other project management or data integration skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong actionable guidance with clear CLI commands and a well-sequenced connection workflow with proper state handling. However, it is significantly bloated by the Ahrefs Overview section (~40 lines of feature descriptions) that adds no actionable value and wastes token budget. The introductory explanation of what Ahrefs is also wastes tokens on information Claude already knows.
Suggestions
Remove or drastically reduce the 'Ahrefs Overview' section — Claude doesn't need a feature catalog to use the CLI commands, and users can discover capabilities via `membrane action list --intent`.
Remove the introductory paragraph explaining what Ahrefs is ('popular SEO tool suite used by marketers...') as this is common knowledge for Claude.
Move the popular actions table to a separate reference file (e.g., ACTIONS.md) and link to it from the main skill to improve progressive disclosure and reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Ahrefs Overview' section is a lengthy catalog of features that Claude already knows or could look up, consuming significant tokens without adding actionable value. The introductory paragraph explaining what Ahrefs is ('popular SEO tool suite used by marketers...') is unnecessary context for Claude. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for authentication, connection setup, action discovery, action execution, and proxy requests, all with concrete syntax and flags. The popular actions table with keys and descriptions is directly usable. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and branching logic for different states. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the massive Ahrefs Overview feature catalog and the popular actions table are inlined when they could be in separate reference files. No bundle files are provided, and no external references are made to offload detailed content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.