mailchimp

Files (2)

• SKILL.md
• mailchimp.cjs

SKILL.md (first lines)

# 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 normally
   reconstruct or relay `httpRequest` objects with the built-in `http_request`
   tool.
3. Treat `MAILCHIMP_MARKETING_BASIC_AUTH`, `MAILCHIMP_MARKETING_OAUTH_TOKEN`,
   and `MANDRILL_API_KEY` as SecretRefs only. Never ask the operator to paste
   tokens into chat, never print raw `Authorization` headers, and never include
   Mandrill keys in `--body-json`.
4. For audience writes, bulk subscriber plans, campaign draft/content writes,
   campaign schedule/send, and Mandrill sends, first run `approval-plan`, show
   the preview, and stop. After explicit operator approval for the named
   audience, campaign, or message target, run the approved helper command
   unchanged.
5. For 401 or 403, stop after the first failure and ask the operator to verify
   the token, user role, Transactional provisioning, and data-center prefix. Do
   not retry with broader permissions.
6. For 429, report rate-limit guidance from `Retry-After` or Mailchimp
   rate-limit headers when present. Do not start retry loops.
7. Minimize subscriber PII in summaries. Prefer subscriber hashes for lookup and
   archive/tag operations. Include email addresses only when required to create
   or update a member.

## Command Contract

Use the standard helper shape:

```text
node skills/mailchimp/mailchimp.cjs [--format json|pretty] [--request] <resource> <action> [flags]
node skills/mailchimp/mailchimp.cjs [--format json|pretty] approval-plan <resource> <action> [flags]
```

```bash
node skills/mailchimp/mailchimp.cjs --help
node skills/mailchimp/mailchimp.cjs --format json credential-check
node skills/mailchimp/mailchimp.cjs --format json oauth metadata --auth oauth
node skills/mailchimp/mailchimp.cjs --format json --request oauth metadata --auth oauth
```

Run Marketing reads:

```bash
node skills/mailchimp/mailchimp.cjs --format json marketing root
node skills/mailchimp/mailchimp.cjs --format json audience list --count 25
node skills/mailchimp/mailchimp.cjs --format json audience members --list-id <list-id> --status subscribed
node skills/mailchimp/mailchimp.cjs --format json audience member --list-id <list-id> --email user@example.com
node skills/mailchimp/mailchimp.cjs --format json audience merge-fields --list-id <list-id>
```

Run guarded audience mutations only after approval:

```bash
node skills/mailchimp/mailchimp.cjs --format json approval-plan audience member-upsert \
  --list-id <list-id> --email user@example.com --status-if-new pending \
  --merge-fields-json '{"FNAME":"Ada"}' --tag customer:active

node skills/mailchimp/mailchimp.cjs --format json approval-plan audience tags-update \
  --list-id <list-id> --email user@example.com --tag vip:active --tag stale:inactive

node skills/mailchimp/mailchimp.cjs --format json approval-plan audience member-archive \
  --list-id <list-id> --email user@example.com

node skills/mailchimp/mailchimp.cjs --format json approval-plan audience bulk-plan \
  --list-id <list-id> --operation member-upsert --count 2500 \
  --source-label imports/2026-06-newsletter.csv \
  --sample-json '{"email":"user@example.com","status_if_new":"pending","FNAME":"Ada"}'
```

Run campaign requests:

```bash
node skills/mailchimp/mailchimp.cjs --format json campaign list --status save
node skills/mailchimp/mailchimp.cjs --format json approval-plan campaign create --body-json '{"type":"regular","recipients":{"list_id":"<list-id>"},"settings":{"subject_line":"Subject","title":"Draft","from_name":"Team","reply_to":"team@example.com"}}'
node skills/mailchimp/mailchimp.cjs --format json approval-plan campaign content-set --campaign-id <campaign-id> --body-json '{"html":"<p>Hello</p>"}'
node skills/mailchimp/mailchimp.cjs --format json approval-plan campaign schedule --campaign-id <campaign-id> --schedule-time 2026-06-01T09:00:00+00:00
node skills/mailchimp/mailchimp.cjs --format json approval-plan campaign send --campaign-id <campaign-id>
```

Run report and read-only automation/journey requests:

```bash
node skills/mailchimp/mailchimp.cjs --format json campaign report --campaign-id <campaign-id> --kind overview
node skills/mailchimp/mailchimp.cjs --format json campaign report --campaign-id <campaign-id> --kind bounces
node skills/mailchimp/mailchimp.cjs --format json campaign report --campaign-id <campaign-id> --kind opens
node skills/mailchimp/mailchimp.cjs --format json campaign report --campaign-id <campaign-id> --kind clicks
node skills/mailchimp/mailchimp.cjs --format json campaign report --campaign-id <campaign-id> --kind email-activity
node skills/mailchimp/mailchimp.cjs --format json automation list
node skills/mailchimp/mailchimp.cjs --format json journey list
```

Run Mandrill transactional requests:

```bash
node skills/mailchimp/mailchimp.cjs --format json mandrill message-info --id <message-id>
node skills/mailchimp/mailchimp.cjs --format json approval-plan mandrill send --body-json '{"message":{"from_email":"ops@example.com","to":[{"email":"user@example.com","type":"to"}],"subject":"Receipt","text":"Thanks"}}'
node skills/mailchimp/mailchimp.cjs --format json approval-plan mandrill send-template --body-json '{"template_name":"receipt","template_content":[],"message":{"to":[{"email":"user@example.com","type":"to"}],"merge":true}}'

From HybridAIOne/hybridclaw, MIT.

More from HybridAIOne/hybridclaw