Drip Campaign from Assets

---
name: partner-drip-campaign-from-assets
description: Use when a partner wants to turn a vendor's campaign kit into a scheduled drip campaign in their own email tool (Mailchimp, HubSpot, etc.), with co-branding and partner-attribution links applied automatically. Trigger phrases include "build a drip campaign", "schedule this in Mailchimp", "turn this kit into emails", "set up a nurture sequence", "launch this campaign in HubSpot", "automate this campaign".
---

# Drip Campaign from Assets (Partner)

**Audience**: Partner user, uses **claude.ai Introw Connect Staging** MCP (+ the partner's own email-tool MCP: Mailchimp, HubSpot, etc.).
**Use case**: Through-Channel Marketing (TCMA), partner-side.

## When to use this skill

Use when a partner wants to launch a vendor campaign in the marketing tool they already run — turning a vendor campaign kit into a scheduled, co-branded, attributed drip sequence — without rebuilding anything in a vendor portal.

**Sample prompts that fire this skill:**
- "build a drip campaign from this kit"
- "schedule this in Mailchimp"
- "turn this kit into emails"
- "set up a nurture sequence for this vendor's campaign"
- "launch this campaign in HubSpot"
- "automate this campaign to my list"

## Why this matters
The partner already has the audience, the domain, and the sending tool — what they lack is the on-message content and the time to assemble it. Pulling a vendor's ready-made kit and assembling it into a scheduled drip in the partner's own tool means the partner launches in minutes, in their own voice, while the vendor still gets full attribution on every click and conversion. This is exactly the friction removal that lifts through-channel adoption past **60%**.

## Prerequisites
- The partner has an email / marketing tool with an MCP or API the assistant can reach (Mailchimp, HubSpot, etc.).
- The partner's audience / list exists in that tool.
- The partner's branding is captured with the vendor (for co-branded assets).

## Process

### Step 1: Pull the vendor campaign kit
- `Introw_Connect_Staging:partners`: identify the vendor portal.
- Fetch the campaign kit for that `roomId`: email templates, narrative, positioning, co-branded collateral, and the campaign's attribution links / form.

### Step 2: Co-brand and insert attribution
- Ensure the co-branded collateral carries the partner's branding (hand off to `partner-cobrand-my-collateral` if needed).
- Insert the **partner-attributed affiliate links and form** into every email so all resulting clicks and conversions attribute back to the partner. Never strip or replace the attribution links — that breaks the vendor's tracking and the partner's credit.

### Step 3: Build the sequence
- Map the kit's email templates into a drip sequence: order, send delays, and audience segment.
- Adapt tone to the partner's voice while preserving the vendor's approved claims and positioning.

### Step 4: Schedule in the partner's own tool
- Create the campaign / sequence in the partner's email tool via its MCP (Mailchimp, HubSpot, etc.): create the emails, set the schedule, and assign the target list/segment.
- Leave the campaign in **draft / scheduled-pending-review** state — do not auto-send.

### Step 5: Confirm and log
- Summarize the scheduled sequence for the partner to review and activate.
- `Introw_Connect_Staging:add_task` on the vendor portal to log that the campaign was launched, so the activity is visible to the vendor.

## Output format
- **Sequence plan**: each email, send delay, and target segment.
- **Attribution check**: confirmation that partner-attributed links / form are in every email.
- **Tool setup**: what was created in the partner's email tool and its current state (draft / scheduled).
- **Review checklist**: what the partner should confirm before activating.

## Guardrails & PRM best practice
- **Never send automatically.** The skill ends at a scheduled/draft campaign the partner reviews and activates.
- **Preserve attribution.** Attribution links and forms must be present in every email — this is how the partner gets credited and paid.
- **Respect the vendor's claims.** Adapt voice, not substance; don't alter approved product claims, pricing, or compliance language.
- **Strictly scoped per portal.** Kit data is fetched only with the owning vendor's `roomId`. No cross-portal leakage.
- **Consent and compliance.** Only send to lists the partner is permitted to email; honor opt-out and regional consent (GDPR/CAN-SPAM) rules.
- **Use current assets.** Pull the latest kit version; don't reuse stale local copies.
- **Cross-skill handoff.** Co-brand collateral via `partner-cobrand-my-collateral`; plan which campaigns to run and when via `partner-cross-vendor-content-calendar`.