ahrefs
Ahrefs integration. Manage Projects. Use when the user wants to interact with Ahrefs data.
62
53%
Does it follow best practices?
Impact
Pending
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 benefits from naming a specific product (Ahrefs) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what actions the skill can perform. The vague phrases 'Manage Projects' and 'interact with Ahrefs data' give almost no information about concrete capabilities, making it hard for Claude to confidently select this skill over others.
Suggestions
List specific concrete actions the skill supports, e.g., 'Create and manage Ahrefs projects, analyze backlink profiles, track keyword rankings, run site audits, export organic traffic data.'
Add natural trigger terms users would say, such as 'backlinks', 'SEO analysis', 'keyword research', 'domain rating', 'site audit', 'organic search'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user asks about SEO metrics, backlink analysis, keyword rankings, or wants to manage Ahrefs projects.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage Projects' and 'interact with Ahrefs data' which are extremely vague. No concrete actions are listed—what does 'manage projects' entail? What kind of data interactions are supported? | 1 / 3 |
Completeness | It does answer both 'what' (Ahrefs integration, manage projects) and 'when' (Use when the user wants to interact with Ahrefs data). The 'Use when...' clause is present and explicit, though both parts are quite shallow. | 3 / 3 |
Trigger Term Quality | 'Ahrefs' is a strong trigger term for users who know the tool, and 'projects' is somewhat relevant. However, it lacks natural keywords users might say like 'backlinks', 'SEO', 'keyword research', 'site audit', 'domain rating', or 'organic traffic'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Ahrefs' is a specific product name which helps distinctiveness, but 'Manage Projects' and 'interact with data' are generic enough that it could overlap with other SEO or project management tools. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
50%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 CLI commands and a useful popular actions table, but is significantly bloated by the Ahrefs Overview section which catalogs features Claude doesn't need explained. The workflow is mostly clear but lacks explicit validation checkpoints for action execution, and the document could benefit from better progressive disclosure by moving reference material to separate files.
Suggestions
Remove or drastically reduce the 'Ahrefs Overview' section — Claude already knows what Ahrefs features are, and this information is available via the linked API docs. This would save ~40 lines of tokens.
Remove the introductory paragraph explaining what Ahrefs is ('Ahrefs is a popular SEO tool suite...') as this is common knowledge for Claude.
Add explicit validation/verification steps after running actions (e.g., check output field for errors, verify expected data shape) to improve workflow clarity.
Consider moving the popular actions table to a separate reference file and linking to it, keeping SKILL.md focused on the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Ahrefs Overview' section is a lengthy catalog of features that Claude already knows or could infer from the API docs. It adds ~40 lines of descriptive bullet points that don't provide actionable guidance. The introductory paragraph explaining what Ahrefs is wastes tokens on common knowledge. | 1 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installing the CLI, authenticating, connecting, searching for actions, creating actions, polling, and running actions with JSON input. The popular actions table with keys is directly usable. | 3 / 3 |
Workflow Clarity | The workflow steps (install → authenticate → connect → search/create → run) are present and sequenced, but there's no explicit validation or error-handling feedback loop for running actions. The action creation section has a polling loop with state checks, which is good, but the overall flow lacks numbered end-to-end sequencing and verification checkpoints. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with headers, but the massive 'Ahrefs Overview' feature catalog is inlined when it could be omitted or linked externally. The popular actions table is useful inline, but the overall document is monolithic with no references to separate files for advanced topics. | 2 / 3 |
Total | 8 / 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
56d7336
- 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.