mailchimp

# Mailchimp Use this skill for Mailchimp Marketing and Mailchimp Transactional work: audience/list inspection, subscriber lookup and controlled mutations, tags, merge fields, campaign draft operations, campaign content, scheduling/sending, campaign reports, automation and journey readouts, and Mandrill transactional message lookup or sends. ## Default Workflow 1. Start with `credential-check` when setup is uncertain. The helper emits gateway-resolved `<env:...>` and `<secret:...>` placeholders; it does not read runtime env or secret values itself. Missing `MAILCHIMP_SERVER_PREFIX`, `MAILCHIMP_MARKETING_BASIC_AUTH`, `MAILCHIMP_MARKETING_OAUTH_TOKEN`, or `MANDRILL_API_KEY` is surfaced by the gateway placeholder resolver or by a 401/403 upstream response. Do not run `hybridclaw secret list`, `hybridclaw env list`, `grep`, or local file inspection from the agent sandbox to decide whether Mailchimp values are configured; those checks can see the wrong runtime surface. For stored OAuth access tokens, use `oauth metadata --auth oauth` to retrieve the account-specific API endpoint and set `MAILCHIMP_SERVER_PREFIX` from the returned API endpoint host. 2. Use `mailchimp.cjs` noun/verb commands for live work. Normal commands send the helper-built request through the HybridClaw gateway `/api/http/request` path, so the gateway resolves `<env:...>` and `<secret:...>` placeholders server-side. Use `--request` only for dry-run/debug output; do not...