mcpField
L
lifecycle-email-system-review

lifecycle-email-system-review

github.com/sylphxaiMarketing & growth140 installsUpdated today
Repository

About lifecycle-email-system-review

This skill turns lifecycle email system questions into planning artifacts with owners, gates, metrics, and recovery paths. It is for teams designing or reviewing messages across user journeys, covering consent, deliverability, suppression, triggers, and product outcomes.

Key features

  1. 01Identify journey, purpose, and consent basis
  2. 02Define audience, triggers, and cadence
  3. 03Set suppression, unsubscribe, and preference rules
  4. 04Plan deliverability checks and event tracking
  5. 05Create email plans, state machines, and QA checklists

Use cases

  1. 01Plan an onboarding email sequence
  2. 02Review consent and suppression for winback emails
  3. 03Set email cadence and deliverability checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill lifecycle-email-system-review

After installing, type/lifecycle-email-system-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/lifecycle-email-system-patterns.md

Details

From the project README

Lifecycle Email System Review

Use this skill to convert a lifecycle email, segmentation, consent, deliverability, suppression, triggers, personalization, and product outcomes question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify user journey, message purpose, consent basis, segment, trigger, sender reputation, localization, suppression rules, and success metric.
  2. Read references/lifecycle-email-system-patterns.md.
  3. Classify message as transactional, onboarding, activation, education, retention, winback, billing, trust/safety, community, or marketing campaign.
  4. Define audience, trigger, eligibility, suppression, cadence, content, deliverability checks, unsubscribe/preference behavior, event tracking, and support fallback.
  5. Produce lifecycle email plan, state machine, decision table, event schema, QA checklist, and fatigue-control policy.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not send marketing or winback emails without consent, suppression, unsubscribe, and preference handling.
  • Do not mix transactional necessity with promotional content in ways that undermine compliance or trust.
  • Do not optimize opens/clicks without activation, retention, refund, complaint, and unsubscribe guardrails.
  • Do not keep emailing users after churn, deletion, region restrictions, or support opt-out without explicit policy.

Output format

Lifecycle email context:
Journey / consent / trigger / deliverability risk:

Lifecycle email plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Segments, triggers, and suppression:
- <item> -> <policy, metric, edge case, support note>

Fatigue and compliance policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported