[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9832JCFQCMRCRJFPXDCAA":3,"skill-same:01M6M9832JCFQCMRCRJFPXDCAA":116},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6M9832JCFQCMRCRJFPXDCAA","suede-emails",null,"Use when asked \"build a welcome email sequence\" or to design nurture, onboarding, win-back, post-purchase or trigger-based lifecycle email flows. Suede AI returns entry and exit criteria, timing, exact copy, sender-rule checks and a measurement plan. NOT FOR: cold outbound (use suede-cold-email), SMS (use suede-sms), in-product onboarding (use suede-onboarding), or broader lifecycle operations (use suede-revops).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"suede emails","emails","trigger","when","sequence","for","measurement","purchase","flows","timing","cold","sms","design","outbound","back","returns","plan","email sequence","email","product","welcome","2026-11-10 10:12:30",false,"---\nname: suede-emails\ndescription: \"Use when asked \\\"build a welcome email sequence\\\" or to design nurture, onboarding, win-back, post-purchase or trigger-based lifecycle email flows. Suede AI returns entry and exit criteria, timing, exact copy, sender-rule checks and a measurement plan. NOT FOR: cold outbound (use suede-cold-email), SMS (use suede-sms), in-product onboarding (use suede-onboarding), or broader lifecycle operations (use suede-revops).\"\nmetadata:\n  display-name: \"Suede AI Lifecycle Email Skills\"\n  version: 2.1.0\n---\n\n# Suede AI Lifecycle Email Skills\n\nDesign lifecycle email as a consent-aware system of triggers, message roles, pacing, and measurable next actions. Create sequences that move a known audience toward value without inventing intent, exhausting the list, or confusing lifecycle messaging with cold outreach.\n\n## Compatibility\n\nAny agent with product, consent and lifecycle context. Current deliverability checks need web access; producing a handoff does not require an email-service integration.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n   - What other emails are they already receiving?\n   - What's the current email performance to beat?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principle\n\nOne email, one job: a single purpose and a single primary CTA per email. Everything downstream, sequence length, roles, copy, follows from that.\n\n---\n\n## Email Sequence Strategy\n\nSequence lengths are set per type in Sequence Types Overview below; use those numbers, not a generic range. Adjust for sales-cycle length, product complexity, and relationship stage.\n\n### Timing\u002FDelays\n- Welcome email: Immediately\n- Early sequence: 1-2 days apart\n- Nurture: 2-4 days apart\n- Long-term: Weekly or bi-weekly\n\nConsider:\n- B2B: Avoid weekends\n- B2C: Test weekends\n- Time zones: Send at local time\n\n### Subject Line Strategy\n- Clear > Clever\n- Specific > Vague\n- Benefit or curiosity-driven\n- 40-60 characters, front-loading the words that matter for mobile truncation\n- Test emoji (they're polarizing)\n- Judge subject tests on clicks or conversions, not opens: Apple Mail Privacy\n  Protection preloads images and inflates open rates\n\n**Patterns that work:**\n- Question: \"Still struggling with X?\"\n- How-to: \"How to [achieve outcome] in [timeframe]\"\n- Number: \"3 ways to [benefit]\"\n- Direct: \"[First name], your [thing] is ready\"\n- Story tease: \"The mistake I made with [topic]\"\n\n### Preview Text\n- Extends the subject line\n- ~90-140 characters\n- Don't repeat subject line\n- Complete the thought or add intrigue\n\n---\n\n## Sequence Types Overview\n\n### Welcome Sequence (Post-Signup)\n**Length**: 5-7 emails over 12-14 days\n**Goal**: Activate, build trust, convert\n\nKey emails:\n1. Welcome + deliver promised value (immediate)\n2. Quick win (day 1-2)\n3. Story\u002FWhy (day 3-4)\n4. Social proof (day 5-6)\n5. Overcome objection (day 7-8)\n6. Core feature highlight (day 9-11)\n7. Conversion (day 12-14)\n\n### Lead Nurture Sequence (Pre-Sale)\n**Length**: 6-8 emails over 2-3 weeks\n**Goal**: Build trust, demonstrate expertise, convert\n\nKey emails:\n1. Deliver lead magnet + intro (immediate)\n2. Expand on topic (day 2-3)\n3. Problem deep-dive (day 4-5)\n4. Solution framework (day 6-8)\n5. Case study (day 9-11)\n6. Differentiation (day 12-14)\n7. Objection handler (day 15-18)\n8. Direct offer (day 19-21)\n\n### Re-Engagement Sequence\n**Length**: 3-4 emails over 2 weeks\n**Trigger**: 30-60 days of inactivity\n**Goal**: Win back or clean list\n\nKey emails:\n1. Check-in (genuine concern)\n2. Value reminder (what's new)\n3. Incentive (special offer)\n4. Last chance (stay or unsubscribe)\n\n### Onboarding Sequence (Product Users)\n**Length**: 5-7 emails over 14 days\n**Goal**: Activate, drive to aha moment, upgrade\n**Note**: Coordinate with in-app onboarding: email supports, doesn't duplicate\n\nKey emails:\n1. Welcome + first step (immediate)\n2. Getting started help (day 1)\n3. Feature highlight (day 2-3)\n4. Success story (day 4-5)\n5. Check-in (day 7)\n6. Advanced tip (day 10-12)\n7. Upgrade\u002Fexpand (day 14+)\n\n**For detailed templates**: See [references\u002Fsequence-templates.md](references\u002Fsequence-templates.md)\n\n---\n\n## Email Types by Category\n\nSix categories: Onboarding · Retention · Billing · Usage · Win-Back · Campaigns.\n\nRead [references\u002Femail-types.md](references\u002Femail-types.md) when you need to pick or design an individual email type: it carries the trigger, timing, role, and copy pattern for each one, plus an email audit checklist.\n\n---\n\n## Email Copy Guidelines\n\n### Structure\n1. **Hook**: First line grabs attention\n2. **Context**: Why this matters to them\n3. **Value**: The useful content\n4. **CTA**: What to do next\n5. **Sign-off**: Human, warm close\n\n### Formatting\n- Short paragraphs (1-3 sentences)\n- White space between sections\n- Bullet points for scanability\n- Bold for emphasis (sparingly)\n- Mobile-first (most read on phone)\n\n### Tone\n- Conversational, not formal\n- First-person (I\u002Fwe) and second-person (you)\n- Active voice\n- Read it out loud: does it sound human?\n\n**Never ship these strings.** They are the lifecycle-email defaults a model reaches for unprompted, and every one of them is a slot where a specific sentence should be:\n\n- \"We're thrilled to have you aboard!\" \u002F \"We're excited to have you!\"\n- \"Welcome to the family!\" \u002F \"You're in good company\"\n- \"Here's what you can do next\" \u002F \"Let's get you started\"\n- \"Don't miss out\" \u002F \"Act now\" \u002F \"Limited time only\"\n- \"Quick question\" \u002F \"Just checking in\" \u002F \"Just following up\"\n- \"We noticed you haven't...\" \u002F \"We miss you!\"\n- \"Ready to take your [X] to the next level?\"\n- \"Unlock the full power of...\" \u002F \"Supercharge your...\"\n- \"As a valued customer\" \u002F \"We value your feedback\"\n\nThe replacement is always the same shape: name the specific thing this reader did, or the specific thing they get next. If a sentence would be true for any recipient of any product, it is one of these in disguise.\n\n### Length\n- 50-125 words for transactional\n- 150-300 words for educational\n- 300-500 words for story-driven\n\n### CTA Guidelines\n- Buttons for primary actions\n- Links for secondary actions\n- One clear primary CTA per email\n- Button text: Action + outcome\n\n**For detailed copy, personalization, and testing guidelines**: See [references\u002Fcopy-guidelines.md](references\u002Fcopy-guidelines.md)\n\n---\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\n```\nPer email: open rate, click rate, unsubscribe rate\nPer sequence: completion rate, primary-conversion rate, revenue or signups attributed\nBaseline: [the user's current numbers for this audience, or \"none supplied\"]\nReview point: [when to read results and what number would trigger a rewrite]\n```\n\n---\n\n## Pre-delivery self-check\n\nRun this on the drafted sequence before presenting it. Each box checks a rule this skill already states, against the copy you just wrote.\n\n- [ ] Every email has exactly one primary CTA\n- [ ] Every subject line is 40-60 characters: count them, do not estimate\n- [ ] No preview text repeats its subject line\n- [ ] Every body is inside the word band for its type (50-125 transactional \u002F 150-300 educational \u002F 300-500 story-driven)\n- [ ] Exit conditions are specified for the sequence\n- [ ] No string from the Tone blocklist appears anywhere in the copy\n- [ ] The consent and suppression assumption is stated explicitly rather than assumed: say which list, which opt-in, and what excludes a contact\n- [ ] Every marketing email is marked for one-click unsubscribe (RFC 8058 headers) and the plan says unsubscribes are honored within 48 hours\n- [ ] The re-engagement or win-back flow ends by suppressing contacts who never re-engage\n\nAny box that fails means fix it before presenting. Do not deliver the sequence with the failure noted as a caveat.\n\n---\n\n## Implementation Hand-off\n\nChoose the provider only after reading the user's installed tools and live account state. Customer.io, Mailchimp, Resend, SendGrid, Kit, and similar services may support parts of the workflow, but this public Suede skill does not assume that any provider, connector, account, or permission is available.\n\nBefore implementation, return:\n\n1. The required trigger, audience, fields, suppression rules, and exit criteria\n2. The provider-neutral sequence and event contract\n3. The exact account or integration that must be inspected\n4. The deliverability checklist from\n   [references\u002Fdeliverability.md](references\u002Fdeliverability.md): SPF, DKIM,\n   DMARC alignment, one-click unsubscribe, complaint-rate monitoring below\n   0.1%, and separated transactional and marketing streams. Gmail began\n   rejecting non-compliant bulk mail more aggressively in November 2025, and\n   Microsoft has enforced its high-volume rules since May 2025.\n5. A preview-and-approval checkpoint before any live change or send\n\n---\n\n## Boundaries\n\n- Do not send, schedule, import contacts, alter automations, or change suppression lists without explicit authorization.\n- Do not invent consent, deliverability, attribution, audience, or performance data.\n- Do not promise inbox placement or revenue; separate observed results from projections.\n- Do not decide legal compliance, transactional classification, or contact eligibility on the user's behalf.\n\n## Routing\n\n- Use `suede-lead-magnets` for the asset that feeds a nurture sequence.\n- Use `suede-churn-prevention` for cancellation, save, and dunning strategy.\n- Use `suede-onboarding` for in-product activation and `suede-copy` for destination-page copy.\n- Use `suede-ab-testing` for sequence experiments and `suede-revops` for lifecycle-stage orchestration.\n- Use `suede-sms` when the same lifecycle program should also reach people by text: SMS layers on top of email, it does not replace it.\n- Use `suede-deslop` before any email in the sequence goes to a real recipient.\n- From those skills, route lifecycle sequence design, cadence, and message roles back to `suede-emails`.\n\n## Worked contract\n\n[Worked contract](references\u002Fusage-contract.md) gives a bounded input, expected output and failure check for this workflow.\n","# Suede AI Lifecycle Email Skills\n\nDesign lifecycle email as a consent-aware system of triggers, message roles, pacing, and measurable next actions. Create sequences that move a known audience toward value without inventing intent, exhausting the list, or confusing lifecycle messaging with cold outreach.\n\n## Compatibility\n\nAny agent with product, consent and lifecycle context. Current deliverability checks need web access; producing a handoff does not require an email-service integration.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n   - What other emails are they already receiving?\n   - What's the current email performance to beat?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principle\n\nOne email, one job: a single purpose and a single primary CTA per email. Everything downstream, sequence length, roles, copy, follows from that.\n\n---\n\n## Email Sequence Strategy\n\nSequence lengths are set per type in Sequence Types Overview below; use those numbers, not a generic range. Adjust for sales-cycle length, product complexity, and relationship stage.\n\n### Timing\u002FDelays\n- Welcome email: Immediately\n- Early sequence: 1-2 days apart\n- Nurture: 2-4 days apart\n- Long-term: Weekly or bi-weekly\n\nConsider:\n- B2B: Avoid weekends\n- B2C: Test weekends\n- Time zones: Send at local time\n\n### Subject Line Strategy\n- Clear > Clever\n- Specific > Vague\n- Benefit or curiosity-driven\n- 40-60 characters, front-loading the words that matter for mobile truncation\n- Test emoji (they're polarizing)\n- Judge subject tests on clicks or conversions, not opens: Apple Mail Privacy\n  Protection preloads images and inflates open rates\n\n**Patterns that work:**\n- Question: \"Still struggling with X?\"\n- How-to: \"How to [achieve outcome] in [timeframe]\"\n- Number: \"3 ways to [benefit]\"\n- Direct: \"[First name], your [thing] is ready\"\n- Story tease: \"The mistake I made with [topic]\"\n\n### Preview Text\n- Extends the subject line\n- ~90-140 characters\n- Don't repeat subject line\n- Complete the thought or add intrigue\n\n---\n\n## Sequence Types Overview\n\n### Welcome Sequence (Post-Signup)\n**Length**: 5-7 emails over 12-14 days\n**Goal**: Activate, build trust, convert\n\nKey emails:\n1. Welcome + deliver promised value (immediate)\n2. Quick win (day 1-2)\n3. Story\u002FWhy (day 3-4)\n4. Social proof (day 5-6)\n5. Overcome objection (day 7-8)\n6. Core feature highlight (day 9-11)\n7. Conversion (day 12-14)\n\n### Lead Nurture Sequence (Pre-Sale)\n**Length**: 6-8 emails over 2-3 weeks\n**Goal**: Build trust, demonstrate expertise, convert\n\nKey emails:\n1. Deliver lead magnet + intro (immediate)\n2. Expand on topic (day 2-3)\n3. Problem deep-dive (day 4-5)\n4. Solution framework (day 6-8)\n5. Case study (day 9-11)\n6. Differentiation (day 12-14)\n7. Objection handler (day 15-18)\n8. Direct offer (day 19-21)\n\n### Re-Engagement Sequence\n**Length**: 3-4 emails over 2 weeks\n**Trigger**: 30-60 days of inactivity\n**Goal**: Win back or clean list\n\nKey emails:\n1. Check-in (genuine concern)\n2. Value reminder (what's new)\n3. Incentive (special offer)\n4. Last chance (stay or unsubscribe)\n\n### Onboarding Sequence (Product Users)\n**Length**: 5-7 emails over 14 days\n**Goal**: Activate, drive to aha moment, upgrade\n**Note**: Coordinate with in-app onboarding: email supports, doesn't duplicate\n\nKey emails:\n1. Welcome + first step (immediate)\n2. Getting started help (day 1)\n3. Feature highlight (day 2-3)\n4. Success story (day 4-5)\n5. Check-in (day 7)\n6. Advanced tip (day 10-12)\n7. Upgrade\u002Fexpand (day 14+)\n\n**For detailed templates**: See [references\u002Fsequence-templates.md](references\u002Fsequence-templates.md)\n\n---\n\n## Email Types by Category\n\nSix categories: Onboarding · Retention · Billing · Usage · Win-Back · Campaigns.\n\nRead [references\u002Femail-types.md](references\u002Femail-types.md) when you need to pick or design an individual email type: it carries the trigger, timing, role, and copy pattern for each one, plus an email audit checklist.\n\n---\n\n## Email Copy Guidelines\n\n### Structure\n1. **Hook**: First line grabs attention\n2. **Context**: Why this matters to them\n3. **Value**: The useful content\n4. **CTA**: What to do next\n5. **Sign-off**: Human, warm close\n\n### Formatting\n- Short paragraphs (1-3 sentences)\n- White space between sections\n- Bullet points for scanability\n- Bold for emphasis (sparingly)\n- Mobile-first (most read on phone)\n\n### Tone\n- Conversational, not formal\n- First-person (I\u002Fwe) and second-person (you)\n- Active voice\n- Read it out loud: does it sound human?\n\n**Never ship these strings.** They are the lifecycle-email defaults a model reaches for unprompted, and every one of them is a slot where a specific sentence should be:\n\n- \"We're thrilled to have you aboard!\" \u002F \"We're excited to have you!\"\n- \"Welcome to the family!\" \u002F \"You're in good company\"\n- \"Here's what you can do next\" \u002F \"Let's get you started\"\n- \"Don't miss out\" \u002F \"Act now\" \u002F \"Limited time only\"\n- \"Quick question\" \u002F \"Just checking in\" \u002F \"Just following up\"\n- \"We noticed you haven't...\" \u002F \"We miss you!\"\n- \"Ready to take your [X] to the next level?\"\n- \"Unlock the full power of...\" \u002F \"Supercharge your...\"\n- \"As a valued customer\" \u002F \"We value your feedback\"\n\nThe replacement is always the same shape: name the specific thing this reader did, or the specific thing they get next. If a sentence would be true for any recipient of any product, it is one of these in disguise.\n\n### Length\n- 50-125 words for transactional\n- 150-300 words for educational\n- 300-500 words for story-driven\n\n### CTA Guidelines\n- Buttons for primary actions\n- Links for secondary actions\n- One clear primary CTA per email\n- Button text: Action + outcome\n\n**For detailed copy, personalization, and testing guidelines**: See [references\u002Fcopy-guidelines.md](references\u002Fcopy-guidelines.md)\n\n---\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\n```\nPer email: open rate, click rate, unsubscribe rate\nPer sequence: completion rate, primary-conversion rate, revenue or signups attributed\nBaseline: [the user's current numbers for this audience, or \"none supplied\"]\nReview point: [when to read results and what number would trigger a rewrite]\n```\n\n---\n\n## Pre-delivery self-check\n\nRun this on the drafted sequence before presenting it. Each box checks a rule this skill already states, against the copy you just wrote.\n\n- [ ] Every email has exactly one primary CTA\n- [ ] Every subject line is 40-60 characters: count them, do not estimate\n- [ ] No preview text repeats its subject line\n- [ ] Every body is inside the word band for its type (50-125 transactional \u002F 150-300 educational \u002F 300-500 story-driven)\n- [ ] Exit conditions are specified for the sequence\n- [ ] No string from the Tone blocklist appears anywhere in the copy\n- [ ] The consent and suppression assumption is stated explicitly rather than assumed: say which list, which opt-in, and what excludes a contact\n- [ ] Every marketing email is marked for one-click unsubscribe (RFC 8058 headers) and the plan says unsubscribes are honored within 48 hours\n- [ ] The re-engagement or win-back flow ends by suppressing contacts who never re-engage\n\nAny box that fails means fix it before presenting. Do not deliver the sequence with the failure noted as a caveat.\n\n---\n\n## Implementation Hand-off\n\nChoose the provider only after reading the user's installed tools and live account state. Customer.io, Mailchimp, Resend, SendGrid, Kit, and similar services may support parts of the workflow, but this public Suede skill does not assume that any provider, connector, account, or permission is available.\n\nBefore implementation, return:\n\n1. The required trigger, audience, fields, suppression rules, and exit criteria\n2. The provider-neutral sequence and event contract\n3. The exact account or integration that must be inspected\n4. The deliverability checklist from\n   [references\u002Fdeliverability.md](references\u002Fdeliverability.md): SPF, DKIM,\n   DMARC alignment, one-click unsubscribe, complaint-rate monitoring below\n   0.1%, and separated transactional and marketing streams. Gmail began\n   rejecting non-compliant bulk mail more aggressively in November 2025, and\n   Microsoft has enforced its high-volume rules since May 2025.\n5. A preview-and-approval checkpoint before any live change or send\n\n---\n\n## Boundaries\n\n- Do not send, schedule, import contacts, alter automations, or change suppression lists without explicit authorization.\n- Do not invent consent, deliverability, attribution, audience, or performance data.\n- Do not promise inbox placement or revenue; separate observed results from projections.\n- Do not decide legal compliance, transactional classification, or contact eligibility on the user's behalf.\n\n## Routing\n\n- Use `suede-lead-magnets` for the asset that feeds a nurture sequence.\n- Use `suede-churn-prevention` for cancellation, save, and dunning strategy.\n- Use `suede-onboarding` for in-product activation and `suede-copy` for destination-page copy.\n- Use `suede-ab-testing` for sequence experiments and `suede-revops` for lifecycle-stage orchestration.\n- Use `suede-sms` when the same lifecycle program should also reach people by text: SMS layers on top of email, it does not replace it.\n- Use `suede-deslop` before any email in the sequence goes to a real recipient.\n- From those skills, route lifecycle sequence design, cadence, and message roles back to `suede-emails`.\n\n## Worked contract\n\n[Worked contract](references\u002Fusage-contract.md) gives a bounded input, expected output and failure check for this workflow.\n",{"name":5,"metadata":55,"description":7},{"version":56,"display-name":57},"2.1.0","Suede AI Lifecycle Email Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-emails",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-emails",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-emails","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002FSKILL.md",true,[82,88,92,96,100,104,108,112],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"agents\u002Fopenai.yaml","REFERENCE","参考文档",556,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Fagents\u002Fopenai.yaml",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"CARD.md",4506,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002FCARD.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Fevals.json",6672,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Fevals\u002Fevals.json",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fcopy-guidelines.md",2331,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Freferences\u002Fcopy-guidelines.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fdeliverability.md",3360,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Freferences\u002Fdeliverability.md",{"path":105,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Femail-types.md",14243,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Freferences\u002Femail-types.md",{"path":109,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fsequence-templates.md",3909,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Freferences\u002Fsequence-templates.md",{"path":113,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fusage-contract.md",898,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-emails\u002Freferences\u002Fusage-contract.md",[117,125,132,139,164,189],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":124},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":124},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":124},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":50},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[146,147,148,149,150,151,152,153,154,41,155,32,156,157,158,159,160,161,162,163],"search","deja search","never","error","ready","memory","re","decide","fix","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":50},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[171,172,173,159,174,175,176,177,178,179,180,181,182,183,151,184,185,186,187,188],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":204,"publishedAt":50},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[191,205,206,207,208,209,210,185,211,152,212,213,214,215,32,216,217,218,219,220],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]