acymailing
AcyMailing integration. Manage data, records, and automate workflows. Use when the user wants to interact with AcyMailing data.
61
52%
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/acymailing/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.
This description relies heavily on the product name 'AcyMailing' for identification but fails to explain what AcyMailing actually does or what specific capabilities the skill provides. The generic phrases 'manage data, records, and automate workflows' could describe virtually any integration skill, making it difficult for Claude to select this skill appropriately unless the user explicitly mentions AcyMailing by name.
Suggestions
Replace vague actions with specific AcyMailing capabilities like 'create email campaigns, manage subscriber lists, schedule newsletters, track email analytics'
Add natural trigger terms users would say: 'email marketing', 'newsletter', 'mailing list', 'subscribers', 'email campaigns', 'bulk email'
Expand the 'Use when' clause with specific scenarios: 'Use when the user wants to send newsletters, manage email subscribers, create marketing campaigns, or automate email workflows'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what specific operations can be performed with AcyMailing (e.g., create campaigns, manage subscribers, send newsletters). | 1 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when' question, but the 'what' is extremely vague ('manage data, records, and automate workflows' could apply to almost any integration). The trigger condition 'interact with AcyMailing data' is circular and unhelpful. | 2 / 3 |
Trigger Term Quality | Includes 'AcyMailing' as a specific product name which is a good trigger term, but lacks natural variations users might say like 'email marketing', 'newsletter', 'mailing list', 'subscribers', or 'email campaigns'. | 2 / 3 |
Distinctiveness Conflict Risk | The AcyMailing product name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to conflict with many other integration skills. Only users who already know they need AcyMailing would trigger this correctly. | 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 CLI commands for AcyMailing integration via Membrane, with good coverage of common operations. However, it includes unnecessary introductory content about what AcyMailing is, lacks validation checkpoints in workflows, and could benefit from better progressive disclosure for advanced use cases.
Suggestions
Remove the introductory paragraph explaining what AcyMailing is - Claude already knows this and can infer from context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (e.g., expired credentials, invalid action IDs)
Remove or condense the 'AcyMailing Overview' bullet list which provides no actionable information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., explaining what AcyMailing is, which Claude can infer from context), and the overview section with bullet points adds little value. However, the CLI commands and action table are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands for installation, login, connection setup, action discovery, and running actions. The commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but there are no validation checkpoints or error recovery guidance. The workflow for first-time setup vs. existing connections is present but lacks explicit verification steps. | 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 popular actions table could be split out if it grows, and there's no clear navigation to deeper resources. | 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.