Awesome-omni-skills mailchimp-automation

Mailchimp Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/mailchimp-automation" ~/.claude/skills/diegosouzapw-awesome-omni-skills-mailchimp-automation && rm -rf "$T"

manifest: skills/mailchimp-automation/SKILL.md

Mailchimp Automation via Rube MCP

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/mailchimp-automation

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Mailchimp Automation via Rube MCP Automate Mailchimp email marketing workflows including campaign creation and sending, audience/list management, subscriber operations, segmentation, and performance analytics through Composio's Mailchimp toolkit.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
Call RUBEMANAGECONNECTIONS with toolkit mailchimp
If connection is not ACTIVE, follow the returned auth link to complete Mailchimp OAuth
Confirm connection status shows ACTIVE before running any workflows
MAILCHIMPGETLISTSINFO - List available audiences and get listid [Prerequisite]
MAILCHIMPADDCAMPAIGN - Create a new campaign with type, audience, subject, from name [Required]
MAILCHIMPSETCAMPAIGN_CONTENT - Set HTML content for the campaign [Required]

Imported Workflow Notes

Imported: Setup

Get Rube MCP: Add

https://rube.app/mcp

as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming
```
RUBE_SEARCH_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
mailchimp
```
If connection is not ACTIVE, follow the returned auth link to complete Mailchimp OAuth
Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Create and Send Email Campaigns

When to use: User wants to create, configure, test, and send an email campaign.

Tool sequence:

```
MAILCHIMP_GET_LISTS_INFO
```
- List available audiences and get list_id [Prerequisite]
```
MAILCHIMP_ADD_CAMPAIGN
```
- Create a new campaign with type, audience, subject, from name [Required]
```
MAILCHIMP_SET_CAMPAIGN_CONTENT
```
- Set HTML content for the campaign [Required]
```
MAILCHIMP_SEND_TEST_EMAIL
```
- Send preview to reviewers before live send [Optional]
```
MAILCHIMP_SEND_CAMPAIGN
```
- Send the campaign immediately [Required]
```
MAILCHIMP_SCHEDULE_CAMPAIGN
```
- Schedule for future delivery instead of immediate send [Optional]

Key parameters for MAILCHIMP_ADD_CAMPAIGN:

```
type
```
: "regular", "plaintext", "rss", or "variate" (required)
```
recipients__list__id
```
: Audience/list ID for recipients
```
settings__subject__line
```
: Email subject line
```
settings__from__name
```
: Sender display name
```
settings__reply__to
```
: Reply-to email address (required for sending)
```
settings__title
```
: Internal campaign title
```
settings__preview__text
```
: Preview text shown in inbox

Key parameters for MAILCHIMP_SET_CAMPAIGN_CONTENT:

```
campaign_id
```
: Campaign ID from creation step (required)
```
html
```
: Raw HTML content for the email
```
plain_text
```
: Plain-text version (auto-generated if omitted)
```
template__id
```
: Use a pre-built template instead of raw HTML

Pitfalls:

```
MAILCHIMP_SEND_CAMPAIGN
```
is irreversible; always send a test email first and get explicit user approval
Campaign must be in "save" (draft) status with valid audience, subject, from name, verified email, and content before sending
```
MAILCHIMP_SCHEDULE_CAMPAIGN
```
requires a valid future datetime; past timestamps fail
Templates and HTML content must include compliant footer/unsubscribe merge tags
Mailchimp uses double-underscore notation for nested params (e.g.,
```
settings__subject__line
```
)

2. Manage Audiences and Subscribers

When to use: User wants to view audiences, list subscribers, or check subscriber details.

Tool sequence:

```
MAILCHIMP_GET_LISTS_INFO
```
- List all audiences with member counts [Required]
```
MAILCHIMP_GET_LIST_INFO
```
- Get details for a specific audience [Optional]
```
MAILCHIMP_LIST_MEMBERS_INFO
```
- List members with status filter and pagination [Required]
```
MAILCHIMP_SEARCH_MEMBERS
```
- Search by email or name across lists [Optional]
```
MAILCHIMP_GET_MEMBER_INFO
```
- Get detailed profile for a specific subscriber [Optional]
```
MAILCHIMP_LIST_SEGMENTS
```
- List segments within an audience [Optional]

Key parameters for MAILCHIMP_LIST_MEMBERS_INFO:

```
list_id
```
: Audience ID (required)
```
status
```
: "subscribed", "unsubscribed", "cleaned", "pending", "transactional", "archived"
```
count
```
: Records per page (default 10, max 1000)
```
offset
```
: Pagination offset (default 0)
```
sort_field
```
: "timestamp_opt", "timestamp_signup", or "last_changed"
```
fields
```
: Comma-separated list to limit response size

Pitfalls:

```
stats.avg_open_rate
```
and
```
stats.avg_click_rate
```
are 0-1 fractions, NOT 0-100 percentages
Always use
```
status="subscribed"
```
to filter active subscribers; omitting returns all statuses
Must paginate using
```
count
```
and
```
offset
```
until collected members match
```
total_items
```
Large list responses may be truncated; data is under
```
response.data.members
```

3. Add and Update Subscribers

When to use: User wants to add new subscribers, update existing ones, or bulk-manage list membership.

Tool sequence:

```
MAILCHIMP_GET_LIST_INFO
```
- Validate target audience exists [Prerequisite]
```
MAILCHIMP_SEARCH_MEMBERS
```
- Check if contact already exists [Optional]
```
MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER
```
- Upsert subscriber (create or update) [Required]
```
MAILCHIMP_ADD_MEMBER_TO_LIST
```
- Add new subscriber (create only) [Optional]
```
MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS
```
- Bulk manage segment membership [Optional]

Key parameters for MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER:

```
list_id
```
: Audience ID (required)
```
subscriber_hash
```
: MD5 hash of lowercase email (required)
```
email_address
```
: Subscriber email (required)
```
status_if_new
```
: Status for new subscribers: "subscribed", "pending", etc. (required)
```
status
```
: Status for existing subscribers

merge_fields

: Object with merge tag keys (e.g.,

{"FNAME": "John", "LNAME": "Doe"}

)

```
tags
```
: Array of tag strings

Key parameters for MAILCHIMP_ADD_MEMBER_TO_LIST:

```
list_id
```
: Audience ID (required)
```
email_address
```
: Subscriber email (required)
```
status
```
: "subscribed", "pending", "unsubscribed", "cleaned", "transactional" (required)

Pitfalls:

```
subscriber_hash
```
must be MD5 of the lowercase email; incorrect casing causes 404s or duplicates

Use

MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER

(upsert) instead of

MAILCHIMP_ADD_MEMBER_TO_LIST

to avoid duplicate errors

```
status_if_new
```
determines status only for new contacts; existing contacts use
```
status
```
Use
```
skip_merge_validation: true
```
to bypass required merge field validation
```
MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS
```
manages static segment membership, not list membership

4. View Campaign Reports and Analytics

When to use: User wants to review campaign performance, open rates, click rates, or subscriber engagement.

Tool sequence:

```
MAILCHIMP_LIST_CAMPAIGNS
```
- List sent campaigns with report summaries [Required]
```
MAILCHIMP_SEARCH_CAMPAIGNS
```
- Find campaigns by name, subject, or content [Optional]
```
MAILCHIMP_GET_CAMPAIGN_REPORT
```
- Get detailed performance report for a campaign [Required]
```
MAILCHIMP_LIST_CAMPAIGN_REPORTS
```
- Bulk fetch reports across multiple campaigns [Optional]
```
MAILCHIMP_LIST_CAMPAIGN_DETAILS
```
- Get link-level click statistics [Optional]
```
MAILCHIMP_GET_CAMPAIGN_LINK_DETAILS
```
- Drill into specific link click data [Optional]
```
MAILCHIMP_LIST_CLICKED_LINK_SUBSCRIBERS
```
- See who clicked a specific link [Optional]
```
MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY
```
- Get per-subscriber campaign activity [Optional]
```
MAILCHIMP_GET_CAMPAIGN_CONTENT
```
- Retrieve campaign HTML content [Optional]

Key parameters for MAILCHIMP_LIST_CAMPAIGNS:

```
status
```
: "save", "paused", "schedule", "sending", "sent"
```
count
```
/
```
offset
```
: Pagination (default 10, max 1000)
```
since_send_time
```
/
```
before_send_time
```
: ISO 8601 date range filter
```
sort_field
```
: "create_time" or "send_time"
```
fields
```
: Limit response fields for performance

Key parameters for MAILCHIMP_GET_CAMPAIGN_REPORT:

```
campaign_id
```
: Campaign ID (required)
Returns: opens, clicks, bounces, unsubscribes, timeseries, industry_stats

Pitfalls:

MAILCHIMP_LIST_CAMPAIGNS

only returns high-level

report_summary

; use

MAILCHIMP_GET_CAMPAIGN_REPORT

for detailed metrics

Draft/unsent campaigns lack meaningful report data
When using
```
fields
```
parameter on LIST_CAMPAIGNS, explicitly request
```
send_time
```
and
```
report_summary
```
subfields
Pagination defaults are low (10 records); iterate with
```
count
```
and
```
offset
```
until
```
total_items
```
is covered
```
send_time
```
is ISO 8601 with timezone; parse carefully

Imported: Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Mailchimp connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
mailchimp
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @mailchimp-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @mailchimp-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @mailchimp-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @mailchimp-automation using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/mailchimp-automation

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@linear-claude-skill
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-automation
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-cli
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@linkedin-profile-optimizer
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Quick Reference

Task	Tool Slug	Key Params
List audiences	`MAILCHIMP_GET_LISTS_INFO`	`count` , `offset`
Get audience details	`MAILCHIMP_GET_LIST_INFO`	`list_id`
Create campaign	`MAILCHIMP_ADD_CAMPAIGN`	`type` , `recipients__list__id` , `settings__subject__line`
Set campaign content	`MAILCHIMP_SET_CAMPAIGN_CONTENT`	`campaign_id` , `html`
Send test email	`MAILCHIMP_SEND_TEST_EMAIL`	`campaign_id` , `test_emails`
Send campaign	`MAILCHIMP_SEND_CAMPAIGN`	`campaign_id`
Schedule campaign	`MAILCHIMP_SCHEDULE_CAMPAIGN`	`campaign_id` , `schedule_time`
Get campaign info	`MAILCHIMP_GET_CAMPAIGN_INFO`	`campaign_id`
Search campaigns	`MAILCHIMP_SEARCH_CAMPAIGNS`	`query`
List campaigns	`MAILCHIMP_LIST_CAMPAIGNS`	`status` , `count` , `offset`
Replicate campaign	`MAILCHIMP_REPLICATE_CAMPAIGN`	`campaign_id`
List subscribers	`MAILCHIMP_LIST_MEMBERS_INFO`	`list_id` , `status` , `count` , `offset`
Search members	`MAILCHIMP_SEARCH_MEMBERS`	`query` , `list_id`
Get member info	`MAILCHIMP_GET_MEMBER_INFO`	`list_id` , `subscriber_hash`
Add subscriber	`MAILCHIMP_ADD_MEMBER_TO_LIST`	`list_id` , `email_address` , `status`
Upsert subscriber	`MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER`	`list_id` , `subscriber_hash` , `email_address` , `status_if_new`
Batch members	`MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS`	`list_id` , `segment_id`
List segments	`MAILCHIMP_LIST_SEGMENTS`	`list_id`
Campaign report	`MAILCHIMP_GET_CAMPAIGN_REPORT`	`campaign_id`
All reports	`MAILCHIMP_LIST_CAMPAIGN_REPORTS`	`count` , `offset`
Link click details	`MAILCHIMP_LIST_CAMPAIGN_DETAILS`	`campaign_id` , `count`
Subscriber activity	`MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY`	`campaign_id` , `subscriber_hash`
Member recent activity	`MAILCHIMP_VIEW_RECENT_ACTIVITY`	`list_id` , `subscriber_hash`
Campaign content	`MAILCHIMP_GET_CAMPAIGN_CONTENT`	`campaign_id`

Imported: Common Patterns

ID Resolution

Always resolve names to IDs before operations:

Audience name -> list_id:
```
MAILCHIMP_GET_LISTS_INFO
```
and match by name
Subscriber email -> subscriber_hash: Compute MD5 of lowercase email in code
Campaign name -> campaign_id:
```
MAILCHIMP_SEARCH_CAMPAIGNS
```
with query
Segment name -> segment_id:
```
MAILCHIMP_LIST_SEGMENTS
```
with list_id

Pagination

Mailchimp uses offset-based pagination:

Use
```
count
```
(page size, max 1000) and
```
offset
```
(skip N records)
Continue until collected records match
```
total_items
```
from the response
Default
```
count
```
is 10; always set explicitly for bulk operations
Search endpoints max at 10 pages (300 results for 30/page)

Subscriber Hash

Many endpoints require

subscriber_hash

(MD5 of lowercase email):

import hashlib
subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest()

Imported: Known Pitfalls

ID Formats

```
list_id
```
(audience ID) is a short alphanumeric string (e.g., "abc123def4")
```
campaign_id
```
is an alphanumeric string
```
subscriber_hash
```
is an MD5 hex string (32 characters)
Segment IDs are integers

Rate Limits

Mailchimp enforces API rate limits; use batching for bulk subscriber operations
High-volume use of GET_MEMBER_INFO and ADD_OR_UPDATE_LIST_MEMBER can trigger throttling
Use
```
MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS
```
for bulk segment operations

Parameter Quirks

Nested parameters use double-underscore notation:
```
settings__subject__line
```
,
```
recipients__list__id
```
```
avg_open_rate
```
and
```
avg_click_rate
```
are 0-1 fractions, not percentages
```
status_if_new
```
only applies to new contacts in upsert operations
```
subscriber_hash
```
must be MD5 of lowercase email; wrong casing creates phantom records
Campaign
```
type
```
is required for creation; most common is "regular"
```
MAILCHIMP_SEND_CAMPAIGN
```
returns HTTP 204 on success (no body)

Content and Compliance

Campaign HTML must include unsubscribe link and physical address (merge tags)
Content must be set via
```
MAILCHIMP_SET_CAMPAIGN_CONTENT
```
before sending
Test emails require campaign to have content already set

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.