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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/mailchimp-automation/SKILL.md

The canonical home for this skill is mailchimp-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete tool sequences and parameters, but suffers from redundancy across sections and lacks enforced validation checkpoints for the irreversible send operation. Splitting reference material into a bundle file and de-duplicating pitfalls would tighten it.

Suggestions

Promote the test-email + explicit-user-approval guard from an [Optional] pitfall to a mandatory validation checkpoint inside the send-campaign workflow sequence.

De-duplicate pitfalls (subscriber_hash casing, double-underscore notation, 0-1 rate fractions) by stating each once and cross-referencing, and consider moving the Quick Reference table to a references/ file.

Add a short end-to-end executable example showing one complete create-set-test-send sequence with real parameter values.

DimensionReasoningScore

Conciseness

The body is mostly action-oriented but repeats several facts across sections — subscriber_hash MD5-of-lowercase, double-underscore param notation, and avg_open_rate being a 0-1 fraction each appear twice, and the Quick Reference table duplicates workflow content.

3 / 5

Actionability

Provides concrete tool slugs, specific key parameters per operation, and an executable Python snippet for computing subscriber_hash, with only minor gaps (no full end-to-end request examples).

4 / 5

Workflow Clarity

Steps are clearly numbered per workflow, but the irreversible MAILCHIMP_SEND_CAMPAIGN exposes its test-email/user-approval guard only as an [Optional] step and a pitfall rather than an enforced validation checkpoint, triggering the destructive-operation cap at 3.

3 / 5

Progressive Disclosure

No bundle files exist and all ~227 lines are inline; although well-sectioned, the full Quick Reference table and per-tool parameter catalogs are reference material that would be better split into a separate file.

3 / 5

Total

13

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 specific, distinct, and rich in natural trigger terms, but it omits an explicit "Use when…" trigger clause, which caps its completeness. Adding a concrete usage-trigger sentence would lift the weakest dimension.

Suggestions

Append an explicit trigger clause such as "Use when the user wants to manage Mailchimp campaigns, audiences, subscribers, segments, or email analytics."

Add natural synonyms ("newsletter", "mailing list") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — "campaigns, audiences, subscribers, segments, and analytics" — giving comprehensive coverage of Mailchimp automation actions rather than vague abstraction.

5 / 5

Completeness

Clearly states the "what" but lacks an explicit "Use when…" trigger clause; "Always search tools first for current schemas" is an instruction rather than a usage trigger, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("Mailchimp", "email marketing", "campaigns", "subscribers", "segments", "analytics") but omits common synonyms such as "newsletter" or "mailing list".

4 / 5

Distinctiveness Conflict Risk

The phrase "Mailchimp email marketing… via Rube MCP (Composio)" carves out a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.