accuranker
Accuranker integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accuranker data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill accuranker61
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 relies heavily on the brand name 'Accuranker' for identification but fails to explain what the tool actually does or what specific capabilities are available. The generic phrases 'manage data, records, and automate workflows' could describe almost any integration and provide no meaningful guidance for skill selection.
Suggestions
Replace generic phrases with specific Accuranker capabilities like 'track keyword rankings, monitor SERP positions, analyze SEO performance metrics'
Add natural trigger terms users would say: 'SEO rankings', 'keyword tracking', 'search position', 'SERP monitoring'
Expand the 'Use when...' clause with specific scenarios: 'Use when the user wants to check keyword rankings, monitor SEO performance, or analyze search visibility data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what Accuranker actually does (SEO rank tracking) or what specific operations are available. | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when' question, but the 'what' is extremely vague. The description tells Claude to use it for 'Accuranker data' but doesn't explain what that data is or what meaningful actions can be performed. | 2 / 3 |
Trigger Term Quality | Includes 'Accuranker' as a trigger term which users familiar with the tool would use, but lacks natural keywords like 'SEO', 'rank tracking', 'keyword rankings', 'SERP', or 'search rankings' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic language that could apply to dozens of integrations. Only the 'Accuranker' brand name provides distinctiveness, which helps but the generic verbs create overlap risk with other data management 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 CLI commands for Accuranker integration via Membrane, with good coverage of common operations and proxy requests. However, it wastes tokens on introductory explanations Claude doesn't need and lacks validation/error-handling guidance for the multi-step connection workflow. The overview bullet list is particularly unhelpful without context on what each item means or how to use it.
Suggestions
Remove the opening paragraph explaining what Accuranker is - Claude already knows this
Either remove the 'Accuranker Overview' bullet list or transform it into actionable guidance showing how these entities map to specific actions
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep accuranker') and error recovery guidance for failed auth
Add example output snippets showing what successful command responses look like to help Claude verify operations succeeded
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Accuranker is, which Claude likely already knows. The overview section is a bare list without actionable context. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands for all operations: installation, login, connection, action discovery, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Accuranker Overview' bullet list adds little value and could be removed. Links to external docs are provided but internal structure could be tighter. | 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.