[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AFS1MSNGFQMA2BE8MRPP0":3,"skill-same:01M71AFS1MSNGFQMA2BE8MRPP0":80},{"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":31,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71AFS1MSNGFQMA2BE8MRPP0","email-marketing",null,"When the user wants to plan email marketing, EDM, newsletter strategy, or email deliverability. Also use when the user mentions \"email marketing\", \"EDM\", \"newsletter\" or \"SPF\". For signup UI, use newsletter-signup-generator.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fchannels\u002Fowned\u002Femail-marketing\u002FSKILL.md",[18,23,26],{"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","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"marketing","Email Marketing","email","user","ui","signup","spf","newsletter","email deliverability","to plan","plan","generator","when","use","strategy","deliverability","for","2026-11-10 10:12:30",false,"---\nname: email-marketing\ndescription: When the user wants to plan email marketing, EDM, newsletter strategy, or email deliverability. Also use when the user mentions \"email marketing\", \"EDM\", \"newsletter\" or \"SPF\". For signup UI, use newsletter-signup-generator.\nmetadata:\n  version: 1.0.1\n---\n\n# Channels: Email Marketing\n\nGuides email marketing strategy for AI\u002FSaaS products. Email ROI ~$36 per dollar spent; open\u002Fclick rates typically higher than social. Covers EDM vs Newsletter, five content types, deliverability (SPF\u002FDKIM\u002FDMARC), and SEO synergy via article delivery.\n\n**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for audience and content strategy. See **content-marketing** for content types and formats across channels.\n\nIdentify:\n1. **Goal**: Retention, conversion, brand reach, or SEO synergy\n2. **Content mix**: Onboarding, campaign, announcement, features, newsletter\n3. **List size**: Bulk sender rules (5,000+\u002Fday) require Gmail\u002FYahoo compliance\n\n## EDM vs Newsletter\n\n| Type | Purpose | Use |\n|------|---------|-----|\n| **EDM** | Direct marketing; conversion-focused | Promotions, campaigns, announcements; bulk sends |\n| **Newsletter** | Ongoing value; relationship | Industry insights, curated articles; regular cadence |\n\n**Combine both**: EDM for push; Newsletter for nurture. Cover different stages and goals.\n\n## Five Content Types\n\n| Type | Use |\n|------|-----|\n| **Onboarding** | Welcome + first-use guidance; 5-7 day sequence; behavior-triggered; drive \"Aha!\" moment |\n| **Campaign** | Promotions, limited-time; conversion or participation |\n| **Announcement** | Product launch, major update; one-time important notice |\n| **Features update** | New features, improvements; help users adopt |\n| **Blog\u002FNewsletter** | Curated articles, industry insights; sustained touch |\n\n## User Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Personalization** | Segment by behavior, source, stage; boosts open\u002Fclick |\n| **Timing** | New users: dense; existing: controlled pace; behavior-triggered > calendar-only |\n| **Welcome series** | Send soon after signup; 5-7 emails over days; guide first key action |\n| **Unsubscribe** | One-click required (Gmail\u002FYahoo); honor within 48h; clear entry |\n| **Complaint rate** | Keep below 0.3%; list hygiene critical |\n\n## Content Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Subject** | One clear topic per email; avoid pure promo |\n| **Value first** | Useful info before promotion |\n| **CTA** | Single primary CTA; clear next step |\n| **Mobile** | 50%+ read on mobile; responsive layout, tappable links |\n\n## Deliverability & Domain Config\n\n**Subdomain**: Use subdomain (e.g. mail.example.com) for marketing; keep transactional (support@, etc.) on main domain. Isolate risk.\n\n### SPF, DKIM, DMARC\n\n| Protocol | Purpose |\n|----------|---------|\n| **SPF** | Authorizes mail servers for domain |\n| **DKIM** | Cryptographic signature; verifies sender |\n| **DMARC** | Policy for unauthenticated mail; start p=none, then quarantine, then reject over 60-90 days |\n\n**Order**: SPF first, then DKIM, then DMARC. Gmail\u002FYahoo require all three for bulk senders (5,000+\u002Fday) since Feb 2024.\n\n**Advanced**: TLS-RPT, MTA-STS, BIMI (brand logo). **Postmaster Tools**: Monitor deliverability, spam rate, auth status.\n\n## Delivery Strategy: Articles + SEO Synergy\n\n| Article Type | Use |\n|--------------|-----|\n| **Retention** | Deep content for existing users; improve retention |\n| **ToFu** | Top of funnel; awareness (trends, concepts, problem framing) |\n| **MoFu** | Middle of funnel; consideration (comparisons, reviews, best practices) |\n\n**Dual value**: (1) Better email engagement (open, click, stickiness); (2) Drive traffic to article pages from non-search channel; signals to Google that users value content; supports SEO.\n\n**Measurement**: GA4 email source traffic to article pages; GSC rank\u002Fclick changes.\n\n## Planning Framework\n\n1. **Content mix**: Allocate onboarding, campaign, announcement, features, newsletter\n2. **Select articles**: Pick retention, ToFu, MoFu from blog; prioritize SEO target pages\n3. **Cadence**: Stable frequency (weekly\u002Fbiweekly\u002Fmonthly); avoid over-sending\n4. **Monitor**: Open rate, click rate; GA4 email contribution to article traffic; GSC\n\n## Frequency\n\n| Guideline | Note |\n|-----------|------|\n| **Baseline** | 1 high-value email\u002Fweek for most brands |\n| **Peak times** | Tue-Thu, 8-11am or 2-4pm (recipient timezone) |\n| **Segmentation** | New vs loyal need different cadence |\n| **Quality** | Relevant, behavior-triggered > calendar volume |\n\n**Data**: ~36% send 1-3\u002Fmonth; ~30% weekly; daily risks high unsubscribe.\n\n## Output Format\n\n- **Content mix** (five types)\n- **EDM vs Newsletter** balance\n- **Deliverability** (subdomain, SPF\u002FDKIM\u002FDMARC)\n- **Article delivery** (Retention, ToFu, MoFu, SEO targets)\n- **Cadence** and frequency\n- **KPI** (open, click, GA4 email traffic, GSC)\n\n## Related Skills\n\n- **content-marketing**: Content types, formats; email as channel in repurposing matrix\n- **newsletter-signup-generator**: Signup form design\n- **traffic-analysis**: Email source attribution, UTM\n- **analytics-tracking**: Email click tracking\n- **content-strategy**: Article selection for email delivery\n- **integrated-marketing**: Email as owned media channel\n","# Channels: Email Marketing\n\nGuides email marketing strategy for AI\u002FSaaS products. Email ROI ~$36 per dollar spent; open\u002Fclick rates typically higher than social. Covers EDM vs Newsletter, five content types, deliverability (SPF\u002FDKIM\u002FDMARC), and SEO synergy via article delivery.\n\n**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for audience and content strategy. See **content-marketing** for content types and formats across channels.\n\nIdentify:\n1. **Goal**: Retention, conversion, brand reach, or SEO synergy\n2. **Content mix**: Onboarding, campaign, announcement, features, newsletter\n3. **List size**: Bulk sender rules (5,000+\u002Fday) require Gmail\u002FYahoo compliance\n\n## EDM vs Newsletter\n\n| Type | Purpose | Use |\n|------|---------|-----|\n| **EDM** | Direct marketing; conversion-focused | Promotions, campaigns, announcements; bulk sends |\n| **Newsletter** | Ongoing value; relationship | Industry insights, curated articles; regular cadence |\n\n**Combine both**: EDM for push; Newsletter for nurture. Cover different stages and goals.\n\n## Five Content Types\n\n| Type | Use |\n|------|-----|\n| **Onboarding** | Welcome + first-use guidance; 5-7 day sequence; behavior-triggered; drive \"Aha!\" moment |\n| **Campaign** | Promotions, limited-time; conversion or participation |\n| **Announcement** | Product launch, major update; one-time important notice |\n| **Features update** | New features, improvements; help users adopt |\n| **Blog\u002FNewsletter** | Curated articles, industry insights; sustained touch |\n\n## User Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Personalization** | Segment by behavior, source, stage; boosts open\u002Fclick |\n| **Timing** | New users: dense; existing: controlled pace; behavior-triggered > calendar-only |\n| **Welcome series** | Send soon after signup; 5-7 emails over days; guide first key action |\n| **Unsubscribe** | One-click required (Gmail\u002FYahoo); honor within 48h; clear entry |\n| **Complaint rate** | Keep below 0.3%; list hygiene critical |\n\n## Content Best Practices\n\n| Practice | Guideline |\n|----------|-----------|\n| **Subject** | One clear topic per email; avoid pure promo |\n| **Value first** | Useful info before promotion |\n| **CTA** | Single primary CTA; clear next step |\n| **Mobile** | 50%+ read on mobile; responsive layout, tappable links |\n\n## Deliverability & Domain Config\n\n**Subdomain**: Use subdomain (e.g. mail.example.com) for marketing; keep transactional (support@, etc.) on main domain. Isolate risk.\n\n### SPF, DKIM, DMARC\n\n| Protocol | Purpose |\n|----------|---------|\n| **SPF** | Authorizes mail servers for domain |\n| **DKIM** | Cryptographic signature; verifies sender |\n| **DMARC** | Policy for unauthenticated mail; start p=none, then quarantine, then reject over 60-90 days |\n\n**Order**: SPF first, then DKIM, then DMARC. Gmail\u002FYahoo require all three for bulk senders (5,000+\u002Fday) since Feb 2024.\n\n**Advanced**: TLS-RPT, MTA-STS, BIMI (brand logo). **Postmaster Tools**: Monitor deliverability, spam rate, auth status.\n\n## Delivery Strategy: Articles + SEO Synergy\n\n| Article Type | Use |\n|--------------|-----|\n| **Retention** | Deep content for existing users; improve retention |\n| **ToFu** | Top of funnel; awareness (trends, concepts, problem framing) |\n| **MoFu** | Middle of funnel; consideration (comparisons, reviews, best practices) |\n\n**Dual value**: (1) Better email engagement (open, click, stickiness); (2) Drive traffic to article pages from non-search channel; signals to Google that users value content; supports SEO.\n\n**Measurement**: GA4 email source traffic to article pages; GSC rank\u002Fclick changes.\n\n## Planning Framework\n\n1. **Content mix**: Allocate onboarding, campaign, announcement, features, newsletter\n2. **Select articles**: Pick retention, ToFu, MoFu from blog; prioritize SEO target pages\n3. **Cadence**: Stable frequency (weekly\u002Fbiweekly\u002Fmonthly); avoid over-sending\n4. **Monitor**: Open rate, click rate; GA4 email contribution to article traffic; GSC\n\n## Frequency\n\n| Guideline | Note |\n|-----------|------|\n| **Baseline** | 1 high-value email\u002Fweek for most brands |\n| **Peak times** | Tue-Thu, 8-11am or 2-4pm (recipient timezone) |\n| **Segmentation** | New vs loyal need different cadence |\n| **Quality** | Relevant, behavior-triggered > calendar volume |\n\n**Data**: ~36% send 1-3\u002Fmonth; ~30% weekly; daily risks high unsubscribe.\n\n## Output Format\n\n- **Content mix** (five types)\n- **EDM vs Newsletter** balance\n- **Deliverability** (subdomain, SPF\u002FDKIM\u002FDMARC)\n- **Article delivery** (Retention, ToFu, MoFu, SEO targets)\n- **Cadence** and frequency\n- **KPI** (open, click, GA4 email traffic, GSC)\n\n## Related Skills\n\n- **content-marketing**: Content types, formats; email as channel in repurposing matrix\n- **newsletter-signup-generator**: Signup form design\n- **traffic-analysis**: Email source attribution, UTM\n- **analytics-tracking**: Email click tracking\n- **content-strategy**: Article selection for email delivery\n- **integrated-marketing**: Email as owned media channel\n",{"name":5,"metadata":54,"description":7},{"version":55},"1.0.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fchannels\u002Fowned\u002Femail-marketing",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ariadoss\u002Fsuperskills --skill email-marketing",{"tool":72,"command":73},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill email-marketing",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill email-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fchannels\u002Fowned\u002Femail-marketing\u002FSKILL.md",true,[],[81,105,128,147,176,192],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":49},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[83,35,91,92,93,94,95,96,97,44,98,99,100,101,102,45,103,104],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":49},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[112,42,93,113,114,115,116,117,118,44,119,120,121,122,123,48,124,125,126,127],"write plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":49},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[130,135,136,137,45,138,139,140,141,142,143,114,144,44,145,146],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":49},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[157,158,159,160,161,162,163,164,165,44,166,167,168,169,170,171,172,173,174,175],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":49},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[178,122,183,184,143,114,185,186,44,187,45,188,189,190,191],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":49},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[199,200,201,202,203,204,205,44,206,45,207],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]