mailchimp-automation
Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
83
80%
Does it follow best practices?
Impact
84%
1.23xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/mailchimp-automation/SKILL.mdQuality
Discovery
82%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 is a strong description that clearly identifies the platform (Mailchimp), the domain (email marketing), and specific capabilities (campaigns, audiences, subscribers, segments, analytics). Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The description is concise, uses third person voice correctly, and has excellent trigger term coverage.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Mailchimp, email campaigns, mailing lists, subscriber management, or email marketing analytics.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: campaigns, audiences, subscribers, segments, and analytics. Also specifies the integration method (Rube MCP/Composio) and includes a procedural note about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Mailchimp email marketing tasks), but lacks an explicit 'Use when...' clause. The when is only implied by the domain terms. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Mailchimp', 'email marketing', 'campaigns', 'audiences', 'subscribers', 'segments', 'analytics'. These cover the main terms a user would naturally use when requesting email marketing automation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Mailchimp' and 'Rube MCP (Composio)'. This is unlikely to conflict with other skills since it targets a very specific platform and integration method. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable Mailchimp automation skill with excellent workflow clarity, specific tool sequences, and important safety warnings around irreversible operations. Its main weakness is verbosity through repetition of pitfalls across sections and inline parameter documentation that could be offloaded to reference files. Trimming duplicated content and better leveraging progressive disclosure would significantly improve token efficiency.
Suggestions
Remove duplicated pitfalls (subscriber_hash casing, avg_open_rate fractions, pagination) that appear in both individual workflow sections and the Known Pitfalls section—keep them in one place only.
Move detailed parameter listings for each tool into a separate REFERENCE.md file and link to it, keeping only the most critical parameters inline in the workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy with significant repetition—pitfalls like subscriber_hash casing, avg_open_rate being 0-1, and pagination details are repeated across multiple sections. The Known Pitfalls section largely duplicates warnings already stated in individual workflows. The quick reference table adds value but the overall document could be tightened considerably. | 2 / 3 |
Actionability | The skill provides specific tool names, exact parameter names with double-underscore notation, concrete code for subscriber hash computation, clear tool sequences for each workflow, and detailed parameter descriptions. The guidance is highly specific and directly executable. | 3 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with prerequisite/required/optional labels, explicit validation steps (e.g., verify connection is ACTIVE, send test email before live send, check if contact exists before adding), and clear warnings about irreversible operations like SEND_CAMPAIGN. The campaign sending workflow includes an explicit approval checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's monolithic—all content is inline in a single file with no references to separate detailed documents. The parameter details and pitfalls for each workflow could be split into separate reference files, keeping the main skill leaner. | 2 / 3 |
Total | 10 / 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.