acumbamail
Acumbamail integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acumbamail data.
54
61%
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/acumbamail/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.
This description follows a generic integration template pattern ('Manage data, records, and automate workflows') that fails to communicate what Acumbamail actually does or what specific capabilities the skill provides. While it includes the product name as a trigger and has an explicit 'Use when' clause, the lack of domain-specific actions (email campaigns, subscriber management, etc.) and natural trigger terms significantly weakens its utility for skill selection.
Suggestions
Replace generic 'manage data, records, and automate workflows' with Acumbamail-specific actions like 'create and send email campaigns, manage subscriber lists, view campaign analytics, and create templates'.
Add natural trigger terms users would say, such as 'email marketing', 'mailing lists', 'subscribers', 'newsletters', 'email campaigns', or 'bulk email'.
Expand the 'Use when' clause to include specific scenarios like 'Use when the user mentions Acumbamail, email campaigns, subscriber lists, or email marketing automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Acumbamail (e.g., create email campaigns, manage subscriber lists, send newsletters, view campaign analytics). | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Acumbamail data) with an explicit 'Use when' clause, though both parts are quite generic. | 3 / 3 |
Trigger Term Quality | It includes 'Acumbamail' as a key trigger term which is distinctive, but lacks natural keywords users might say such as 'email campaigns', 'mailing lists', 'subscribers', 'newsletters', or 'email marketing'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Acumbamail' provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills that use identical boilerplate language. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands and a clear connection setup workflow, making it practically useful. However, it suffers from some verbosity (introductory explanation, a large table with empty descriptions), and lacks validation/verification steps for destructive and batch operations. The content could benefit from splitting detailed reference material into separate files and adding safety checkpoints.
Suggestions
Add validation/confirmation steps for destructive operations (delete-list, delete-subscriber) and batch operations (batch-add-subscribers, batch-delete-subscribers) — e.g., 'list current subscribers before deleting' or 'verify count after batch add'.
Remove or populate the 'No description' entries in the popular actions table — empty descriptions waste tokens without adding value.
Remove the introductory paragraph explaining what Acumbamail is, as Claude already knows this and it wastes context window tokens.
Consider splitting the proxy requests section and the popular actions table into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Acumbamail is an email marketing platform. It's used by businesses and marketers...') and the popular actions table has 'No description' for every entry, adding bulk without value. The Membrane CLI setup and auth flow sections are reasonably efficient but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Flag tables and JSON parameter examples make it fully executable. | 3 / 3 |
Workflow Clarity | The connection setup workflow is well-sequenced with state handling (READY, CLIENT_ACTION_REQUIRED, errors), but batch operations like 'batch-add-subscribers' and 'batch-delete-subscribers' lack any validation or feedback loop guidance. Destructive operations (delete-list, delete-subscriber) have no verification steps, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's somewhat monolithic — the proxy request details, popular actions table, and connection state machine could be split into referenced files. No bundle files exist to offload detail, and the document is long for a single SKILL.md. | 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.