[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MY993XSV88RM9FKHCM253":3,"skill-same:01M71MY993XSV88RM9FKHCM253":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M71MY993XSV88RM9FKHCM253","email-sequences",null,"Use when creating or optimizing an automated email sequence: welcome, onboarding, lead nurture, re-engagement, post-purchase or lifecycle drip flows. Covers sequence types, timing and per-email copy; for B2B cold outreach use cold-email.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000038","人力资源",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"sequences","email","email sequences","timing","lead","when","sequence","for","purchase","re","flows","types","writing","cold","b2b","cold outreach","marketing","lifecycle","email sequence","welcome","2026-11-10 10:56:23",false,"---\nname: email-sequences\ndescription: \"Use when creating or optimizing an automated email sequence: welcome, onboarding, lead nurture, re-engagement, post-purchase or lifecycle drip flows. Covers sequence types, timing and per-email copy; for B2B cold outreach use cold-email.\"\ntags: [\"marketing\",\"writing\",\"email\",\"growth\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Femails\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\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\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n\n### 1. One Email, One Job\n- Each email has one primary purpose\n- One main CTA per email\n- Don't try to do everything\n\n### 2. Value Before Ask\n- Lead with usefulness\n- Build trust through content\n- Earn the right to sell\n\n### 3. Relevance Over Volume\n- Fewer, better emails win\n- Segment for relevance\n- Quality > frequency\n\n### 4. Clear Path Forward\n- Every email moves them somewhere\n- Links should do something useful\n- Make next steps obvious\n\n---\n\n## Email Sequence Strategy\n\n### Sequence Length\n- Welcome: 3-7 emails\n- Lead nurture: 5-10 emails\n- Onboarding: 5-10 emails\n- Re-engagement: 3-5 emails\n\nDepends on:\n- Sales cycle length\n- Product complexity\n- 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 ideal\n- Test emoji (they're polarizing)\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\n### Onboarding Emails\n- New users series\n- New customers series\n- Key onboarding step reminders\n- New user invites\n\n### Retention Emails\n- Upgrade to paid\n- Upgrade to higher plan\n- Ask for review\n- Proactive support offers\n- Product usage reports\n- NPS survey\n- Referral program\n\n### Billing Emails\n- Switch to annual\n- Failed payment recovery\n- Cancellation survey\n- Upcoming renewal reminders\n\n### Usage Emails\n- Daily\u002Fweekly\u002Fmonthly summaries\n- Key event notifications\n- Milestone celebrations\n\n### Win-Back Emails\n- Expired trials\n- Cancelled customers\n\n### Campaign Emails\n- Monthly roundup \u002F newsletter\n- Seasonal promotions\n- Product updates\n- Industry news roundup\n- Pricing updates\n\n**For detailed email type reference**: See [references\u002Femail-types.md](references\u002Femail-types.md)\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### 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\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fnitrosend.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **lead-magnets**: For planning lead magnets that feed into nurture sequences\n- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)\n- **onboarding**: For in-app onboarding (email supports this)\n- **copywriting**: For landing pages emails link to\n- **ab-testing**: For testing email elements\n- **popups**: For email capture popups\n- **revops**: For lifecycle stages that trigger email sequences\n","# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\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\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n\n### 1. One Email, One Job\n- Each email has one primary purpose\n- One main CTA per email\n- Don't try to do everything\n\n### 2. Value Before Ask\n- Lead with usefulness\n- Build trust through content\n- Earn the right to sell\n\n### 3. Relevance Over Volume\n- Fewer, better emails win\n- Segment for relevance\n- Quality > frequency\n\n### 4. Clear Path Forward\n- Every email moves them somewhere\n- Links should do something useful\n- Make next steps obvious\n\n---\n\n## Email Sequence Strategy\n\n### Sequence Length\n- Welcome: 3-7 emails\n- Lead nurture: 5-10 emails\n- Onboarding: 5-10 emails\n- Re-engagement: 3-5 emails\n\nDepends on:\n- Sales cycle length\n- Product complexity\n- 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 ideal\n- Test emoji (they're polarizing)\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\n### Onboarding Emails\n- New users series\n- New customers series\n- Key onboarding step reminders\n- New user invites\n\n### Retention Emails\n- Upgrade to paid\n- Upgrade to higher plan\n- Ask for review\n- Proactive support offers\n- Product usage reports\n- NPS survey\n- Referral program\n\n### Billing Emails\n- Switch to annual\n- Failed payment recovery\n- Cancellation survey\n- Upcoming renewal reminders\n\n### Usage Emails\n- Daily\u002Fweekly\u002Fmonthly summaries\n- Key event notifications\n- Milestone celebrations\n\n### Win-Back Emails\n- Expired trials\n- Cancelled customers\n\n### Campaign Emails\n- Monthly roundup \u002F newsletter\n- Seasonal promotions\n- Product updates\n- Industry news roundup\n- Pricing updates\n\n**For detailed email type reference**: See [references\u002Femail-types.md](references\u002Femail-types.md)\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### 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\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fnitrosend.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **lead-magnets**: For planning lead magnets that feed into nurture sequences\n- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)\n- **onboarding**: For in-app onboarding (email supports this)\n- **copywriting**: For landing pages emails link to\n- **ab-testing**: For testing email elements\n- **popups**: For email capture popups\n- **revops**: For lifecycle stages that trigger email sequences\n",{"name":5,"tags":60,"tools":62,"source":63,"license":14,"description":7,"source_path":64,"source_commit":65},[51,47,36,61],"growth",[],"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Femails","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add monoes\u002Fmonomind --skill email-sequences",{"tool":81,"command":82},"bunx","bunx skills add monoes\u002Fmonomind --skill email-sequences",{"tool":84,"command":85},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill email-sequences","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002FSKILL.md",true,[89,94,100,104],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fcopy-guidelines.md","REFERENCE","参考文档",2332,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002Freferences\u002Fcopy-guidelines.md",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Femail-types.md",14250,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002Freferences\u002Femail-types.md",{"path":105,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fsequence-templates.md",3918,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Femail-sequences\u002Freferences\u002Fsequence-templates.md",[109,138,168,195,219,246],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":137},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":151,"publishedAt":137},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[145,148],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":149,"categoryName":150,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[47,152,153,121,154,155,40,156,126,157,158,159,160,161,162,163,164,165,166,167],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":137},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理",[161,179,180,181,182,124,183,40,184,185,186,160,187,188,189,190,191,192,193,194],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":205,"publishedAt":137},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[202],{"categoryNo":203,"categoryName":204,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[126,161,206,207,42,208,124,193,40,209,210,211,212,186,213,214,215,216,217,218],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":231,"publishedAt":137},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[232,233,234,235,42,236,237,238,239,125,240,241,242,126,129,213,243,244,245,215],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":253,"publishedAt":137},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[252],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},[234,254,255,256,257,258,259,42,260,261,157,262,263,264,129,213,265,266,215,267],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]