luckiest-co 1.0.0 → 1.0.3

package/skills/luckiest-emails/SKILL.md

@@ -0,0 +1,220 @@
+---
+name: luckiest-emails
+description: Designs and optimizes email sequences, drip campaigns, automated flows, and lifecycle email programs. Use when the user wants to build or improve a multi-email automated flow, or mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." For cold outreach emails, see luckiest-cold-email. For in-app onboarding, see luckiest-onboarding.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-emails
+  author: luckiest
+---
+
+# Email Sequence Design
+
+This skill designs email sequences that nurture relationships, drive action, and
+move people toward conversion. It applies expert email-marketing and automation
+practice to any multi-email automated flow.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-emails", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-emails", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or
+the legacy `product-marketing-context.md` filename in older setups), read it
+before asking questions. Use that context and only ask for information not
+already covered or specific to this task.
+
+Before creating a sequence, understand:
+
+1. **Sequence Type** — welcome/onboarding, lead nurture, re-engagement,
+   post-purchase, event-based, educational, or sales.
+
+2. **Audience Context** — who they are, what triggered them into this sequence,
+   what they already know/believe, and their current relationship with the sender.
+
+3. **Goals** — primary conversion goal, relationship-building goals,
+   segmentation goals, and what defines success.
+
+---
+
+## Core Principles
+
+1. **One Email, One Job** — each email has one primary purpose and one main CTA.
+2. **Value Before Ask** — lead with usefulness; earn the right to sell.
+3. **Relevance Over Volume** — fewer, better, segmented emails win.
+4. **Clear Path Forward** — every email moves the reader somewhere useful.
+
+---
+
+## Email Sequence Strategy
+
+### Sequence Length
+- Welcome: 3-7 emails
+- Lead nurture: 5-10 emails
+- Onboarding: 5-10 emails
+- Re-engagement: 3-5 emails
+
+Depends on sales cycle length, product complexity, and relationship stage.
+
+### Timing/Delays
+- Welcome email: immediately
+- Early sequence: 1-2 days apart
+- Nurture: 2-4 days apart
+- Long-term: weekly or bi-weekly
+
+Prefer **behavior-triggered** sends (action completed → next email) over fixed
+time delays where the platform allows, with time-based sends as the fallback.
+Consider: B2B avoid weekends; B2C test weekends; send at the recipient's local time.
+
+### Subject Line Strategy
+- Clear > clever, specific > vague, benefit- or curiosity-driven
+- 40-60 characters ideal; test emoji (they are polarizing)
+
+**Patterns that work:**
+- Question: "Still struggling with X?"
+- How-to: "How to [achieve outcome] in [timeframe]"
+- Number: "3 ways to [benefit]"
+- Direct: "[First name], your [thing] is ready"
+- Story tease: "The mistake I made with [topic]"
+
+### Preview Text
+- Extends the subject line (~90-140 characters)
+- Does not repeat the subject; completes the thought or adds intrigue
+
+### Exit Conditions and Suppression
+Design these up front, not as an afterthought:
+- Define what removes a subscriber from the sequence (converted, replied,
+  unsubscribed, bounced).
+- When a subscriber completes the sequence's goal mid-flow, suppress the
+  remaining emails or branch them into the next-stage flow — never keep selling
+  something they already bought.
+- Frequency-cap across overlapping sequences so no one is over-mailed.
+
+---
+
+## Sequence Types Overview
+
+- **Welcome (post-signup):** 5-7 emails over 12-14 days. Goal: activate, build
+  trust, convert.
+- **Lead nurture (pre-sale):** 6-8 emails over 2-3 weeks. Goal: build trust,
+  demonstrate expertise, convert.
+- **Re-engagement:** 3-4 emails over ~2 weeks, triggered by 30-60 days of
+  inactivity. Goal: win back or clean the list. End with a **sunset policy** —
+  remove non-responders after the final "last chance" email to protect
+  deliverability.
+- **Onboarding (product users):** 5-7 emails over 14 days. Goal: activate, drive
+  to the aha moment, upgrade. Coordinate with in-app onboarding — email supports,
+  it does not duplicate.
+
+**For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md)
+
+---
+
+## Email Types by Category
+
+Onboarding, retention, billing, usage, win-back, and campaign emails each cover
+distinct lifecycle moments.
+
+**For the full email-type reference and audit checklist**: See [references/email-types.md](references/email-types.md)
+
+---
+
+## Email Copy Guidelines
+
+### Structure
+Hook → Context → Value → CTA → Sign-off.
+
+### Formatting
+Short paragraphs (1-3 sentences), white space, bullets for scanability, bold
+sparingly, mobile-first.
+
+### Tone
+Conversational not formal; first- and second-person; active voice; read it out
+loud to check it sounds human.
+
+### Length
+50-125 words transactional; 150-300 educational; 300-500 story-driven.
+
+### CTA
+Buttons for primary actions, links for secondary; one clear primary CTA per
+email; button text = action + outcome.
+
+### Deliverability and Consent
+Authenticate the sending domain (SPF/DKIM/DMARC) and warm up new domains before
+bulk sending. Every email needs a working one-click unsubscribe and honors the
+recipient's consent basis (CAN-SPAM, GDPR/PECR).
+
+**For detailed copy, personalization, segmentation, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md)
+
+---
+
+## Output Format
+
+### Sequence Overview
+```
+Sequence Name: [Name]
+Trigger: [What starts the sequence]
+Goal: [Primary conversion goal]
+Length: [Number of emails]
+Timing: [Delay between emails]
+Exit Conditions: [When they leave the sequence, incl. mid-flow conversion]
+```
+
+### For Each Email
+```
+Email [#]: [Name/Purpose]
+Send: [Timing]
+Subject: [Subject line]
+Preview: [Preview text]
+Body: [Full copy]
+CTA: [Button text] → [Link destination]
+Segment/Conditions: [If applicable]
+```
+
+### Metrics Plan
+What to measure and benchmarks (open, click, unsubscribe, conversion).
+
+---
+
+## Task-Specific Questions
+
+1. What triggers entry to this sequence?
+2. What's the primary goal/conversion action?
+3. What do they already know about you?
+4. What other emails are they receiving?
+5. What's your current email performance?
+
+---
+
+## Tool Integrations
+
+For implementation, see the tools registry. Key email tools include Customer.io
+(behavior-based automation), Mailchimp (SMB), Nitrosend (AI-native), Resend
+(developer-friendly transactional), SendGrid (transactional at scale), and Kit
+(creator/newsletter).
+
+---
+
+## Share with your tribe
+
+After delivering a sequence, offer (never auto-post, never touch credentials):
+"Want me to surface this sequence plan to your Luckiest tribe? Anyone building a
+similar flow will see the structure and timing you landed on." If they accept,
+hand off the sequence plan to the tribe-share flow. If they decline, stop. Do not
+share a sequence tied to a private or unreleased launch without an explicit ask.
+
+---
+
+## Related Skills
+
+- **luckiest-lead-magnets**: planning lead magnets that feed nurture sequences
+- **luckiest-churn-prevention**: cancel flows, save offers, dunning strategy
+- **luckiest-onboarding**: in-app onboarding (email supports this)
+- **luckiest-copywriting**: landing pages emails link to
+- **luckiest-ab-testing**: testing email elements
+- **luckiest-popups**: email capture popups
+- **luckiest-revops**: lifecycle stages that trigger email sequences

package/skills/luckiest-emails/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "luckiest-emails",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Create a welcome email sequence for new users who sign up for our project management tool's free trial. The trial is 14 days. We want to get them to their aha moment (creating their first project and inviting a team member).",
+      "expected_output": "Should check for product-marketing.md first. Should create a welcome sequence (5-7 emails) following the core principles: one email one job, value before ask. Should map each email to a specific goal in the 14-day trial journey. Should include timing/delays between emails. Each email should follow the email copy structure: hook \u2192 context \u2192 value \u2192 CTA \u2192 sign-off. Should include subject lines following the subject line strategy. Should align sequence with the aha moment (first project + team invite). Output should follow the structured format with sequence overview and per-email specs.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Creates 5-7 email welcome sequence",
+        "Follows one email one job principle",
+        "Maps emails to trial timeline (14 days)",
+        "Includes timing between emails",
+        "Each email has hook, context, value, CTA",
+        "Includes subject lines for each email",
+        "Aligns with stated aha moment",
+        "Output follows structured per-email format"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We need a lead nurture sequence for people who download our 'State of DevOps 2024' report. Goal is to get them to book a demo of our CI/CD platform.",
+      "expected_output": "Should create a lead nurture sequence (6-8 emails). Should follow value before ask \u2014 first emails should provide related value, not immediately push for demo. Should map the sequence from awareness (report download) through consideration (related content, case studies) to decision (demo request). Should include timing between emails. Each email should have clear subject line, hook, single CTA. Should gradually increase commitment asks across the sequence.",
+      "assertions": [
+        "Creates 6-8 email lead nurture sequence",
+        "Follows value before ask principle",
+        "Maps from awareness through consideration to decision",
+        "Includes timing between emails",
+        "Each email has clear subject line and single CTA",
+        "Gradually increases commitment asks",
+        "Connects to original download topic"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our email open rates have tanked. used to be 35% now we're at 18%. what's going on and how do we fix our subject lines?",
+      "expected_output": "Should trigger on casual phrasing. Should diagnose potential causes of declining open rates: sender reputation, list hygiene, subject line quality, sending frequency, deliverability issues. Should apply the subject line strategy from the skill: test curiosity vs benefit vs urgency patterns, personalization, optimal length. Should recommend a re-engagement campaign to clean the list. Should provide specific subject line formulas and examples. Should suggest testing framework for subject lines.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Diagnoses potential causes beyond just subject lines",
+        "Addresses sender reputation and deliverability",
+        "Recommends list hygiene or re-engagement",
+        "Applies subject line strategy with specific patterns",
+        "Provides subject line formulas and examples",
+        "Suggests testing framework"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Build a re-engagement sequence for subscribers who haven't opened any emails in 90 days. We have about 5,000 inactive subscribers.",
+      "expected_output": "Should create a re-engagement sequence (3-4 emails). Should follow the re-engagement pattern: first email acknowledges absence and offers value, middle emails escalate with compelling reasons to re-engage, final email is a clear 'last chance' before removal. Should recommend aggressive subject lines to break through. Should include a sunset policy (remove non-responders after sequence completes). Should address the impact on deliverability of keeping inactive subscribers.",
+      "assertions": [
+        "Creates 3-4 email re-engagement sequence",
+        "Acknowledges absence in first email",
+        "Escalates through the sequence",
+        "Includes 'last chance' final email",
+        "Recommends sunset policy for non-responders",
+        "Addresses deliverability impact of inactive subscribers",
+        "Uses compelling subject lines"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What's the ideal timing for our onboarding email sequence? We send the first email immediately after signup, but we're not sure about the rest.",
+      "expected_output": "Should provide timing guidance for onboarding sequences. Should reference the timing and delays framework: immediate first email (welcome/confirmation), then suggest data-driven timing based on user behavior triggers vs fixed time delays. Should recommend behavior-triggered emails when possible (user completed action \u2192 next email) with time-based fallbacks. Should provide typical timing patterns for SaaS onboarding (day 0, day 1, day 3, day 5, day 7, etc.). Should note that optimal timing depends on product complexity and trial length.",
+      "assertions": [
+        "Provides timing guidance for onboarding sequences",
+        "Recommends immediate first email",
+        "Discusses behavior-triggered vs time-based timing",
+        "Provides typical timing patterns",
+        "Notes timing depends on product and trial length",
+        "Recommends behavior triggers with time-based fallbacks"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me optimize our post-signup onboarding experience. Users sign up but 60% never complete setup.",
+      "expected_output": "Should recognize this is an in-app onboarding optimization task, not an email sequence task. Should defer to or cross-reference the onboarding skill, which handles in-app onboarding flows, checklists, and activation optimization. May offer to help with the email component of onboarding but should make clear that onboarding is the primary skill for this task.",
+      "assertions": [
+        "Recognizes this as in-app onboarding optimization",
+        "References or defers to onboarding skill",
+        "Does not attempt full onboarding redesign using email patterns",
+        "May offer email component support"
+      ],
+      "files": []
+    }
+  ]
+}

package/skills/luckiest-emails/references/copy-guidelines.md

@@ -0,0 +1,120 @@
+# Email Copy Guidelines
+
+## Contents
+- Structure
+- Formatting
+- Tone
+- Length
+- CTA Buttons vs. Links
+- Personalization (merge fields, dynamic content, triggered emails)
+- Segmentation Strategies (by behavior, by stage, by profile)
+- Testing and Optimization (what to test, how to test, metrics to track)
+
+## Structure
+
+1. **Hook**: First line grabs attention
+2. **Context**: Why this matters to them
+3. **Value**: The useful content
+4. **CTA**: What to do next
+5. **Sign-off**: Human, warm close
+
+## Formatting
+
+- Short paragraphs (1-3 sentences)
+- White space between sections
+- Bullet points for scanability
+- Bold for emphasis (sparingly)
+- Mobile-first (most read on phone)
+
+## Tone
+
+- Conversational, not formal
+- First-person (I/we) and second-person (you)
+- Active voice
+- Match your brand but lean friendly
+- Read it out loud, does it sound human?
+
+## Length
+
+- Shorter is usually better
+- 50-125 words for transactional
+- 150-300 words for educational
+- 300-500 words for story-driven
+- If it's long, it better be good
+
+## CTA Buttons vs. Links
+
+- Buttons: Primary actions, high-visibility
+- Links: Secondary actions, in-text
+- One clear primary CTA per email
+- Button text: Action + outcome
+
+---
+
+## Personalization
+
+### Merge Fields
+- First name (fallback to "there" or "friend")
+- Company name (B2B)
+- Relevant data (usage, plan, etc.)
+
+### Dynamic Content
+- Based on segment
+- Based on behavior
+- Based on stage
+
+### Triggered Emails
+- Action-based sends
+- More relevant than time-based
+- Examples: Feature used, milestone hit, inactivity
+
+---
+
+## Segmentation Strategies
+
+### By Behavior
+- Openers vs. non-openers
+- Clickers vs. non-clickers
+- Active vs. inactive
+
+### By Stage
+- Trial vs. paid
+- New vs. long-term
+- Engaged vs. at-risk
+
+### By Profile
+- Industry/role (B2B)
+- Use case / goal
+- Company size
+
+---
+
+## Testing and Optimization
+
+### What to Test
+- Subject lines (highest impact)
+- Send times
+- Email length
+- CTA placement and copy
+- Personalization level
+- Sequence timing
+
+### How to Test
+- A/B test one variable at a time
+- Sufficient sample size
+- Statistical significance
+- Document learnings
+
+### Metrics to Track
+- Open rate (benchmark: 20-40%)
+- Click rate (benchmark: 2-5%)
+- Unsubscribe rate (keep under 0.5%)
+- Conversion rate (specific to sequence goal)
+- Revenue per email (if applicable)
+
+### Deliverability and Consent (design constraint, not an afterthought)
+- Authenticate the sending domain (SPF, DKIM, DMARC) before any bulk send
+- Warm up new domains/IPs gradually
+- Every email needs a working, one-click unsubscribe and a physical address
+- Honor consent basis (CAN-SPAM, GDPR/PECR) for the recipient's region
+- Frequency-cap across overlapping sequences so no subscriber is over-mailed