Name: mailchimp
Rating: 60.8 (1 reviews)
Author: membranedev

mailchimp

Mailchimp integration. Manage marketing automation data, records, and workflows. Use when the user wants to interact with Mailchimp data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mailchimp/SKILL.md

Quality

Content

68%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 body is highly actionable with concrete, executable Membrane CLI commands and a useful actions table, and its connection workflow has a real polling feedback loop. It is held back by conceptual/marketing padding and by the absence of validation steps after mutating actions.

Suggestions

Trim the opening paragraph that explains what Mailchimp is and tighten the marketing phrasing in 'Best practices' so every token earns its place.

Add an explicit validation/verification step after running mutating actions (e.g., re-fetch with get-member or get-audience to confirm the change took effect) so the destructive workflow has a feedback loop.

Label the post-connection workflow explicitly as 'Step 2' (or remove the dangling 'skip to Step 2' reference) so the connection→search→run sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI command examples, but it opens by explaining what Mailchimp is ('Mailchimp is a marketing automation platform primarily used for email marketing...') and uses marketing phrasing in best practices ('burn less tokens and make communication more secure'), which is unnecessary padding Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every phase (install, login, connection ensure/get, action list/run, request proxy) plus a concrete popular-actions table with real keys, covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with a READY/BUILDING polling feedback loop, but the skill drives mutating create/update/delete-style actions (create-audience, update-member, add-member-to-list) with no verification step afterward, so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and no bundle files, but the ~20-row popular-actions table is inlined in a single file with no separate reference split, placing it at 'good structure, minor organization gaps' rather than the ideal one-level-deep reference pattern.	4 / 5
	Total	15 / 20 Passed

Description

73%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 a solid, third-person trigger-style statement that clearly names the Mailchimp niche and includes an explicit 'Use when' clause. Its main weakness is generic, non-comprehensive action language ('manage data, records, and workflows') rather than enumerating concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Mailchimp integration', 'marketing automation') and a few concrete action areas ('Manage marketing automation data, records, and workflows'), but 'manage ... data, records, and workflows' is generic rather than a comprehensive list of specific actions, matching the anchor that names the domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage marketing automation data, records, and workflows') and 'when' ('Use when the user wants to interact with Mailchimp data'), but the 'when' clause is narrow and the 'what' is somewhat generic, so it sits at 4 rather than the fully concrete 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say — 'Mailchimp', 'marketing automation', and 'interact with Mailchimp data' — giving good keyword coverage, though it misses common synonyms/variations, fitting the 'good coverage, a few natural terms missing' anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	'Mailchimp integration' targets a specific named product with distinct triggers, giving it a clear niche and minimal conflict risk with other skills, matching the top anchor.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/mailchimp/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.