acelle-mail
Acelle Mail integration. Manage Users. Use when the user wants to interact with Acelle Mail data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill acelle-mail61
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 identifies a specific product (Acelle Mail) and includes a 'Use when' clause, but fails to articulate concrete capabilities beyond vague 'Manage Users' and 'interact with data.' The lack of specific actions (e.g., create campaigns, manage subscribers, view analytics) and missing natural trigger terms significantly weaken its utility for skill selection.
Suggestions
List specific concrete actions like 'create/update/delete users, manage subscriber lists, configure campaigns, view email analytics'
Add natural trigger terms users would say: 'email marketing', 'subscriber management', 'mailing lists', 'email campaigns'
Make the 'Use when' clause more specific: 'Use when the user mentions Acelle Mail, email marketing automation, or needs to manage email subscribers and campaigns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Manage Users' as a concrete action, which is vague. 'Interact with Acelle Mail data' is abstract and doesn't specify what operations are possible beyond user management. | 1 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when' question, but the 'what' is weak ('Manage Users' and 'interact with data' are too vague). The trigger condition 'interact with Acelle Mail data' is overly broad. | 2 / 3 |
Trigger Term Quality | Includes 'Acelle Mail' as a specific product name which users would say, but lacks natural variations or related terms (e.g., 'email marketing', 'subscriber lists', 'campaigns', 'mailing lists'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Acelle Mail' is a specific product name which helps distinctiveness, but 'Manage Users' and 'interact with data' are generic enough to potentially overlap with other user management or data 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 a useful action reference table. However, it includes unnecessary introductory explanation about what Acelle Mail is, and lacks validation checkpoints in the workflow steps. The structure could benefit from clearer progressive disclosure with external references for the detailed action catalog.
Suggestions
Remove the introductory paragraph explaining what Acelle Mail is - Claude already knows this context
Add validation/verification steps after key commands (e.g., 'Verify connection succeeded by running membrane connection list')
Consider moving the large action table to a separate ACTIONS.md file and linking to it for better progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Acelle Mail is a self-hosted email marketing application, similar to MailChimp' - Claude knows this). The overview hierarchy and some prose could be tightened, but the action table and command examples are efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, a comprehensive action table with exact action keys, and concrete examples for running actions with JSON input. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No explicit error handling or verification steps after running commands. The 'First-time setup' and 'Connecting' sections list steps but don't include feedback loops for failures. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file with no references to external documentation for advanced topics. The action table is inline rather than linked, and there's no separation of quick-start vs. advanced content. | 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.