跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

reactivation-specialist

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. 流失召回/重新授权/沉默用户清理

aaron-he-zhu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aaron-he-zhu/aaron-marketing-skills --skill reactivation-specialist

技能说明


name: reactivation-specialist slug: aaron-reactivation-specialist displayName: "Reactivation Specialist · 流失召回" summary: "流失召回/重新授权/沉默用户清理" description: '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. 流失召回/重新授权/沉默用户清理' version: "20.1.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use when a defined cohort has stopped opening/clicking and the user wants a self-contained win-back and re-permission program before those subjects are suppressed: define the lapsed cohort by a no-engagement window, design a staged offer ladder (soft re-engagement → incentive → last-chance), add a re-consent / re-permission capture step so re-engaged subjects re-affirm opt-in, and set the sunset-confirm rule that either re-permissions or suppresses each subject. Activate when the problem is a decaying tail of the list and the goal is to recover or cleanly retire it — not to design the everyday lifecycle flows." argument-hint: " [platform/ESP] [offer/incentive available] [suppression policy]" metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "email", "phase": "nurture", "geo-relevance": "low", "hermes": {"tags": ["marketing", "email", "nurture"], "category": "email"}, "openclaw": {"emoji": "✉️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Reactivation Specialist

Designs a closed-loop reactivation program for lapsed email cohorts — the win-back offer ladder, the re-consent (re-permission) capture step, and the sunset-confirm / suppression rule. It defines the lapsed cohort by a no-engagement window, stages an offer ladder that escalates then stops, requires re-engaged subjects to re-affirm opt-in, and specifies the terminal rule that either re-permissions a subject or suppresses them. It does not author the SEND N (Nurture / Lifecycle) sub-item notes: engagement-decay / sunset is owned by email-sequence-designer and preference-center / frequency options by preference-frequency-manager — this program feeds both owners its sunset-confirm and re-consent facts to fold in, and references their notes rather than re-emitting them. It does not design the everyday lifecycle flows, own the consent record, or compute the final EQS.

Quick Start

Build a win-back campaign for subscribers who haven't opened in [N] days on [ESP]. Here is my engagement export: [paste/path]. I can offer [incentive].
My unengaged tail is [X]% of the list and complaints are creeping up. Design a re-permission sweep with an offer ladder and a sunset-confirm rule.
I need to clean the dead weight off my list without a bulk delete. Design a reactivation program that re-consents the recoverable subjects and suppresses the rest.

Skill Contract

Expected output: a lapsed-cohort definition (the no-engagement window + how the cohort is pulled), a staged offer ladder (each step's trigger, timing, message intent, and escalation/stop rule), a re-consent / re-permission capture step (what re-affirms opt-in and how it is recorded), a sunset-confirm / suppression rule (the terminal branch that either re-permissions or suppresses each subject), a handoff of the sunset-confirm and re-consent facts to the SEND N sub-item owners (engagement-decay / sunset → email-sequence-designer; preference-center / frequency options → preference-frequency-manager) rather than an own sub-item score, and the standard handoff summary.

  • Reads: the lapsed-cohort criteria (no-open / no-click window), the available incentive or offer, the ESP engagement/flow export (own data) for last-open / last-click recency and complaint signals when available, the current suppression policy, and one SEND profile (promotional|retention|cold-outbound|newsletter).
  • Writes: a user-facing reactivation program (cohort + ladder + re-consent + sunset) and a reusable handoff summary to memory/email/reactivation-specialist/YYYY-MM-DD-<cohort-or-goal>.md.
  • Promotes: the cohort window, offer-ladder steps, re-consent rule, sunset thresholds, and any missing exports to memory/hot-cache.md and memory/open-loops.md; propose durable cohort/sunset thresholds as pending-decision items — never write decisions.md directly.
  • Done when: the lapsed cohort has an explicit no-engagement window; the offer ladder has staged steps with timing and an escalation/stop rule; a re-consent / re-permission capture step exists; a sunset-confirm rule terminally re-permissions or suppresses every subject; and the sunset-confirm + re-consent facts are handed to the SEND N sub-item owners (engagement-decay/sunset → email-sequence-designer; preference-center/frequency → preference-frequency-manager) to fold into their notes. Do not author those N sub-item notes here, and do not compute EQS.
  • Primary next skill: [consent-registry](../../../protocol/consent-regist
阅读完整来源 ↗