ahrefs
Ahrefs integration. Manage Projects. Use when the user wants to interact with Ahrefs data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill ahrefs61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description correctly identifies the tool (Ahrefs) and includes a 'Use when' clause, but fails to describe what specific capabilities the skill provides. 'Manage Projects' is too vague for an SEO tool that likely handles backlink analysis, keyword tracking, and site audits. Users searching for SEO-related help may not trigger this skill due to missing domain-specific keywords.
Suggestions
Replace 'Manage Projects' with specific Ahrefs capabilities like 'analyze backlinks, track keyword rankings, audit site SEO, monitor domain authority'
Add natural SEO trigger terms to the 'Use when' clause: 'backlinks', 'keyword research', 'SEO analysis', 'domain rating', 'competitor analysis'
Expand the trigger condition from 'interact with Ahrefs data' to specific scenarios like 'when analyzing SEO metrics, researching keywords, or checking backlink profiles'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Manage Projects' which is vague and abstract. It doesn't list concrete actions like 'analyze backlinks', 'track keyword rankings', or 'audit site SEO'. | 1 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when' question, but the 'what' is extremely weak ('Manage Projects' is not descriptive). The trigger condition 'interact with Ahrefs data' is also vague. | 2 / 3 |
Trigger Term Quality | Includes 'Ahrefs' which is a specific tool name users would mention, but lacks natural SEO-related keywords users might say like 'backlinks', 'keyword research', 'SEO analysis', 'domain rating', or 'site audit'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Ahrefs' is a distinct tool name that reduces conflict risk, but 'Manage Projects' and 'interact with data' are generic phrases that could overlap with other project management or data integration skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable guidance with executable CLI commands and a useful action reference table. However, it's weakened by verbose introductory content explaining what Ahrefs is, an overly detailed feature overview that doesn't add operational value, and missing validation steps in the connection workflow.
Suggestions
Remove or drastically shorten the introductory paragraph and 'Ahrefs Overview' section - Claude doesn't need to know what Ahrefs is or its feature list to use the API
Add explicit validation steps after connection setup (e.g., 'Verify connection: membrane connection list --json | grep ahrefs')
Move the detailed feature overview to a separate REFERENCE.md file and link to it for users who need feature discovery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Ahrefs is a popular SEO tool suite used by marketers...') and the extensive feature overview section could be trimmed since Claude can infer most of this from context. However, the actionable sections are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable commands throughout - CLI installation, login, connection setup, action discovery, and proxy requests all have copy-paste ready examples with clear flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. The workflow doesn't specify how to verify successful connection or handle authentication failures beyond mentioning headless environments. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Ahrefs Overview' section is a large block that could be moved to a reference file. The skill links to external docs but doesn't structure internal content across multiple files. | 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 | |
- 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.