acelle-mail
Acelle Mail integration. Manage Users. Use when the user wants to interact with Acelle Mail data.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/acelle-mail/SKILL.mdQuality
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.
The description is minimal and lacks specificity in both capabilities and trigger terms. While it correctly names the product (Acelle Mail) and includes a 'Use when' clause, the actions described are too vague ('Manage Users', 'interact with data') to help Claude confidently select this skill or understand its full scope.
Suggestions
List specific concrete actions such as 'Create, update, delete, and list users; manage subscriber lists; configure sending servers' instead of just 'Manage Users'.
Expand the 'Use when' clause with natural trigger terms like 'email marketing platform', 'subscriber management', 'mailing lists', 'Acelle API', or 'email campaigns'.
Add more detail about what 'Acelle Mail data' encompasses to distinguish this skill from generic user management or other email platform integrations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage Users' which is a single vague action. It doesn't list concrete actions like create users, delete users, update permissions, list subscribers, etc. 'Interact with Acelle Mail data' is abstract language. | 1 / 3 |
Completeness | It has a weak 'what' (Manage Users) and a 'Use when' clause, but the trigger is extremely vague ('interact with Acelle Mail data'). The 'when' doesn't provide explicit, useful triggers beyond restating the product name. It technically has a 'Use when' clause so it's not capped at 2 by the missing clause rule, but the clause itself is nearly vacuous. | 2 / 3 |
Trigger Term Quality | It includes 'Acelle Mail' which is a specific product name users would mention, and 'Users' as a keyword. However, it's missing common variations and related terms like 'email marketing', 'subscribers', 'mailing lists', 'campaigns', or specific API operations. | 2 / 3 |
Distinctiveness Conflict Risk | 'Acelle Mail' is a specific product which helps distinctiveness, but 'Manage Users' is generic enough to overlap with any user management skill. The description doesn't clearly delineate its scope from other email or user management tools. | 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 is a functional integration skill with strong actionability — every operation has concrete CLI commands ready to execute. Its main weaknesses are verbosity in the introductory sections (explaining what Acelle Mail is), a large inline actions table that could be referenced externally, and missing validation/error-handling guidance for destructive operations like deletions and campaign launches.
Suggestions
Remove the introductory paragraph explaining what Acelle Mail is — Claude doesn't need this context, and the skill description already covers it.
Add validation or confirmation steps for destructive operations (delete-subscriber, delete-list, run-campaign) to prevent accidental data loss.
Move the popular actions table to a separate reference file (e.g., ACTIONS.md) and link to it, keeping SKILL.md leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Acelle Mail is (similar to MailChimp, used by businesses, etc.) is unnecessary context Claude doesn't need. The overview hierarchy and popular actions table are useful but could be more compact. Some sections like best practices repeat what's already implied. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command includes specific flags and options. | 3 / 3 |
Workflow Clarity | The workflow for authentication (including headless environments) and action creation (with polling states) is well-sequenced. However, there are no validation checkpoints for destructive operations like delete-subscriber or delete-list, and no error recovery guidance for failed action runs. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the popular actions table (20 rows) and the full overview hierarchy could be split into a reference file. The skill links to official docs but doesn't split its own content across files despite being fairly long. | 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
56d7336
- 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.