acumbamail
Acumbamail integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acumbamail data.
59
49%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/acumbamail/SKILL.mdQuality
Discovery
35%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 product name 'Acumbamail' for identification but fails to explain what Acumbamail actually is (an email marketing platform) or what specific actions can be performed. The generic phrases 'manage data, records, and automate workflows' could apply to almost any integration, and the trigger guidance is circular rather than helpful.
Suggestions
Add domain-specific trigger terms users would naturally say: 'email marketing', 'campaigns', 'subscribers', 'mailing lists', 'newsletters', 'email automation'
Replace generic actions with Acumbamail-specific capabilities: 'Create and send email campaigns, manage subscriber lists, track open rates and click-through analytics'
Expand the 'Use when...' clause with concrete scenarios: 'Use when the user wants to send marketing emails, manage email subscribers, create newsletters, or analyze campaign performance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Acumbamail) and mentions general actions ('Manage data, records, and automate workflows'), but these are generic and not specific to what Acumbamail actually does (email marketing, campaigns, subscribers, etc.). | 2 / 3 |
Completeness | Has a 'Use when...' clause but it's circular ('interact with Acumbamail data'). The 'what' is vague ('manage data, records') and the 'when' doesn't provide meaningful trigger guidance beyond the product name. | 2 / 3 |
Trigger Term Quality | Only includes 'Acumbamail' as a trigger term. Missing natural keywords users would say like 'email marketing', 'campaigns', 'subscribers', 'mailing lists', or 'newsletters'. | 1 / 3 |
Distinctiveness Conflict Risk | The Acumbamail name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with many other 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 clear syntax examples. However, it lacks validation checkpoints for destructive batch operations, includes some unnecessary explanatory content, and the popular actions table with empty descriptions adds bulk without value. The workflow could be strengthened with explicit error handling and verification steps.
Suggestions
Add validation/verification steps for batch operations (batch-add-subscribers, batch-delete-subscribers) with error recovery guidance
Remove or populate the 'No description' entries in the popular actions table - either add meaningful descriptions or remove the table entirely
Remove the introductory paragraph explaining what Acumbamail is - Claude already knows this
Add an example showing how to verify a successful action execution or handle common errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Acumbamail is an email marketing platform' description that Claude doesn't need). The popular actions table has 'No description' for every entry, adding bulk without value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for connection setup, action discovery, and execution. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. Batch operations (batch-add-subscribers, batch-delete-subscribers) are mentioned without any validation or error recovery guidance, which should cap this at 2 per rubric guidelines. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the popular actions table is verbose inline content that could be referenced externally. The overview section ('Lists > Subscribers, Templates, Campaigns') adds little value and could be removed or expanded meaningfully. | 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
d19a82b
- 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.