CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.23x
Quality

80%

Does it follow best practices?

Impact

84%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/mailchimp-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 clear workflow sequences, specific tool names, and useful pitfall warnings. Its main weaknesses are repetition across sections (subscriber_hash, pagination, rate stats mentioned multiple times) and the monolithic structure that could benefit from splitting detailed parameter references and the quick reference table into separate files. The content is well-structured within its single file but would benefit from tighter editing to eliminate redundancy.

Suggestions

Deduplicate repeated pitfalls (subscriber_hash casing, avg_open_rate format, pagination) by consolidating them only in the 'Known Pitfalls' section and removing from individual workflow pitfalls.

Consider moving the detailed parameter documentation and the quick reference table to separate bundle files (e.g., PARAMETERS.md, REFERENCE.md) to keep SKILL.md as a concise overview with pointers.

DimensionReasoningScore

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 vs optional distinctions.

3 / 3

Workflow Clarity

Each workflow has a clearly numbered tool sequence with prerequisite/required/optional 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. Error recovery guidance is provided in pitfalls sections.

3 / 3

Progressive Disclosure

The content is a monolithic single file at ~200+ lines with no bundle files to offload detailed parameter documentation or the large reference table. The detailed parameter lists for each workflow and the extensive quick reference table could be split into separate reference files, keeping the SKILL.md as a leaner overview with pointers.

2 / 3

Total

10

/

12

Passed

Description

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 (Rube MCP/Composio), and multiple concrete capabilities. Its main weakness is the lack of an explicit 'Use when...' clause, which caps completeness at 2. 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, subscriber management, or email marketing analytics.'

DimensionReasoningScore

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 specific platform and integration method.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.