accuranker
Accuranker integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accuranker data.
49
53%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/accuranker/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 the specific product (Accuranker) and including an explicit 'Use when' clause, but it is severely lacking in specificity of capabilities. The actions described ('manage data, records, and automate workflows') are boilerplate phrases that could apply to any integration and give Claude no meaningful information about what Accuranker actually does (SEO rank tracking, keyword monitoring, SERP analysis).
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with concrete Accuranker-specific actions such as 'track keyword rankings, monitor SERP positions, analyze SEO performance data, manage keyword lists'.
Add natural trigger terms users would actually say, such as 'SEO rankings', 'keyword tracking', 'rank tracker', 'SERP data', 'search engine positions'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user asks about SEO rankings, keyword positions, rank tracking, or wants to pull data from Accuranker'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Accuranker. These are generic phrases that could apply to virtually any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Accuranker data) with an explicit trigger clause, though both are quite generic in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Accuranker' as a key trigger term which is specific and useful, but lacks natural keywords users might say such as 'SEO rankings', 'keyword tracking', 'SERP data', 'rank tracking', or other domain-specific terms associated with Accuranker. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Accuranker' provides some distinctiveness since it's a specific product name, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration skills. Without domain-specific terms like SEO or rank tracking, it's not maximally distinct. | 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 concrete, executable CLI commands and a useful popular actions table, making it highly actionable. However, it suffers from significant verbosity: the introductory explanation of Accuranker, the generic Membrane boilerplate (authentication, connection states), and the bare entity-type bullet list all consume tokens without adding Accuranker-specific value. The workflow is reasonably clear for connection setup but lacks validation/error-handling guidance for action execution.
Suggestions
Remove the introductory paragraph explaining what Accuranker is and the bare 'Accuranker Overview' bullet list — Claude already knows this and the list provides no actionable guidance.
Extract the generic Membrane CLI setup, authentication, and connection management instructions into a shared reference file, keeping only Accuranker-specific details inline.
Add error handling guidance for action execution — e.g., what to do when `membrane action run` fails, returns empty output, or hits rate limits.
Consider adding a concrete end-to-end example (e.g., 'List all keywords for a domain') showing the full flow from connection to action output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Accuranker is and who uses it — information Claude already knows or can infer. The 'Accuranker Overview' section is a bare bullet list of entity types with no actionable value. There's also significant boilerplate about Membrane CLI setup, authentication flows, and connection state handling that appears to be generic across all Membrane-based skills rather than Accuranker-specific. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installing the CLI, authenticating, creating connections, searching for actions, running actions, and making proxy requests. The popular actions table with specific keys and the input parameter syntax are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence (ensure → wait → check state → proceed), and the state machine for CLIENT_ACTION_REQUIRED is well-documented. However, there are no explicit validation checkpoints or error recovery feedback loops for the action execution workflow itself — e.g., no guidance on what to do if an action run fails or returns unexpected output. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's monolithic — all content is inline in a single file with no references to supporting documents. The Membrane CLI setup and authentication boilerplate could be extracted to a shared reference, and the popular actions table could link to more detailed usage examples in separate files. | 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
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.