plugins/pm-copy/skills/email-sequence/SKILL.md
Write a multi-email nurture/onboarding/launch sequence with a goal per email. Use when asked to write an email sequence, a welcome/onboarding series, a nurture drip, a launch sequence, or a re-engagement series. Produces the sequence map (trigger, timing, goal per email) plus the full copy for each email — subject, body, and one CTA — designed to move the reader one step at a time.
npx skillsauth add mohitagw15856/pm-claude-skills email-sequenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A good sequence isn't a newsletter on a timer — each email has one job and earns the next open. This
skill maps the sequence (what triggers it, the cadence, the single goal of each email) and writes the
copy, so a welcome series activates, a nurture drip builds trust toward a sale, and a launch sequence
converts — without burning the list. (For the lifecycle strategy/segmentation, pair with
lifecycle-crm-plan; this writes the emails.)
Ask for these only if they aren't already provided:
1. Sequence map — the spine:
| # | Trigger / timing | Goal of this email | Angle | |---|---|---|---| | 1 | t+0 (on signup) | welcome + set the one expectation | warm | | 2 | t+2d | deliver a quick win | value | | 3 | t+4d | handle the top objection | proof | | 4 | t+6d | make the ask | CTA |
2. The emails — for each, the full copy: subject (+ a preview-text line), a short body with one idea, and one CTA. Each email earns the next: end with a hook forward where it helps.
3. Rules — the exit condition (e.g. stop the nurture once they convert), a frequency/suppression note, and the one metric per email to judge it by (not just opens).
Lifecycle email practice — one-goal-per-email sequences, value-before-ask, behaviour-triggered cadence with exits.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.