email-campaign
$
npx mdskill add mohitagw15856/pm-claude-skills/email-campaignThis skill writes complete, sequenced email campaigns — from welcome flows to product launches to re-engagement sequences. Each email is written with subject line, preview text, full body copy, and CTA.
SKILL.md
.github/skills/email-campaignView on GitHub ↗
--- name: email-campaign description: "Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence." --- # Email Campaign Skill This skill writes complete, sequenced email campaigns — from welcome flows to product launches to re-engagement sequences. Each email is written with subject line, preview text, full body copy, and CTA. ## Required Inputs Ask the user for these if not provided: - **Campaign goal** (onboard new users / launch a product / nurture leads / re-engage churned users / announce a feature) - **Audience** (who receives this? job title, lifecycle stage, what they know already) - **Product or offer** being promoted or introduced - **Number of emails in sequence** (if unsure, recommend based on goal) - **Tone** (professional / conversational / bold / educational) - **Sender name** (person or brand?) ## Sequence Recommendations by Goal If the user hasn't specified number of emails, use these defaults: - **Onboarding:** 4 emails over 7 days (Day 0, Day 1, Day 3, Day 7) - **Product launch:** 3 emails (Teaser → Launch Day → Follow-up/Last chance) - **Lead nurture:** 5 emails over 2 weeks - **Re-engagement:** 3 emails (Gentle nudge → Value reminder → Final offer) - **Feature announcement:** 2 emails (Announcement → How-to/deep dive) ## Output Structure Per Email For every email in the sequence, produce: --- **Email [N] of [Total] — [Descriptive label e.g. "Welcome / Day 0"]** **Send timing:** [When relative to trigger event or previous email] **Subject line:** [Primary option] **Subject line (A/B variant):** [Alternative to test] **Preview text:** [40–90 characters — adds context to the subject, doesn't repeat it] **Body:** [Full email copy — formatted with clear opening line, 2–3 body paragraphs, one primary CTA] **CTA button text:** [3–6 words] **CTA destination:** [What page/action this should link to] **Strategic note:** [Why this email does what it does — the psychological or strategic intent. 1–2 sentences.] --- ## Writing Rules - Opening line must earn attention — no "Hi, welcome to [product]" openers - Each email has ONE primary CTA — never two competing asks - Keep paragraphs to 2–3 sentences maximum for mobile readability - Use "you" more than "we" — centre the reader, not the brand - Subject lines under 50 characters perform best on mobile — flag if going over - Preview text should add information the subject doesn't — never just repeat it - Every email should stand alone — assume some subscribers miss earlier emails ## Quality Checks - [ ] Each email has a single clear CTA - [ ] Subject lines are under 50 characters (or flagged) - [ ] Preview text doesn't repeat the subject line - [ ] Opening line is specific and attention-earning - [ ] Sequence has logical narrative arc (doesn't feel like disconnected blasts) - [ ] Tone is consistent across all emails - [ ] Strategic notes explain the intent of each email ## Example Trigger Phrases - "Write a 3-email launch sequence for [product]" - "Build an onboarding email flow for [SaaS tool]" - "Create a drip campaign to nurture leads for [offer]" - "Write a re-engagement campaign for churned users"
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.