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 ./plugins/all-skills/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.
The description is strong in specificity and distinctiveness, clearly naming the platform (Mailchimp), the integration method, and multiple concrete capabilities. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The natural trigger terms are well-chosen and cover the key concepts users would mention.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Mailchimp, email campaigns, mailing lists, newsletter management, or subscriber management.'
| 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 instruction to search tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Mailchimp email marketing tasks), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the domain terms mentioned. | 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, clear tool sequences, and useful pitfall documentation. Its main weaknesses are repetition across sections (subscriber_hash, pagination, rate stats mentioned multiple times) and the monolithic structure that could benefit from splitting reference material into separate files. The content would be more token-efficient if deduplicated and if some parameter documentation were trimmed given the instruction to always check RUBE_SEARCH_TOOLS for current schemas.
Suggestions
Deduplicate repeated pitfalls (subscriber_hash casing, avg_open_rate format, pagination) by consolidating them in the Known Pitfalls section only and removing duplicates from individual workflow sections.
Consider moving the Quick Reference table and detailed parameter listings to a separate REFERENCE.md file, since the skill already instructs users to call RUBE_SEARCH_TOOLS for current schemas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but contains significant repetition—pitfalls like subscriber_hash casing, avg_open_rate being 0-1, and pagination details are repeated across multiple sections. The quick reference table at the end largely duplicates information already covered in the workflow sections. Some parameter documentation could be trimmed since the skill itself says to always call RUBE_SEARCH_TOOLS first for current schemas. | 2 / 3 |
Actionability | The skill provides specific tool names, exact parameter names with double-underscore notation, concrete tool sequences for each workflow, and an executable code snippet for computing subscriber hashes. The guidance is copy-paste ready with specific parameter values and clear required/optional annotations. | 3 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with Required/Optional/Prerequisite annotations. The campaign sending workflow includes explicit validation steps (send test email, get user approval before irreversible send). The setup section has a clear 4-step verification sequence. Pitfalls sections serve as error-recovery guidance for each workflow. | 3 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files to reference. While it has good internal section structure, the document is very long (~200+ lines of dense content) with the quick reference table, known pitfalls, and common patterns sections that could be split into separate reference files. The repeated information across sections suggests the content would benefit from better factoring. | 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
- davepoon/buildwithclaude
- Commit
d065ead
- 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.