# Build a compliant email reactivation program

Lapsed subscriber lists can reduce deliverability and create consent risk. This skill designs a staged win-back program with fresh consent signals and clear suppression outcomes.

## Install

```bash
npx skillstore add aaron-he-zhu/reactivation-specialist
```

## Metadata

- Status: approved
- Slug: aaron-he-zhu-reactivation-specialist
- Version: 19.0.0
- Author version: 19.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 9781cb8b9511388f280499740cc52a8181c5eedb744a04aef7dd7275f18884ea
- Author: aaron-he-zhu
- GitHub username: aaron-he-zhu
- License: Apache-2.0
- Repository: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/email/nurture/reactivation-specialist
- Ref: 0715a6e09ea875c8e28cb705ce87cc83045e69c1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 81
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/aaron-he-zhu-reactivation-specialist
- Manifest: https://skillstore.pages.dev/api/skills/aaron-he-zhu-reactivation-specialist/manifest

## Capabilities

- Defines a lapsed cohort using no-open or no-click windows.
- Creates a staged offer ladder with triggers, timing, and stop rules.
- Designs a re-consent action for recovered subscribers.
- Sets terminal re-permission and suppression outcomes for each subscriber.
- Flags missing consent records and uncertain cohort definitions for user input.
- Produces a handoff summary for related consent and email-quality workflows.

## Use Cases

- Recover inactive subscribers: Create a measured win-back sequence for subscribers who have not engaged within a defined period.
- Run a re-permission sweep: Define a fresh opt-in action and a clear path for subscribers who do not respond.
- Clean a declining mailing list: Set a safe sunset rule that protects deliverability without using a bulk deletion approach.

## Prompt Templates

### Define a basic win-back campaign

```
Build a win-back campaign for subscribers who have not opened an email in 90 days. I use [ESP] and can offer [incentive].
```

### Create a re-permission plan

```
Design a re-permission sweep for our inactive subscribers. Use a three-step ladder, include a click-to-confirm action, and propose a suppression rule.
```

### Use engagement data

```
Using this engagement export, define a lapsed cohort and reactivation plan. Label conclusions as Measured, User-provided, or Estimated. Our policy is [policy].
```

### Prepare a governed handoff

```
Create a reactivation program for the retention profile. Include re-consent, frequency guardrails, terminal states, open questions, and a handoff summary for consent tracking.
```

## Limitations

- It designs a program but does not send emails or modify an ESP.
- It does not hold consent records or calculate final email-quality scores.
- It relies on user-provided engagement data and suppression policies.
- It does not replace legal review of consent requirements in your jurisdiction.

## Best Practices

- Use a defined engagement window and exclude already suppressed contacts.
- Require an explicit re-consent action before returning a subscriber to active nurture.
- Limit reactivation touches and document the final suppression decision.

## Anti Patterns

- Do not repeatedly message subscribers after the last-chance step.
- Do not treat an email open alone as a fresh consent signal.
- Do not design a suppression rule when lawful basis is unknown.

## Security Audit

- Audited at: 2026-07-27T11:41:51.529\+00:00
- Summary: Most static findings are false positives from Markdown backticks and relative documentation links. One confirmed issue remains: the save instruction uses a user-derived cohort-or-goal placeholder without requiring filename sanitization or path containment. The skill otherwise instructs the agent to treat imported data as untrusted and requires user confirmation before saving.

## Stats

- Views: 1
- Downloads: 6
- Favorites: 0
- Popularity score: 0