BC mailchimp-marketing
Manage Mailchimp audiences, campaigns, automations, e-commerce, and analytics. Create and send email campaigns, manage subscribers, configure automations, handle e-commerce stores, and track performance with detailed reports.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5946 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 57 mutating operations with no state check
- 70Execution cost. Instruction body is 5946 tokens
- 100Tools and files. No external tools needed
- 100Steps. 45 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 225: enough signal without eating the budget
- +4Structure: 46 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: clean
This Mailchimp skill is a disclosed ClawLink-based integration that can manage a connected Mailchimp account, including high-impact actions, but it requires user confirmation for writes and shows no scanner or artifact-backed malicious behavior.
LLM: benign (high) · VirusTotal: · 9 Jun 2026