CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-mailchimp

CLI harness for the Mailchimp Marketing API v3.0 — 303 commands across 30 resource groups (lists, campaigns, reports, automations, ecommerce, templates, and more). Supports JSON output and interactive REPL mode.

Quality

72%

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 ./mailchimp/agent-harness/cli_anything/mailchimp/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

This is a well-organized, highly actionable CLI reference with executable examples throughout and genuinely useful non-obvious details (subscriber hashing, rate limits). Its weaknesses are the inlined bulk command catalog that belongs in a reference file and the absence of safety/validation guidance around destructive and batch operations, plus one inconsistent command name in the patterns section.

Suggestions

Move the full command tables (Root through Other Resources, ~110 lines) into a references/COMMANDS.md file, keeping only the most common commands and patterns inline.

Add validation guidance for destructive/batch operations, e.g. verify a campaign's send-checklist before `campaigns send`, and confirm list/campaign IDs before delete commands.

Fix the command-name inconsistency: `lists create-members` in Common Agent Patterns should match the documented `lists create-lists-id-members`.

DimensionReasoningScore

Conciseness

The body is dense reference material — terse command tables, envelope shapes, and non-obvious notes (MD5 subscriber hash, datacenter suffix) with no padding about concepts Claude already knows. Minor instances of trimmable content remain (the ~13-line REPL transcript and the Root table), so it fits 'efficient; minor over-explanation' rather than 'every token earns its place'.

4 / 5

Actionability

Commands are copy-paste ready with real JSON payloads, jq pipelines, and a working MD5 hash one-liner. One concrete gap: the pattern `lists create-members <list_id>` contradicts the command table's `lists create-lists-id-members <LIST_ID>`, so that example would not execute as written — 'mostly executable with minor gaps'.

4 / 5

Workflow Clarity

Multi-step agent patterns exist (create campaign → send-checklist → filter unmet items), but destructive and batch operations (`lists delete`, `campaigns send`, the `batches` group) have no validation or confirmation guidance. The rubric explicitly caps workflow clarity at 3 for batch/destructive skills missing feedback loops.

3 / 5

Progressive Disclosure

Section headers and tables give the body decent structure, but ~110 lines of full command catalog are inlined in SKILL.md with no bundle files at all — content that clearly belongs in a one-level-deep reference file, matching 'content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

65%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 and highly distinctive thanks to the Mailchimp branding and quantified scope, but it describes the interface rather than user-facing actions and entirely lacks a 'when to use' trigger clause. Adding a 'Use when…' sentence and action verbs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Mailchimp audiences, subscribers, email campaigns, or marketing reports.'

Replace passive scope statements with concrete actions, e.g. 'create and send email campaigns, manage audience members and tags, pull campaign reports.'

Include natural synonyms users actually say — 'audiences', 'subscribers', 'newsletter', 'email marketing' — alongside the resource-group names.

DimensionReasoningScore

Specificity

The description names the domain ('CLI harness for the Mailchimp Marketing API v3.0', '303 commands across 30 resource groups') and two concrete interface features ('Supports JSON output and interactive REPL mode'), but lists no action verbs for what the commands do — resource-group names (lists, campaigns, reports) are topics, not the specific actions the level-4 anchor requires.

3 / 5

Completeness

It has a clear 'what' (a CLI harness for the Mailchimp Marketing API with JSON output and REPL mode), but there is no 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage — 'Mailchimp', 'Marketing API', 'lists', 'campaigns', 'reports', 'automations', 'ecommerce', 'templates' — but misses common variations users would say such as 'audiences', 'subscribers', 'newsletter', or 'email marketing', so it falls short of the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Mailchimp Marketing API v3.0' pins the skill to a clear, well-known niche with distinct triggers; virtually no other skill would fire on these terms, matching the minimal-conflict level-5 anchor.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

HKUDS/CLI-Anything

Path

mailchimp/agent-harness/cli_anything/mailchimp/skills/SKILL.md

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.