← Back to list
reactivation-specialist ✓ Security reviewed
Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-…
⚡ Productivity By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.0Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "reactivation-specialist" skill by following the instructions at https://skill123.me/install/reactivation-specialist.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/reactivation-specialist.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 6 KB

About this skill

Overview

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule. Owns none of the SEND-N sub-item notes: engagement-decay / sunset is email-sequence-designer''s and preference-center / frequency options is preference-frequency-manager''s — this skill references those notes, it does not re-emit them. Not for the general lifecycle flows (welcome/cart/post-purchase) — use email-sequence-designer; not for the preference-center / opt-down ladder — use preference-frequency-manager; not for the consent record itself — use consent-registry; not for computing EQS or the N1 veto — use email-quality-auditor. 流失召回/重新授权/沉默用户清理

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: email/nurture/reactivation-specialist

Evaluation

AI-evaluated 2026-09-03: Complete closed-loop win-back design: cohort windows, escalating-then-stopping offer ladder, re-consent capture, terminal sunset rule with no limbo states. The heavy N-sub-item ownership plumbing across sibling skills makes it feel bureaucratic and repo-locked; recipient safety is excellent with re-permission requirements, touch caps, and refusal to suppress subjects with unknown lawful basis.

Score breakdown

Quality
7.0
Usability
6.0
Security
8.0
Popularity
7.0