acymailing
AcyMailing integration. Manage data, records, and automate workflows. Use when the user wants to interact with AcyMailing data.
44
45%
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/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.
The description relies heavily on the product name 'AcyMailing' for identification but fails to describe what AcyMailing actually is or what specific actions the skill can perform. The language is generic and could apply to almost any integration skill, with the 'Use when' clause being circular rather than informative.
Suggestions
Add specific concrete actions like 'Create and send email campaigns, manage subscriber lists, track open rates, and configure automated email sequences'.
Expand trigger terms to include natural language users would say: 'email campaigns', 'newsletters', 'subscriber lists', 'mailing lists', 'email marketing', 'email automation'.
Make the 'Use when' clause more descriptive: 'Use when the user needs to manage email marketing campaigns, subscriber lists, newsletters, or email automation through AcyMailing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to AcyMailing. There are no specific capabilities mentioned such as creating campaigns, managing subscriber lists, or sending emails. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and includes a 'Use when' clause, but the trigger is essentially circular ('when the user wants to interact with AcyMailing data') and doesn't provide meaningful guidance on when to select this skill. | 2 / 3 |
Trigger Term Quality | It includes 'AcyMailing' as a key trigger term, but lacks natural keywords users would actually say like 'email campaigns', 'newsletters', 'subscriber lists', 'mailing lists', or 'email marketing'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AcyMailing' provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many integration or data management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic Membrane CLI integration template with AcyMailing branding. The actionability is strong with executable commands throughout, but the content is bloated with boilerplate explanations (what AcyMailing is, how Membrane works) that aren't specific to this integration. The popular actions table with empty descriptions wastes tokens without adding value.
Suggestions
Remove the introductory paragraph explaining what AcyMailing is — Claude already knows this, and the skill description covers it.
Fill in the Description column of the popular actions table or remove it; empty cells waste tokens without providing actionable guidance.
Extract the generic Membrane CLI setup (install, auth, connection, proxy) into a shared reference file and keep only AcyMailing-specific content inline.
Add a concrete end-to-end example (e.g., creating a list and subscribing a user) with expected output to demonstrate the full workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what AcyMailing is, what it does, and who uses it — all things Claude can infer or look up. The Membrane CLI setup, authentication flow, and connection state machine are verbose and generic (not AcyMailing-specific). The popular actions table has empty description columns, wasting tokens. Much of this content is boilerplate shared across many Membrane-based skills. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installing the CLI, authenticating, creating connections, searching for actions, running actions, and making proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON parameter examples. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, errors), but there are no explicit validation checkpoints after running actions or campaigns. The overall flow from install → auth → connect → discover → run is present but lacks error recovery guidance for action execution failures. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. The Membrane CLI boilerplate (authentication, connection setup, proxy requests) could be extracted to a shared reference file. The AcyMailing overview section is too thin to justify its own section, while the generic Membrane content is too long to be inline. | 2 / 3 |
Total | 8 / 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.