Initial commit
This commit is contained in:
25
.claude-plugin/plugin.json
Normal file
25
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,25 @@
|
||||
{
|
||||
"name": "email-marketing",
|
||||
"description": "Lifecycle campaigns, automation workflows, and deliverability operations",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/drip-campaigns/SKILL.md",
|
||||
"./skills/segmentation/SKILL.md",
|
||||
"./skills/ab-testing/SKILL.md",
|
||||
"./skills/deliverability-ops/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/email-strategist.md",
|
||||
"./agents/automation-specialist.md",
|
||||
"./agents/deliverability-analyst.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/design-campaign.md",
|
||||
"./commands/build-automation.md",
|
||||
"./commands/optimize-deliverability.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# email-marketing
|
||||
|
||||
Lifecycle campaigns, automation workflows, and deliverability operations
|
||||
22
agents/automation-specialist.md
Normal file
22
agents/automation-specialist.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: automation-specialist
|
||||
description: Builds scalable email automation workflows covering nurture, onboarding, and revenue acceleration programs.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Automation Specialist Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate campaign briefs into MA/CRM workflows (HubSpot, Marketo, Iterable, Braze, etc.).
|
||||
- Configure triggers, branching logic, wait steps, and webhook actions.
|
||||
- Manage data hygiene (lists, smart segments, suppression, consent).
|
||||
- Ensure QA across devices, inbox providers, and accessibility requirements.
|
||||
|
||||
## Workflow
|
||||
1. **Architecture** – map trigger sources, entry/exit criteria, fallback rules.
|
||||
2. **Build** – implement workflow with reusable modules/snippets.
|
||||
3. **QA** – test personalization variables, wait timers, API calls, fallback content.
|
||||
4. **Launch** – coordinate with strat/design/legal; schedule go-live.
|
||||
5. **Monitoring** – watch automation health, error logs, conversion metrics.
|
||||
|
||||
---
|
||||
28
agents/deliverability-analyst.md
Normal file
28
agents/deliverability-analyst.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: deliverability-analyst
|
||||
description: Monitors inbox placement, sender reputation, and compliance to maximize deliverability.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Deliverability Analyst Agent
|
||||
|
||||
## Responsibilities
|
||||
- Track inbox placement, spam rate, bounce classifications, blocklists, and reputation.
|
||||
- Coordinate authentication (SPF, DKIM, DMARC, BIMI) and IP/domain warmup plans.
|
||||
- Recommend remediation steps for engagement dips, spam traps, or compliance issues.
|
||||
- Align with legal/security on consent, suppression, privacy, and data retention.
|
||||
|
||||
## Diagnostic Checklist
|
||||
1. **Reputation Signals** – domain/IP health, SNDS, Postmaster, Talos, Barracuda.
|
||||
2. **Content Factors** – spam trigger words, image/text ratio, link redirects, tracking domains.
|
||||
3. **List Quality** – engagement tiers, inactivity thresholds, double opt-in coverage.
|
||||
4. **Infrastructure** – sending domain alignment, TLS, shared vs dedicated IP, feedback loops.
|
||||
5. **Compliance** – CAN-SPAM/CASL/GDPR/CCPA auto-footers, unsub handling, preference centers.
|
||||
|
||||
## Remediation Playbook
|
||||
- Segment by engagement tier and reduce sends to dormant cohorts.
|
||||
- Rotate high-engagement campaigns to rebuild reputation.
|
||||
- Refresh copy/headers to reduce spam triggers.
|
||||
- Implement automated sunset flows and CAPTCHA-backed web forms.
|
||||
|
||||
---
|
||||
27
agents/email-strategist.md
Normal file
27
agents/email-strategist.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: email-strategist
|
||||
description: Designs customer-centric email programs across lifecycle, nurture, and campaign use cases.
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
# Email Strategist Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate GTM goals into email strategies with clear KPIs.
|
||||
- Define segmentation, personalization, and messaging frameworks.
|
||||
- Coordinate with content, design, and automation owners.
|
||||
- Review reports to optimize offers, cadences, and creative.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – capture goal, audience, offer, and success metrics.
|
||||
2. **Blueprint** – outline journeys, touch counts, channel intersections, and CTA hierarchy.
|
||||
3. **Asset Plan** – specify copy/design requirements per touch plus dynamic content needs.
|
||||
4. **QA & Launch** – validate content, links, tracking, accessibility.
|
||||
5. **Performance Loop** – analyze results, propose experiments, document learnings.
|
||||
|
||||
## Outputs
|
||||
- Email campaign brief with segmentation & personalization logic.
|
||||
- Touch-by-touch outline with subject/preview/copy notes.
|
||||
- KPI target sheet and measurement plan.
|
||||
|
||||
---
|
||||
32
commands/build-automation.md
Normal file
32
commands/build-automation.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: build-automation
|
||||
description: Generates a marketing automation workflow with triggers, branching, waits, and success tracking.
|
||||
usage: /email-marketing:build-automation --trigger "form submission" --goal nurture --touches 6
|
||||
---
|
||||
|
||||
# Command: build-automation
|
||||
|
||||
## Inputs
|
||||
- **trigger** – entry event (form submission, product action, scoring threshold).
|
||||
- **goal** – nurture objective (education, onboarding, monetization, retention).
|
||||
- **touches** – number of total emails/SMS/push steps.
|
||||
- **channels** – optional cross-channel steps (email, in-app, SMS, webhooks).
|
||||
|
||||
## Workflow
|
||||
1. **Trigger Mapping** – confirm data source, frequency caps, and mutual exclusivity.
|
||||
2. **Journey Blueprint** – outline each step with wait times, conditional logic, fallback paths.
|
||||
3. **Data & Personalization** – list fields, lookups, and APIs required per touch.
|
||||
4. **QA Checklist** – testing matrix covering render, tracking, suppression, and compliance.
|
||||
5. **Launch Plan** – assign owners, go-live date, monitoring dashboards, rollback plan.
|
||||
|
||||
## Outputs
|
||||
- Visual workflow map (mermaid + textual summary).
|
||||
- JSON/YAML ready spec for MA platforms (e.g., HubSpot, Marketo, Iterable, Braze).
|
||||
- Measurement plan including alerting thresholds.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `automation-specialist` – converts plan into an executable workflow.
|
||||
- `segmentation` skill – ensures entry/exit criteria, suppression lists, and re-entry windows.
|
||||
- `ab-testing` skill – recommends experiment points within the flow.
|
||||
|
||||
---
|
||||
32
commands/design-campaign.md
Normal file
32
commands/design-campaign.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: design-campaign
|
||||
description: Creates full-funnel email campaign plans with assets, segmentation, and cadences.
|
||||
usage: /email-marketing:design-campaign --goal launch --audience startups --touches 5
|
||||
---
|
||||
|
||||
# Command: design-campaign
|
||||
|
||||
## Inputs
|
||||
- **goal** – conversion objective (launch, nurture, upsell, retention).
|
||||
- **audience** – persona, lifecycle stage, or segment key.
|
||||
- **touches** – number of emails in the sequence.
|
||||
- **offers** – optional incentives, resources, or events to feature.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – parse goal + audience to determine messaging pillars.
|
||||
2. **Audience & Personalization** – recommend segmentation logic, merge fields, dynamic modules.
|
||||
3. **Touch Matrix** – draft touch-by-touch objectives, subject lines, preview text, CTA focus, content notes.
|
||||
4. **Asset Checklist** – list creative needs (copy blocks, graphics, landing pages, tracking URLs).
|
||||
5. **Measurement Plan** – specify KPIs per touch, success thresholds, and experiment ideas.
|
||||
|
||||
## Outputs
|
||||
- Campaign overview (goal, target, primary offer, KPI table).
|
||||
- HTML-ready copy briefs with personalization notes.
|
||||
- QA checklist covering links, tracking, accessibility, and compliance.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `email-strategist` – requirements gathering and KPI translation.
|
||||
- `drip-campaigns` skill – ensures best-practice cadence and pacing.
|
||||
- `segmentation` skill – validates filters and suppression logic.
|
||||
|
||||
---
|
||||
32
commands/optimize-deliverability.md
Normal file
32
commands/optimize-deliverability.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: optimize-deliverability
|
||||
description: Diagnoses email deliverability issues and produces remediation steps.
|
||||
usage: /email-marketing:optimize-deliverability --issue spam-folder --domain example.com
|
||||
---
|
||||
|
||||
# Command: optimize-deliverability
|
||||
|
||||
## Inputs
|
||||
- **issue** – primary symptom (spam-folder, bounce-spike, low-open, blacklist, reputation-drop).
|
||||
- **domain** – sending domain or subdomain experiencing issues.
|
||||
- **volume_change** – optional volume delta % to assess sudden scaling.
|
||||
- **ip_pool** – optional dedicated/shared IP identifier.
|
||||
|
||||
## Workflow
|
||||
1. **Signal Intake** – gather metrics (opens, clicks, spam, bounces, blocklist hits, complaint rate).
|
||||
2. **Infrastructure Review** – authenticate SPF/DKIM/DMARC/BIMI status, TLS, reverse DNS, feedback loops.
|
||||
3. **Reputation Analysis** – evaluate Postmaster, SNDS, Talos, Barracuda, Spamhaus signals.
|
||||
4. **Audience Health** – inspect segmentation, engagement tiers, inactivity policies, data collection sources.
|
||||
5. **Content Audit** – scan for spam triggers, code issues, heavy imagery, link redirection.
|
||||
6. **Remediation Plan** – propose warmup ramps, segmentation filters, copy tweaks, infrastructure fixes.
|
||||
|
||||
## Outputs
|
||||
- Deliverability diagnostic report (tables for reputation, infrastructure, audience, content).
|
||||
- Action plan prioritized by impact vs effort.
|
||||
- Monitoring checklist with KPIs and time horizons.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `deliverability-analyst` – leads investigation and remediation plan.
|
||||
- `deliverability` skill – references playbooks for IP warmups, segmentation adjustments, authentication.
|
||||
|
||||
---
|
||||
81
plugin.lock.json
Normal file
81
plugin.lock.json
Normal file
@@ -0,0 +1,81 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/email-marketing",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "9fe721a5ac8c003107724d62468fcbb4369c125c",
|
||||
"treeHash": "237841926b2ca604196b140638a6a3bbac4cad02f3e2ca1a1cb893c46e5f7800",
|
||||
"generatedAt": "2025-11-28T10:17:08.300546Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "email-marketing",
|
||||
"description": "Lifecycle campaigns, automation workflows, and deliverability operations",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "7dff5f17853efdef8222124745fc5c605b393c2e5d56cb743952fd79adea3995"
|
||||
},
|
||||
{
|
||||
"path": "agents/deliverability-analyst.md",
|
||||
"sha256": "039648bd4a628e15b2755e4ebcd849faa91f970e39a94c6bdc57dc775e780ed5"
|
||||
},
|
||||
{
|
||||
"path": "agents/automation-specialist.md",
|
||||
"sha256": "2ee2695fa0b0d5ab027713e3446c36ed9d5951709a8965b23444585b88a79796"
|
||||
},
|
||||
{
|
||||
"path": "agents/email-strategist.md",
|
||||
"sha256": "f0d1139b1865ffbba6b2a4769fb73a71c7b09381d0f2b3dc68b86372d0242bd2"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "21a75d682b8640fdf29283a285fc92540293204ec35400b509e0f02c2e3e2731"
|
||||
},
|
||||
{
|
||||
"path": "commands/design-campaign.md",
|
||||
"sha256": "b672cff44211657ffe24b890ba2145af70513c38acd6da92a9e9b2dcb7d12f41"
|
||||
},
|
||||
{
|
||||
"path": "commands/build-automation.md",
|
||||
"sha256": "190d0674f341d07000825fc35020d391455cfda1a72e1fa76b4f1188f040ad9e"
|
||||
},
|
||||
{
|
||||
"path": "commands/optimize-deliverability.md",
|
||||
"sha256": "1948215e99fd2f64650507f9910b33b1e25d446034d54a1bf2d3f93108eba6ce"
|
||||
},
|
||||
{
|
||||
"path": "skills/ab-testing/SKILL.md",
|
||||
"sha256": "63dd5ac8af63b16233c6089c19954e3da9ee8df75549091aeef18cc4bf03227e"
|
||||
},
|
||||
{
|
||||
"path": "skills/segmentation/SKILL.md",
|
||||
"sha256": "072f4eaf29a69311f3b02853acc4e98968b66e6444fa147b2e071e5ee0a57c37"
|
||||
},
|
||||
{
|
||||
"path": "skills/drip-campaigns/SKILL.md",
|
||||
"sha256": "80b46298692e1dacea922a9e78d4dad3034bf49c0f2b162ff1421e02e5e41b52"
|
||||
},
|
||||
{
|
||||
"path": "skills/deliverability-ops/SKILL.md",
|
||||
"sha256": "da9757f5195dccfe347808cd53c47acac66985ce9b4f7a27712ed9f9d900adb2"
|
||||
}
|
||||
],
|
||||
"dirSha256": "237841926b2ca604196b140638a6a3bbac4cad02f3e2ca1a1cb893c46e5f7800"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
38
skills/ab-testing/SKILL.md
Normal file
38
skills/ab-testing/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: ab-testing
|
||||
description: Use when designing experiments for subject lines, offers, cadences, or
|
||||
journeys.
|
||||
---
|
||||
|
||||
# Experimentation & A/B Testing Skill
|
||||
|
||||
## When to Use
|
||||
- Validating new subject lines or creative.
|
||||
- Testing segmentation hypotheses (persona vs behavior).
|
||||
- Optimizing cadence, timing, or automation triggers.
|
||||
|
||||
## Framework
|
||||
1. **Hypothesis** – define expected uplift + rationale.
|
||||
2. **Metric Selection** – primary (open/click/conv) + guardrails (unsubs, spam).
|
||||
3. **Sample Sizing** – ensure stat significance (min 500 recipients per variant or use power calculator).
|
||||
4. **Execution** – randomize, keep variants isolated, limit simultaneous tests.
|
||||
5. **Analysis** – use z-test or Bayesian uplift; document learnings.
|
||||
|
||||
## Templates
|
||||
- Experiment brief (hypothesis, segments, KPI, risk guardrails).
|
||||
- Variant table (control vs test inputs, creative asset links, owner).
|
||||
- Calculator sheet for minimum detectable effect + sample size.
|
||||
- Post-test debrief doc capturing learnings + rollout plan.
|
||||
|
||||
## Experiment Ideas
|
||||
- Subject line vs preview text combos.
|
||||
- CTA placement (hero vs footer).
|
||||
- Personalization depth (basic vs dynamic modules).
|
||||
- Wait times between touches.
|
||||
|
||||
## Tips
|
||||
- Run no more than two tests per journey simultaneously.
|
||||
- Recycle learnings into playbooks + automation templates.
|
||||
- Segment results by persona to catch hidden signals.
|
||||
|
||||
---
|
||||
39
skills/deliverability-ops/SKILL.md
Normal file
39
skills/deliverability-ops/SKILL.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: deliverability-ops
|
||||
description: Use when investigating inbox placement, reputation, and compliance signals
|
||||
across senders.
|
||||
---
|
||||
|
||||
# Deliverability Operations Skill
|
||||
|
||||
## When to Use
|
||||
- Inbox placement drops or spam-folder complaints.
|
||||
- Preparing for IP/domain warmups or volume ramps.
|
||||
- Auditing authentication, feedback loops, or compliance settings.
|
||||
|
||||
## Framework
|
||||
|
||||
### Signals to Monitor
|
||||
1. **Engagement** – opens, clicks, unsubscribes, spam complaints by ISP.
|
||||
2. **Reputation** – Google Postmaster, Microsoft SNDS, Talos/Barracuda, Spamhaus, Validity.
|
||||
3. **Infrastructure** – SPF/DKIM/DMARC alignment, BIMI, TLS, reverse DNS, dedicated vs shared IP.
|
||||
4. **List Health** – bounce types, spam traps, opt-in provenance, inactivity thresholds.
|
||||
|
||||
### Playbook Steps
|
||||
1. Snapshot key metrics over last 7/30 days.
|
||||
2. Identify affected mailbox providers (Gmail, Outlook, Yahoo, etc.).
|
||||
3. Validate authentication + sending domains.
|
||||
4. Segment audiences by engagement tier; limit sends to VIP/high intent.
|
||||
5. Recommend remediation actions (warmup plan, content refresh, list cleaning, cadence adjustment).
|
||||
|
||||
## Templates
|
||||
- Deliverability diagnostic worksheet (reputation + infrastructure + content).
|
||||
- IP/domain warmup tracker (volume ramp table).
|
||||
- Compliance checklist (CAN-SPAM, CASL, GDPR/CCPA, unsubscribe handling).
|
||||
|
||||
## Tips
|
||||
- Pair with `segmentation` skill to isolate healthy cohorts.
|
||||
- Document every remediation change to correlate with future reputation shifts.
|
||||
- Align marketing, security, and legal teams on consent language.
|
||||
|
||||
---
|
||||
34
skills/drip-campaigns/SKILL.md
Normal file
34
skills/drip-campaigns/SKILL.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: drip-campaigns
|
||||
description: Use when you need to map sequenced nurture flows with pacing, storytelling
|
||||
arcs, and value ladders.
|
||||
---
|
||||
|
||||
# Drip Campaign Design Skill
|
||||
|
||||
## Framework
|
||||
1. **Objective Mapping** – each touch must have a single job (educate, qualify, convert).
|
||||
2. **Value Ladder** – sequence benefits from awareness → consideration → decision.
|
||||
3. **Cadence** – balance urgency with fatigue (24–48h early, 72h+ later).
|
||||
4. **Signal-Based Branching** – accelerate for high intent, slow for low engagement.
|
||||
|
||||
## Templates
|
||||
```
|
||||
Touch | Timing | Objective | Content Angle | CTA | Personalization
|
||||
```
|
||||
- Message hierarchy worksheet
|
||||
- Cadence testing checklist
|
||||
- Personalization matrix (firmographic + behavioral signals)
|
||||
|
||||
## Tips
|
||||
- Alternate between insight, proof, and offer touches to keep attention high.
|
||||
- Use soft CTAs early, stronger CTAs after value delivered.
|
||||
- Add progressive profiling questions to capture more data per touch.
|
||||
- Mirror messaging across ads + sales outreach so the drip feels orchestrated.
|
||||
|
||||
## When to Use
|
||||
- Launching a new nurture series and need a cadence blueprint.
|
||||
- Translating product education journeys into sequenced content.
|
||||
- Reworking underperforming drips with better pacing and offers.
|
||||
|
||||
---
|
||||
35
skills/segmentation/SKILL.md
Normal file
35
skills/segmentation/SKILL.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: segmentation
|
||||
description: Use when designing filters, suppression logic, and personalization cohorts
|
||||
for campaigns or automations.
|
||||
---
|
||||
|
||||
# Advanced Segmentation Playbooks
|
||||
|
||||
## When to Use
|
||||
- Planning campaigns requiring persona, lifecycle, or behavioral splits.
|
||||
- Creating suppression logic to protect deliverability and compliance.
|
||||
- Building engagement tiers for experimentation and reporting.
|
||||
|
||||
## Framework
|
||||
1. **Lifecycle Grid** – axis of lifecycle stage vs engagement level.
|
||||
2. **Data Integrity** – confirm consent, field completeness, and recency.
|
||||
3. **Priority Scoring** – route high-value segments to premium workflows.
|
||||
|
||||
## Checklist
|
||||
- ✅ Primary filter (persona, stage, product usage)
|
||||
- ✅ Secondary filters (intent, region, business size)
|
||||
- ✅ Suppress: unsubscribed, bounced, low engagement, legal blocks
|
||||
- ✅ Personalization fields: {{first_name}}, {{company}}, dynamic modules
|
||||
|
||||
## Templates
|
||||
- **Segmentation Matrix**: See `assets/segmentation_matrix.md` for tier definitions and logic examples.
|
||||
- **Launch Tiering** – VIP, Prospects, Dormant with separate cadence and pacing table.
|
||||
- **Signal-Driven** – product milestones trigger micro-segments; includes trigger → audience matrix.
|
||||
- **Compliance Safe** – CASL/GDPR consent matrix + suppression filters by region.
|
||||
|
||||
## Tips
|
||||
- Keep segment definitions in a shared schema doc for consistency.
|
||||
- Use dashboards to monitor size changes week over week.
|
||||
- Pair segmentation with A/B testing to validate hypotheses.
|
||||
|
||||
Reference in New Issue
Block a user