Codex

email-campaign

Project directory path (default current directory)

104 stars

Best use case

email-campaign is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

It is a strong fit for teams already working in Codex.

Project directory path (default current directory)

Teams using email-campaign should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/email-campaign/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/email-campaign/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/email-campaign/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How email-campaign Compares

Feature / Agentemail-campaignStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Project directory path (default current directory)

Which AI agents support this skill?

This skill is designed for Codex.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Email Campaign Command

Create comprehensive email marketing campaign with strategy, content, and automation planning.

## What This Command Does

1. **Develops Email Strategy**
   - Campaign objectives
   - Audience segmentation
   - Email sequence planning

2. **Creates Email Content**
   - Subject lines and preview text
   - Email body copy
   - CTA strategy

3. **Plans Technical Setup**
   - Automation workflow
   - Personalization strategy
   - Testing plan

## Orchestration Flow

```
Email Campaign Request
        ↓
[Email Marketer] → Campaign Strategy & Sequence
        ↓
[Copywriter] → Email Copy & Subject Lines
        ↓
[Graphic Designer] → Email Design Direction
        ↓
[Legal Reviewer] → CAN-SPAM Compliance
        ↓
[Quality Controller] → Email QC Checklist
        ↓
[Accessibility Checker] → Email Accessibility
        ↓
Email Campaign Package Complete
```

## Agents Involved

| Agent | Role | Output |
|-------|------|--------|
| Email Marketer | Strategy lead | Sequence, automation |
| Copywriter | Content | Copy, subject lines |
| Graphic Designer | Design | Visual direction |
| Legal Reviewer | Compliance | Legal review |
| Quality Controller | QC | Pre-send checklist |
| Accessibility Checker | Accessibility | Email accessibility |

## Campaign Types

| Type | Description | Typical Sequence |
|------|-------------|------------------|
| Nurture | Lead nurturing series | 5-7 emails over 2-4 weeks |
| Promotional | Sales/offer campaign | 2-3 emails over 1 week |
| Announcement | News/launch | 1-2 emails |
| Automated | Trigger-based | Varies by trigger |

## Output Artifacts

Saved to `.aiwg/marketing/email/{campaign-name}/`:

- `email-strategy.md` - Campaign strategy
- `email-sequence.md` - Email sequence plan
- `emails/` - Individual email content
  - `email-1.md`
  - `email-2.md`
  - etc.
- `subject-lines.md` - Subject line options
- `automation-flow.md` - Automation workflow
- `testing-plan.md` - A/B testing strategy
- `compliance-checklist.md` - Legal compliance

## Parameter Handling

### --guidance Parameter

**Purpose**: Provide upfront direction to tailor priorities and approach

**Examples**:
```bash
--guidance "Nurture sequence for enterprise leads"
--guidance "High personalization, segment by industry"
--guidance "Mobile-first design, 60% mobile open rate"
```

**How Applied**:
- Parse guidance for keywords: priority, timeline, audience, focus, constraints
- Adjust agent emphasis and output depth based on stated priorities
- Modify deliverable order based on timeline constraints
- Influence scope and detail level based on context

### --interactive Parameter

**Purpose**: Guide through discovery questions for comprehensive input

**Questions Asked** (if --interactive):
1. What is the primary goal of this email campaign?
2. Who is the target audience/segment?
3. How many emails in the sequence?
4. What is the timeline for sending?
5. What offers or CTAs will be included?
6. What automation triggers apply?

## Usage Examples

```bash
# Nurture sequence
/email-campaign "New Subscriber Welcome" --campaign-type nurture

# Promotional campaign
/email-campaign "Black Friday Sale" --campaign-type promotional

# Product announcement
/email-campaign "Feature Launch" --campaign-type announcement

# With strategic guidance
/email-campaign "Example" --guidance "Your specific context here"

# Interactive mode
/email-campaign "Example" --interactive
```

## Success Criteria

- [ ] Campaign strategy defined
- [ ] Email sequence planned
- [ ] All email copy drafted
- [ ] Subject lines created with A/B variants
- [ ] Automation workflow documented
- [ ] Legal compliance verified
- [ ] QC checklist completed
- [ ] Accessibility reviewed

## References

- @$AIWG_ROOT/agentic/code/frameworks/media-marketing-kit/README.md — Media marketing kit framework overview
- @$AIWG_ROOT/agentic/code/addons/voice-framework/README.md — Voice framework for email tone and messaging
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/subagent-scoping.md — Multi-agent email campaign orchestration
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference

Related Skills

intake-start-campaign

104
from jmagly/aiwg

Validate manually-created campaign intake forms and kick off Strategy phase with agent assignments

Codex

intake-from-campaign

104
from jmagly/aiwg

Scan existing campaign materials, media kit, or marketing assets and generate intake documents by analyzing content, brand elements, and performance data

Codex

campaign-kickoff

104
from jmagly/aiwg

Project directory path (default current directory)

Codex

campaign-analytics

104
from jmagly/aiwg

Project directory path (default current directory)

Codex

aiwg-orchestrate

104
from jmagly/aiwg

Route structured artifact work to AIWG workflows via MCP with zero parent context cost

venv-manager

104
from jmagly/aiwg

Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.

pytest-runner

104
from jmagly/aiwg

Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.

vitest-runner

104
from jmagly/aiwg

Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.

eslint-checker

104
from jmagly/aiwg

Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.

repo-analyzer

104
from jmagly/aiwg

Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.

pr-reviewer

104
from jmagly/aiwg

Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.

YouTube Acquisition

104
from jmagly/aiwg

yt-dlp patterns for acquiring content from YouTube and video platforms