[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-email-sequence":3,"mdc--bd06vm-key":37,"related-repo-anthropic-email-sequence":1085,"related-org-anthropic-email-sequence":1202},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"email-sequence","design multi-email marketing sequences","Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A\u002FB test suggestions, or when mapping a sequence end-to-end with a flow diagram.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20,23],{"name":14,"slug":15,"type":16},"Marketing","marketing","tag",{"name":18,"slug":19,"type":16},"Campaign Planning","campaign-planning",{"name":21,"slug":22,"type":16},"Email","email",{"name":24,"slug":25,"type":16},"Email Marketing","email-marketing",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-04-06T17:58:23.376957",null,2736,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002FHEAD\u002Fmarketing\u002Fskills\u002Femail-sequence","---\nname: email-sequence\ndescription: Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A\u002FB test suggestions, or when mapping a sequence end-to-end with a flow diagram.\nargument-hint: \"[sequence type]\"\n---\n\n# Email Sequence\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nDesign and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.\n\n## Trigger\n\nUser runs `\u002Femail-sequence` or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.\n\n## Inputs\n\nGather the following from the user. If not provided, ask before proceeding:\n\n1. **Sequence type** — one of:\n   - Onboarding\n   - Lead nurture\n   - Re-engagement\n   - Product launch\n   - Event follow-up\n   - Upgrade\u002Fupsell\n   - Win-back\n   - Educational drip\n\n2. **Goal** — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)\n\n3. **Audience** — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)\n\n4. **Number of emails** (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below\n\n5. **Timing\u002Fcadence preferences** (optional) — desired spacing between emails (e.g., \"every 3 days\", \"weekly\", \"aggressive first week then taper off\")\n\n6. **Brand voice** — if configured in local settings, apply automatically and inform the user. If not configured, ask: \"Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone.\"\n\n7. **Additional context** (optional):\n   - Specific offers, discounts, or incentives to include\n   - CTAs or landing pages to link to\n   - Content assets available (blog posts, case studies, videos, guides)\n   - Product features to highlight\n   - Competitor differentiators to reference\n\n## Process\n\n### 1. Sequence Strategy\n\nBefore drafting any emails, define the overall sequence architecture:\n\n- **Narrative arc** — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last?\n- **Journey mapping** — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion)\n- **Escalation logic** — how does the intensity, urgency, or value of each email build on the previous one?\n- **Success definition** — what specific action signals that the sequence has done its job and the recipient should exit?\n\n### 2. Individual Email Design\n\nFor each email in the sequence, produce:\n\n#### Subject Line\n- Provide 2-3 options per email\n- Vary approaches: curiosity, benefit-driven, urgency, personalization, question-based\n- Keep under 50 characters where possible; note preview behavior on mobile\n\n#### Preview Text\n- 40-90 characters that complement (not repeat) the subject line\n- Should add context or intrigue that increases open likelihood\n\n#### Email Purpose\n- One sentence explaining why this email exists and what it moves the recipient toward\n\n#### Body Copy\n- Full draft ready to use\n- Clear hierarchy: hook, body, CTA\n- Short paragraphs (2-3 sentences max)\n- Scannable formatting with bold key phrases where appropriate\n- Personalization tokens where relevant (e.g., first name, company name, product used)\n\n#### Primary CTA\n- Button text and destination\n- One primary CTA per email (secondary CTA only if appropriate for the sequence stage)\n\n#### Timing\n- Days after the trigger event or after the previous email\n- Note if timing should adjust based on engagement (e.g., \"send sooner if they opened but did not click\")\n\n#### Segment\u002FCondition Notes\n- Who receives this email vs. who skips it\n- Any behavioral or attribute-based conditions (e.g., \"only send to users who have not completed setup\")\n\n### 3. Sequence Logic\n\nDefine the flow control for the sequence:\n\n- **Branching conditions** — alternate paths based on engagement. For example:\n  - \"If opened email 2 but did not click CTA, send email 2b (softer re-ask) instead of email 3\"\n  - \"If clicked CTA in email 1, skip email 2 and go directly to email 3\"\n- **Exit conditions** — when a recipient converts (completes the desired action), remove them from the sequence. Define what \"conversion\" means for this sequence.\n- **Re-entry rules** — can someone re-enter the sequence? Under what conditions? (e.g., \"if a user churns again 90 days later, re-enter the win-back sequence\")\n- **Suppression rules** — do not send if the recipient is already in another active sequence, has unsubscribed from marketing, or has contacted support in the last 48 hours\n\n### 4. Performance Benchmarks\n\nProvide expected benchmarks based on the sequence type so the user can set targets:\n\n| Metric | Onboarding | Lead Nurture | Re-engagement | Win-back |\n|--------|-----------|--------------|---------------|----------|\n| Open rate | 50-70% | 20-30% | 15-25% | 15-20% |\n| Click-through rate | 10-20% | 3-7% | 2-5% | 2-4% |\n| Conversion rate | 15-30% | 2-5% | 3-8% | 1-3% |\n| Unsubscribe rate | \u003C0.5% | \u003C0.5% | 1-2% | 1-3% |\n\nAdjust benchmarks based on industry and audience if the user has provided that context.\n\n## Sequence Type Templates\n\nUse these as starting frameworks. Adapt length and content based on the user's goal and audience.\n\n**Onboarding (5-7 emails over 14-21 days):**\nWelcome and set expectations -- Quick win to demonstrate value -- Core feature deep dive -- Advanced feature or integration -- Social proof and community -- Check-in and feedback request -- Upgrade prompt or next steps\n\n**Lead Nurture (4-6 emails over 3-4 weeks):**\nValue-first educational content -- Pain point identification -- Solution positioning with proof -- Social proof and results -- Soft CTA (trial, demo, resource) -- Direct CTA (buy, book, sign up)\n\n**Re-engagement (3-4 emails over 10-14 days):**\n\"We miss you\" with a compelling reason to return -- Value reminder highlighting what they are missing -- Incentive or exclusive offer -- Last chance with clear deadline\n\n**Win-back (3-5 emails over 30 days):**\nFriendly check-in asking what went wrong -- What is new since they left -- Special offer or incentive to return -- Feedback request (even if they do not come back) -- Final goodbye with door open\n\n**Product Launch (4-6 emails over 2-3 weeks):**\nTeaser or pre-announcement -- Launch announcement with full details -- Feature spotlight or use case -- Social proof and early results -- Limited-time offer or bonus -- Last chance or reminder\n\n**Event Follow-up (3-4 emails over 7-10 days):**\nThank you with key takeaways or recordings -- Resource roundup from the event -- Related offer or next step -- Feedback survey\n\n**Upgrade\u002FUpsell (3-5 emails over 2-3 weeks):**\nUsage milestone or success celebration -- Feature gap or limitation they are hitting -- Upgrade benefits with proof -- Limited-time incentive -- Direct comparison of plans\n\n**Educational Drip (5-8 emails over 4-6 weeks):**\nIntroduction and what they will learn -- Lesson 1: foundational concept -- Lesson 2: intermediate concept -- Lesson 3: advanced concept -- Practical application or exercise -- Resource roundup -- Graduation and next steps\n\n## Tool Integration\n\n### If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io)\n- Reference how to set up the sequence as a flow or automation in the platform\n- Note any platform-specific features to use (e.g., smart send time, conditional splits, A\u002FB testing)\n- Map the branching logic to the platform's visual flow builder concepts\n\n### If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo)\n- Reference lead scoring data to inform segmentation and exit conditions\n- Use lifecycle stage data to tailor messaging per segment\n- Note how to set enrollment triggers based on CRM properties or list membership\n\n### If no tools are connected\n- Deliver all email content in copy-paste-ready format\n- Include a setup checklist the user can follow in any email platform:\n  1. Create the automation or flow\n  2. Set the enrollment trigger\n  3. Add each email with the specified delays\n  4. Configure branching and exit conditions\n  5. Set up tracking for the recommended metrics\n\n## Output\n\nPresent the complete sequence with the following sections:\n\n### Sequence Overview Table\n\n| # | Subject Line | Purpose | Timing | Primary CTA | Condition |\n|---|-------------|---------|--------|-------------|-----------|\n\n### Full Email Drafts\nEach email with subject line options, preview text, purpose, body copy, CTA, timing, and segment notes.\n\n### Sequence Flow Diagram\nA text-based diagram showing the email flow, branching paths, and exit points. Use a clear format such as:\n\n```\n[Trigger] --> Email 1 (Day 0)\n                |\n          Opened? --Yes--> Email 2 (Day 3)\n                |              |\n                No        Clicked CTA? --Yes--> [EXIT: Converted]\n                |              |\n                v              No\n          Email 1b (Day 2)     |\n                |              v\n                +--------> Email 3 (Day 7)\n                               |\n                               v\n                          Email 4 (Day 10)\n                               |\n                          [EXIT: Sequence complete]\n```\n\n### Branching Logic Notes\nSummary of all conditions, exits, and suppressions in a reference list.\n\n### A\u002FB Test Suggestions\n- 2-3 recommended A\u002FB tests (subject lines, CTA text, send time, email length)\n- What to test, how to split, and how to measure the winner\n\n### Metrics to Track\n- Primary conversion metric for the sequence\n- Per-email metrics: open rate, CTR, unsubscribe rate\n- Sequence-level metrics: overall conversion rate, time to conversion, drop-off points\n- Recommended review cadence (e.g., \"Review performance weekly for the first month, then monthly\")\n\n## After the Sequence\n\nAsk: \"Would you like me to:\n- Revise the copy or tone for any specific email?\n- Add a branching path for a specific scenario?\n- Create a variation of this sequence for a different audience segment?\n- Draft the A\u002FB test variants for the subject lines?\n- Build a companion sequence (e.g., a post-purchase follow-up after this lead nurture converts)?\"\n",{"data":38,"body":40},{"name":4,"description":6,"argument-hint":39},"[sequence type]",{"type":41,"children":42},"root",[43,51,70,75,82,96,102,107,255,261,268,273,316,322,327,334,352,358,371,377,385,391,419,425,438,444,457,463,476,482,487,543,549,554,703,708,714,719,729,739,749,759,769,779,789,799,805,811,829,835,853,859,900,906,911,917,953,959,964,970,975,987,993,998,1004,1017,1023,1046,1052,1057],{"type":44,"tag":45,"props":46,"children":47},"element","h1",{"id":4},[48],{"type":49,"value":50},"text","Email Sequence",{"type":44,"tag":52,"props":53,"children":54},"blockquote",{},[55],{"type":44,"tag":56,"props":57,"children":58},"p",{},[59,61,68],{"type":49,"value":60},"If you see unfamiliar placeholders or need to check which tools are connected, see ",{"type":44,"tag":62,"props":63,"children":65},"a",{"href":64},"..\u002F..\u002FCONNECTORS.md",[66],{"type":49,"value":67},"CONNECTORS.md",{"type":49,"value":69},".",{"type":44,"tag":56,"props":71,"children":72},{},[73],{"type":49,"value":74},"Design and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.",{"type":44,"tag":76,"props":77,"children":79},"h2",{"id":78},"trigger",[80],{"type":49,"value":81},"Trigger",{"type":44,"tag":56,"props":83,"children":84},{},[85,87,94],{"type":49,"value":86},"User runs ",{"type":44,"tag":88,"props":89,"children":91},"code",{"className":90},[],[92],{"type":49,"value":93},"\u002Femail-sequence",{"type":49,"value":95}," or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.",{"type":44,"tag":76,"props":97,"children":99},{"id":98},"inputs",[100],{"type":49,"value":101},"Inputs",{"type":44,"tag":56,"props":103,"children":104},{},[105],{"type":49,"value":106},"Gather the following from the user. If not provided, ask before proceeding:",{"type":44,"tag":108,"props":109,"children":110},"ol",{},[111,167,177,187,197,207,217],{"type":44,"tag":112,"props":113,"children":114},"li",{},[115,121,123],{"type":44,"tag":116,"props":117,"children":118},"strong",{},[119],{"type":49,"value":120},"Sequence type",{"type":49,"value":122}," — one of:",{"type":44,"tag":124,"props":125,"children":126},"ul",{},[127,132,137,142,147,152,157,162],{"type":44,"tag":112,"props":128,"children":129},{},[130],{"type":49,"value":131},"Onboarding",{"type":44,"tag":112,"props":133,"children":134},{},[135],{"type":49,"value":136},"Lead nurture",{"type":44,"tag":112,"props":138,"children":139},{},[140],{"type":49,"value":141},"Re-engagement",{"type":44,"tag":112,"props":143,"children":144},{},[145],{"type":49,"value":146},"Product launch",{"type":44,"tag":112,"props":148,"children":149},{},[150],{"type":49,"value":151},"Event follow-up",{"type":44,"tag":112,"props":153,"children":154},{},[155],{"type":49,"value":156},"Upgrade\u002Fupsell",{"type":44,"tag":112,"props":158,"children":159},{},[160],{"type":49,"value":161},"Win-back",{"type":44,"tag":112,"props":163,"children":164},{},[165],{"type":49,"value":166},"Educational drip",{"type":44,"tag":112,"props":168,"children":169},{},[170,175],{"type":44,"tag":116,"props":171,"children":172},{},[173],{"type":49,"value":174},"Goal",{"type":49,"value":176}," — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)",{"type":44,"tag":112,"props":178,"children":179},{},[180,185],{"type":44,"tag":116,"props":181,"children":182},{},[183],{"type":49,"value":184},"Audience",{"type":49,"value":186}," — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)",{"type":44,"tag":112,"props":188,"children":189},{},[190,195],{"type":44,"tag":116,"props":191,"children":192},{},[193],{"type":49,"value":194},"Number of emails",{"type":49,"value":196}," (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below",{"type":44,"tag":112,"props":198,"children":199},{},[200,205],{"type":44,"tag":116,"props":201,"children":202},{},[203],{"type":49,"value":204},"Timing\u002Fcadence preferences",{"type":49,"value":206}," (optional) — desired spacing between emails (e.g., \"every 3 days\", \"weekly\", \"aggressive first week then taper off\")",{"type":44,"tag":112,"props":208,"children":209},{},[210,215],{"type":44,"tag":116,"props":211,"children":212},{},[213],{"type":49,"value":214},"Brand voice",{"type":49,"value":216}," — if configured in local settings, apply automatically and inform the user. If not configured, ask: \"Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone.\"",{"type":44,"tag":112,"props":218,"children":219},{},[220,225,227],{"type":44,"tag":116,"props":221,"children":222},{},[223],{"type":49,"value":224},"Additional context",{"type":49,"value":226}," (optional):",{"type":44,"tag":124,"props":228,"children":229},{},[230,235,240,245,250],{"type":44,"tag":112,"props":231,"children":232},{},[233],{"type":49,"value":234},"Specific offers, discounts, or incentives to include",{"type":44,"tag":112,"props":236,"children":237},{},[238],{"type":49,"value":239},"CTAs or landing pages to link to",{"type":44,"tag":112,"props":241,"children":242},{},[243],{"type":49,"value":244},"Content assets available (blog posts, case studies, videos, guides)",{"type":44,"tag":112,"props":246,"children":247},{},[248],{"type":49,"value":249},"Product features to highlight",{"type":44,"tag":112,"props":251,"children":252},{},[253],{"type":49,"value":254},"Competitor differentiators to reference",{"type":44,"tag":76,"props":256,"children":258},{"id":257},"process",[259],{"type":49,"value":260},"Process",{"type":44,"tag":262,"props":263,"children":265},"h3",{"id":264},"_1-sequence-strategy",[266],{"type":49,"value":267},"1. Sequence Strategy",{"type":44,"tag":56,"props":269,"children":270},{},[271],{"type":49,"value":272},"Before drafting any emails, define the overall sequence architecture:",{"type":44,"tag":124,"props":274,"children":275},{},[276,286,296,306],{"type":44,"tag":112,"props":277,"children":278},{},[279,284],{"type":44,"tag":116,"props":280,"children":281},{},[282],{"type":49,"value":283},"Narrative arc",{"type":49,"value":285}," — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last?",{"type":44,"tag":112,"props":287,"children":288},{},[289,294],{"type":44,"tag":116,"props":290,"children":291},{},[292],{"type":49,"value":293},"Journey mapping",{"type":49,"value":295}," — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion)",{"type":44,"tag":112,"props":297,"children":298},{},[299,304],{"type":44,"tag":116,"props":300,"children":301},{},[302],{"type":49,"value":303},"Escalation logic",{"type":49,"value":305}," — how does the intensity, urgency, or value of each email build on the previous one?",{"type":44,"tag":112,"props":307,"children":308},{},[309,314],{"type":44,"tag":116,"props":310,"children":311},{},[312],{"type":49,"value":313},"Success definition",{"type":49,"value":315}," — what specific action signals that the sequence has done its job and the recipient should exit?",{"type":44,"tag":262,"props":317,"children":319},{"id":318},"_2-individual-email-design",[320],{"type":49,"value":321},"2. Individual Email Design",{"type":44,"tag":56,"props":323,"children":324},{},[325],{"type":49,"value":326},"For each email in the sequence, produce:",{"type":44,"tag":328,"props":329,"children":331},"h4",{"id":330},"subject-line",[332],{"type":49,"value":333},"Subject Line",{"type":44,"tag":124,"props":335,"children":336},{},[337,342,347],{"type":44,"tag":112,"props":338,"children":339},{},[340],{"type":49,"value":341},"Provide 2-3 options per email",{"type":44,"tag":112,"props":343,"children":344},{},[345],{"type":49,"value":346},"Vary approaches: curiosity, benefit-driven, urgency, personalization, question-based",{"type":44,"tag":112,"props":348,"children":349},{},[350],{"type":49,"value":351},"Keep under 50 characters where possible; note preview behavior on mobile",{"type":44,"tag":328,"props":353,"children":355},{"id":354},"preview-text",[356],{"type":49,"value":357},"Preview Text",{"type":44,"tag":124,"props":359,"children":360},{},[361,366],{"type":44,"tag":112,"props":362,"children":363},{},[364],{"type":49,"value":365},"40-90 characters that complement (not repeat) the subject line",{"type":44,"tag":112,"props":367,"children":368},{},[369],{"type":49,"value":370},"Should add context or intrigue that increases open likelihood",{"type":44,"tag":328,"props":372,"children":374},{"id":373},"email-purpose",[375],{"type":49,"value":376},"Email Purpose",{"type":44,"tag":124,"props":378,"children":379},{},[380],{"type":44,"tag":112,"props":381,"children":382},{},[383],{"type":49,"value":384},"One sentence explaining why this email exists and what it moves the recipient toward",{"type":44,"tag":328,"props":386,"children":388},{"id":387},"body-copy",[389],{"type":49,"value":390},"Body Copy",{"type":44,"tag":124,"props":392,"children":393},{},[394,399,404,409,414],{"type":44,"tag":112,"props":395,"children":396},{},[397],{"type":49,"value":398},"Full draft ready to use",{"type":44,"tag":112,"props":400,"children":401},{},[402],{"type":49,"value":403},"Clear hierarchy: hook, body, CTA",{"type":44,"tag":112,"props":405,"children":406},{},[407],{"type":49,"value":408},"Short paragraphs (2-3 sentences max)",{"type":44,"tag":112,"props":410,"children":411},{},[412],{"type":49,"value":413},"Scannable formatting with bold key phrases where appropriate",{"type":44,"tag":112,"props":415,"children":416},{},[417],{"type":49,"value":418},"Personalization tokens where relevant (e.g., first name, company name, product used)",{"type":44,"tag":328,"props":420,"children":422},{"id":421},"primary-cta",[423],{"type":49,"value":424},"Primary CTA",{"type":44,"tag":124,"props":426,"children":427},{},[428,433],{"type":44,"tag":112,"props":429,"children":430},{},[431],{"type":49,"value":432},"Button text and destination",{"type":44,"tag":112,"props":434,"children":435},{},[436],{"type":49,"value":437},"One primary CTA per email (secondary CTA only if appropriate for the sequence stage)",{"type":44,"tag":328,"props":439,"children":441},{"id":440},"timing",[442],{"type":49,"value":443},"Timing",{"type":44,"tag":124,"props":445,"children":446},{},[447,452],{"type":44,"tag":112,"props":448,"children":449},{},[450],{"type":49,"value":451},"Days after the trigger event or after the previous email",{"type":44,"tag":112,"props":453,"children":454},{},[455],{"type":49,"value":456},"Note if timing should adjust based on engagement (e.g., \"send sooner if they opened but did not click\")",{"type":44,"tag":328,"props":458,"children":460},{"id":459},"segmentcondition-notes",[461],{"type":49,"value":462},"Segment\u002FCondition Notes",{"type":44,"tag":124,"props":464,"children":465},{},[466,471],{"type":44,"tag":112,"props":467,"children":468},{},[469],{"type":49,"value":470},"Who receives this email vs. who skips it",{"type":44,"tag":112,"props":472,"children":473},{},[474],{"type":49,"value":475},"Any behavioral or attribute-based conditions (e.g., \"only send to users who have not completed setup\")",{"type":44,"tag":262,"props":477,"children":479},{"id":478},"_3-sequence-logic",[480],{"type":49,"value":481},"3. Sequence Logic",{"type":44,"tag":56,"props":483,"children":484},{},[485],{"type":49,"value":486},"Define the flow control for the sequence:",{"type":44,"tag":124,"props":488,"children":489},{},[490,513,523,533],{"type":44,"tag":112,"props":491,"children":492},{},[493,498,500],{"type":44,"tag":116,"props":494,"children":495},{},[496],{"type":49,"value":497},"Branching conditions",{"type":49,"value":499}," — alternate paths based on engagement. For example:\n",{"type":44,"tag":124,"props":501,"children":502},{},[503,508],{"type":44,"tag":112,"props":504,"children":505},{},[506],{"type":49,"value":507},"\"If opened email 2 but did not click CTA, send email 2b (softer re-ask) instead of email 3\"",{"type":44,"tag":112,"props":509,"children":510},{},[511],{"type":49,"value":512},"\"If clicked CTA in email 1, skip email 2 and go directly to email 3\"",{"type":44,"tag":112,"props":514,"children":515},{},[516,521],{"type":44,"tag":116,"props":517,"children":518},{},[519],{"type":49,"value":520},"Exit conditions",{"type":49,"value":522}," — when a recipient converts (completes the desired action), remove them from the sequence. Define what \"conversion\" means for this sequence.",{"type":44,"tag":112,"props":524,"children":525},{},[526,531],{"type":44,"tag":116,"props":527,"children":528},{},[529],{"type":49,"value":530},"Re-entry rules",{"type":49,"value":532}," — can someone re-enter the sequence? Under what conditions? (e.g., \"if a user churns again 90 days later, re-enter the win-back sequence\")",{"type":44,"tag":112,"props":534,"children":535},{},[536,541],{"type":44,"tag":116,"props":537,"children":538},{},[539],{"type":49,"value":540},"Suppression rules",{"type":49,"value":542}," — do not send if the recipient is already in another active sequence, has unsubscribed from marketing, or has contacted support in the last 48 hours",{"type":44,"tag":262,"props":544,"children":546},{"id":545},"_4-performance-benchmarks",[547],{"type":49,"value":548},"4. Performance Benchmarks",{"type":44,"tag":56,"props":550,"children":551},{},[552],{"type":49,"value":553},"Provide expected benchmarks based on the sequence type so the user can set targets:",{"type":44,"tag":555,"props":556,"children":557},"table",{},[558,589],{"type":44,"tag":559,"props":560,"children":561},"thead",{},[562],{"type":44,"tag":563,"props":564,"children":565},"tr",{},[566,572,576,581,585],{"type":44,"tag":567,"props":568,"children":569},"th",{},[570],{"type":49,"value":571},"Metric",{"type":44,"tag":567,"props":573,"children":574},{},[575],{"type":49,"value":131},{"type":44,"tag":567,"props":577,"children":578},{},[579],{"type":49,"value":580},"Lead Nurture",{"type":44,"tag":567,"props":582,"children":583},{},[584],{"type":49,"value":141},{"type":44,"tag":567,"props":586,"children":587},{},[588],{"type":49,"value":161},{"type":44,"tag":590,"props":591,"children":592},"tbody",{},[593,622,650,677],{"type":44,"tag":563,"props":594,"children":595},{},[596,602,607,612,617],{"type":44,"tag":597,"props":598,"children":599},"td",{},[600],{"type":49,"value":601},"Open rate",{"type":44,"tag":597,"props":603,"children":604},{},[605],{"type":49,"value":606},"50-70%",{"type":44,"tag":597,"props":608,"children":609},{},[610],{"type":49,"value":611},"20-30%",{"type":44,"tag":597,"props":613,"children":614},{},[615],{"type":49,"value":616},"15-25%",{"type":44,"tag":597,"props":618,"children":619},{},[620],{"type":49,"value":621},"15-20%",{"type":44,"tag":563,"props":623,"children":624},{},[625,630,635,640,645],{"type":44,"tag":597,"props":626,"children":627},{},[628],{"type":49,"value":629},"Click-through rate",{"type":44,"tag":597,"props":631,"children":632},{},[633],{"type":49,"value":634},"10-20%",{"type":44,"tag":597,"props":636,"children":637},{},[638],{"type":49,"value":639},"3-7%",{"type":44,"tag":597,"props":641,"children":642},{},[643],{"type":49,"value":644},"2-5%",{"type":44,"tag":597,"props":646,"children":647},{},[648],{"type":49,"value":649},"2-4%",{"type":44,"tag":563,"props":651,"children":652},{},[653,658,663,667,672],{"type":44,"tag":597,"props":654,"children":655},{},[656],{"type":49,"value":657},"Conversion rate",{"type":44,"tag":597,"props":659,"children":660},{},[661],{"type":49,"value":662},"15-30%",{"type":44,"tag":597,"props":664,"children":665},{},[666],{"type":49,"value":644},{"type":44,"tag":597,"props":668,"children":669},{},[670],{"type":49,"value":671},"3-8%",{"type":44,"tag":597,"props":673,"children":674},{},[675],{"type":49,"value":676},"1-3%",{"type":44,"tag":563,"props":678,"children":679},{},[680,685,690,694,699],{"type":44,"tag":597,"props":681,"children":682},{},[683],{"type":49,"value":684},"Unsubscribe rate",{"type":44,"tag":597,"props":686,"children":687},{},[688],{"type":49,"value":689},"\u003C0.5%",{"type":44,"tag":597,"props":691,"children":692},{},[693],{"type":49,"value":689},{"type":44,"tag":597,"props":695,"children":696},{},[697],{"type":49,"value":698},"1-2%",{"type":44,"tag":597,"props":700,"children":701},{},[702],{"type":49,"value":676},{"type":44,"tag":56,"props":704,"children":705},{},[706],{"type":49,"value":707},"Adjust benchmarks based on industry and audience if the user has provided that context.",{"type":44,"tag":76,"props":709,"children":711},{"id":710},"sequence-type-templates",[712],{"type":49,"value":713},"Sequence Type Templates",{"type":44,"tag":56,"props":715,"children":716},{},[717],{"type":49,"value":718},"Use these as starting frameworks. Adapt length and content based on the user's goal and audience.",{"type":44,"tag":56,"props":720,"children":721},{},[722,727],{"type":44,"tag":116,"props":723,"children":724},{},[725],{"type":49,"value":726},"Onboarding (5-7 emails over 14-21 days):",{"type":49,"value":728},"\nWelcome and set expectations -- Quick win to demonstrate value -- Core feature deep dive -- Advanced feature or integration -- Social proof and community -- Check-in and feedback request -- Upgrade prompt or next steps",{"type":44,"tag":56,"props":730,"children":731},{},[732,737],{"type":44,"tag":116,"props":733,"children":734},{},[735],{"type":49,"value":736},"Lead Nurture (4-6 emails over 3-4 weeks):",{"type":49,"value":738},"\nValue-first educational content -- Pain point identification -- Solution positioning with proof -- Social proof and results -- Soft CTA (trial, demo, resource) -- Direct CTA (buy, book, sign up)",{"type":44,"tag":56,"props":740,"children":741},{},[742,747],{"type":44,"tag":116,"props":743,"children":744},{},[745],{"type":49,"value":746},"Re-engagement (3-4 emails over 10-14 days):",{"type":49,"value":748},"\n\"We miss you\" with a compelling reason to return -- Value reminder highlighting what they are missing -- Incentive or exclusive offer -- Last chance with clear deadline",{"type":44,"tag":56,"props":750,"children":751},{},[752,757],{"type":44,"tag":116,"props":753,"children":754},{},[755],{"type":49,"value":756},"Win-back (3-5 emails over 30 days):",{"type":49,"value":758},"\nFriendly check-in asking what went wrong -- What is new since they left -- Special offer or incentive to return -- Feedback request (even if they do not come back) -- Final goodbye with door open",{"type":44,"tag":56,"props":760,"children":761},{},[762,767],{"type":44,"tag":116,"props":763,"children":764},{},[765],{"type":49,"value":766},"Product Launch (4-6 emails over 2-3 weeks):",{"type":49,"value":768},"\nTeaser or pre-announcement -- Launch announcement with full details -- Feature spotlight or use case -- Social proof and early results -- Limited-time offer or bonus -- Last chance or reminder",{"type":44,"tag":56,"props":770,"children":771},{},[772,777],{"type":44,"tag":116,"props":773,"children":774},{},[775],{"type":49,"value":776},"Event Follow-up (3-4 emails over 7-10 days):",{"type":49,"value":778},"\nThank you with key takeaways or recordings -- Resource roundup from the event -- Related offer or next step -- Feedback survey",{"type":44,"tag":56,"props":780,"children":781},{},[782,787],{"type":44,"tag":116,"props":783,"children":784},{},[785],{"type":49,"value":786},"Upgrade\u002FUpsell (3-5 emails over 2-3 weeks):",{"type":49,"value":788},"\nUsage milestone or success celebration -- Feature gap or limitation they are hitting -- Upgrade benefits with proof -- Limited-time incentive -- Direct comparison of plans",{"type":44,"tag":56,"props":790,"children":791},{},[792,797],{"type":44,"tag":116,"props":793,"children":794},{},[795],{"type":49,"value":796},"Educational Drip (5-8 emails over 4-6 weeks):",{"type":49,"value":798},"\nIntroduction and what they will learn -- Lesson 1: foundational concept -- Lesson 2: intermediate concept -- Lesson 3: advanced concept -- Practical application or exercise -- Resource roundup -- Graduation and next steps",{"type":44,"tag":76,"props":800,"children":802},{"id":801},"tool-integration",[803],{"type":49,"value":804},"Tool Integration",{"type":44,"tag":262,"props":806,"children":808},{"id":807},"if-email-marketing-is-connected-eg-klaviyo-mailchimp-customerio",[809],{"type":49,"value":810},"If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io)",{"type":44,"tag":124,"props":812,"children":813},{},[814,819,824],{"type":44,"tag":112,"props":815,"children":816},{},[817],{"type":49,"value":818},"Reference how to set up the sequence as a flow or automation in the platform",{"type":44,"tag":112,"props":820,"children":821},{},[822],{"type":49,"value":823},"Note any platform-specific features to use (e.g., smart send time, conditional splits, A\u002FB testing)",{"type":44,"tag":112,"props":825,"children":826},{},[827],{"type":49,"value":828},"Map the branching logic to the platform's visual flow builder concepts",{"type":44,"tag":262,"props":830,"children":832},{"id":831},"if-marketing-automation-or-crm-is-connected-eg-hubspot-marketo",[833],{"type":49,"value":834},"If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo)",{"type":44,"tag":124,"props":836,"children":837},{},[838,843,848],{"type":44,"tag":112,"props":839,"children":840},{},[841],{"type":49,"value":842},"Reference lead scoring data to inform segmentation and exit conditions",{"type":44,"tag":112,"props":844,"children":845},{},[846],{"type":49,"value":847},"Use lifecycle stage data to tailor messaging per segment",{"type":44,"tag":112,"props":849,"children":850},{},[851],{"type":49,"value":852},"Note how to set enrollment triggers based on CRM properties or list membership",{"type":44,"tag":262,"props":854,"children":856},{"id":855},"if-no-tools-are-connected",[857],{"type":49,"value":858},"If no tools are connected",{"type":44,"tag":124,"props":860,"children":861},{},[862,867],{"type":44,"tag":112,"props":863,"children":864},{},[865],{"type":49,"value":866},"Deliver all email content in copy-paste-ready format",{"type":44,"tag":112,"props":868,"children":869},{},[870,872],{"type":49,"value":871},"Include a setup checklist the user can follow in any email platform:\n",{"type":44,"tag":108,"props":873,"children":874},{},[875,880,885,890,895],{"type":44,"tag":112,"props":876,"children":877},{},[878],{"type":49,"value":879},"Create the automation or flow",{"type":44,"tag":112,"props":881,"children":882},{},[883],{"type":49,"value":884},"Set the enrollment trigger",{"type":44,"tag":112,"props":886,"children":887},{},[888],{"type":49,"value":889},"Add each email with the specified delays",{"type":44,"tag":112,"props":891,"children":892},{},[893],{"type":49,"value":894},"Configure branching and exit conditions",{"type":44,"tag":112,"props":896,"children":897},{},[898],{"type":49,"value":899},"Set up tracking for the recommended metrics",{"type":44,"tag":76,"props":901,"children":903},{"id":902},"output",[904],{"type":49,"value":905},"Output",{"type":44,"tag":56,"props":907,"children":908},{},[909],{"type":49,"value":910},"Present the complete sequence with the following sections:",{"type":44,"tag":262,"props":912,"children":914},{"id":913},"sequence-overview-table",[915],{"type":49,"value":916},"Sequence Overview Table",{"type":44,"tag":555,"props":918,"children":919},{},[920],{"type":44,"tag":559,"props":921,"children":922},{},[923],{"type":44,"tag":563,"props":924,"children":925},{},[926,931,935,940,944,948],{"type":44,"tag":567,"props":927,"children":928},{},[929],{"type":49,"value":930},"#",{"type":44,"tag":567,"props":932,"children":933},{},[934],{"type":49,"value":333},{"type":44,"tag":567,"props":936,"children":937},{},[938],{"type":49,"value":939},"Purpose",{"type":44,"tag":567,"props":941,"children":942},{},[943],{"type":49,"value":443},{"type":44,"tag":567,"props":945,"children":946},{},[947],{"type":49,"value":424},{"type":44,"tag":567,"props":949,"children":950},{},[951],{"type":49,"value":952},"Condition",{"type":44,"tag":262,"props":954,"children":956},{"id":955},"full-email-drafts",[957],{"type":49,"value":958},"Full Email Drafts",{"type":44,"tag":56,"props":960,"children":961},{},[962],{"type":49,"value":963},"Each email with subject line options, preview text, purpose, body copy, CTA, timing, and segment notes.",{"type":44,"tag":262,"props":965,"children":967},{"id":966},"sequence-flow-diagram",[968],{"type":49,"value":969},"Sequence Flow Diagram",{"type":44,"tag":56,"props":971,"children":972},{},[973],{"type":49,"value":974},"A text-based diagram showing the email flow, branching paths, and exit points. Use a clear format such as:",{"type":44,"tag":976,"props":977,"children":981},"pre",{"className":978,"code":980,"language":49},[979],"language-text","[Trigger] --> Email 1 (Day 0)\n                |\n          Opened? --Yes--> Email 2 (Day 3)\n                |              |\n                No        Clicked CTA? --Yes--> [EXIT: Converted]\n                |              |\n                v              No\n          Email 1b (Day 2)     |\n                |              v\n                +--------> Email 3 (Day 7)\n                               |\n                               v\n                          Email 4 (Day 10)\n                               |\n                          [EXIT: Sequence complete]\n",[982],{"type":44,"tag":88,"props":983,"children":985},{"__ignoreMap":984},"",[986],{"type":49,"value":980},{"type":44,"tag":262,"props":988,"children":990},{"id":989},"branching-logic-notes",[991],{"type":49,"value":992},"Branching Logic Notes",{"type":44,"tag":56,"props":994,"children":995},{},[996],{"type":49,"value":997},"Summary of all conditions, exits, and suppressions in a reference list.",{"type":44,"tag":262,"props":999,"children":1001},{"id":1000},"ab-test-suggestions",[1002],{"type":49,"value":1003},"A\u002FB Test Suggestions",{"type":44,"tag":124,"props":1005,"children":1006},{},[1007,1012],{"type":44,"tag":112,"props":1008,"children":1009},{},[1010],{"type":49,"value":1011},"2-3 recommended A\u002FB tests (subject lines, CTA text, send time, email length)",{"type":44,"tag":112,"props":1013,"children":1014},{},[1015],{"type":49,"value":1016},"What to test, how to split, and how to measure the winner",{"type":44,"tag":262,"props":1018,"children":1020},{"id":1019},"metrics-to-track",[1021],{"type":49,"value":1022},"Metrics to Track",{"type":44,"tag":124,"props":1024,"children":1025},{},[1026,1031,1036,1041],{"type":44,"tag":112,"props":1027,"children":1028},{},[1029],{"type":49,"value":1030},"Primary conversion metric for the sequence",{"type":44,"tag":112,"props":1032,"children":1033},{},[1034],{"type":49,"value":1035},"Per-email metrics: open rate, CTR, unsubscribe rate",{"type":44,"tag":112,"props":1037,"children":1038},{},[1039],{"type":49,"value":1040},"Sequence-level metrics: overall conversion rate, time to conversion, drop-off points",{"type":44,"tag":112,"props":1042,"children":1043},{},[1044],{"type":49,"value":1045},"Recommended review cadence (e.g., \"Review performance weekly for the first month, then monthly\")",{"type":44,"tag":76,"props":1047,"children":1049},{"id":1048},"after-the-sequence",[1050],{"type":49,"value":1051},"After the Sequence",{"type":44,"tag":56,"props":1053,"children":1054},{},[1055],{"type":49,"value":1056},"Ask: \"Would you like me to:",{"type":44,"tag":124,"props":1058,"children":1059},{},[1060,1065,1070,1075,1080],{"type":44,"tag":112,"props":1061,"children":1062},{},[1063],{"type":49,"value":1064},"Revise the copy or tone for any specific email?",{"type":44,"tag":112,"props":1066,"children":1067},{},[1068],{"type":49,"value":1069},"Add a branching path for a specific scenario?",{"type":44,"tag":112,"props":1071,"children":1072},{},[1073],{"type":49,"value":1074},"Create a variation of this sequence for a different audience segment?",{"type":44,"tag":112,"props":1076,"children":1077},{},[1078],{"type":49,"value":1079},"Draft the A\u002FB test variants for the subject lines?",{"type":44,"tag":112,"props":1081,"children":1082},{},[1083],{"type":49,"value":1084},"Build a companion sequence (e.g., a post-purchase follow-up after this lead nurture converts)?\"",{"items":1086,"total":1201},[1087,1103,1119,1135,1153,1172,1186],{"slug":1088,"name":1088,"fn":1089,"description":1090,"org":1091,"tags":1092,"stars":26,"repoUrl":27,"updatedAt":1102},"accessibility-review","run WCAG accessibility audits","Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with \"audit accessibility\", \"check a11y\", \"is this accessible?\", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1093,1096,1099],{"name":1094,"slug":1095,"type":16},"Accessibility","accessibility",{"name":1097,"slug":1098,"type":16},"Design","design",{"name":1100,"slug":1101,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":1104,"name":1104,"fn":1105,"description":1106,"org":1107,"tags":1108,"stars":26,"repoUrl":27,"updatedAt":1118},"account-research","research accounts for sales intel","Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with \"research [company]\", \"look up [person]\", \"intel on [prospect]\", \"who is [name] at [company]\", or \"tell me about [company]\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1109,1112,1115],{"name":1110,"slug":1111,"type":16},"CRM","crm",{"name":1113,"slug":1114,"type":16},"Research","research",{"name":1116,"slug":1117,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":1120,"name":1120,"fn":1121,"description":1122,"org":1123,"tags":1124,"stars":26,"repoUrl":27,"updatedAt":1134},"analyze","answer data questions and run analyses","Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1125,1128,1131],{"name":1126,"slug":1127,"type":16},"Analytics","analytics",{"name":1129,"slug":1130,"type":16},"Data Analysis","data-analysis",{"name":1132,"slug":1133,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":1136,"name":1136,"fn":1137,"description":1138,"org":1139,"tags":1140,"stars":26,"repoUrl":27,"updatedAt":1152},"architecture","create and evaluate architecture decision records","Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1141,1144,1146,1149],{"name":1142,"slug":1143,"type":16},"ADR","adr",{"name":1145,"slug":1136,"type":16},"Architecture",{"name":1147,"slug":1148,"type":16},"Documentation","documentation",{"name":1150,"slug":1151,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":1154,"name":1154,"fn":1155,"description":1156,"org":1157,"tags":1158,"stars":26,"repoUrl":27,"updatedAt":1171},"audit-support","support SOX 404 control testing","Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1159,1162,1165,1168],{"name":1160,"slug":1161,"type":16},"Audit","audit",{"name":1163,"slug":1164,"type":16},"Finance","finance",{"name":1166,"slug":1167,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":1169,"slug":1170,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":1173,"name":1173,"fn":1174,"description":1175,"org":1176,"tags":1177,"stars":26,"repoUrl":27,"updatedAt":1185},"brand-review","review content against brand voice","Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1178,1181,1182],{"name":1179,"slug":1180,"type":16},"Branding","branding",{"name":14,"slug":15,"type":16},{"name":1183,"slug":1184,"type":16},"Writing","writing","2026-04-06T17:58:19.548331",{"slug":1187,"name":1187,"fn":1188,"description":1189,"org":1190,"tags":1191,"stars":26,"repoUrl":27,"updatedAt":1200},"brand-voice-enforcement","enforce brand voice in content","This skill applies brand guidelines to content creation. It should be used when the user asks to \"write an email\", \"draft a proposal\", \"create a pitch deck\", \"write a LinkedIn post\", \"draft a presentation\", \"write a Slack message\", \"draft sales content\", or any content creation request where brand voice should be applied. Also triggers on \"on-brand\", \"brand voice\", \"enforce voice\", \"apply brand guidelines\", \"brand-aligned content\", \"write in our voice\", \"use our brand tone\", \"make this sound like us\", \"rewrite this in our tone\", or \"this doesn't sound on-brand\". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1192,1193,1196,1199],{"name":1179,"slug":1180,"type":16},{"name":1194,"slug":1195,"type":16},"Communications","communications",{"name":1197,"slug":1198,"type":16},"Content Creation","content-creation",{"name":1183,"slug":1184,"type":16},"2026-04-06T18:00:23.528956",200,{"items":1203,"total":1380},[1204,1223,1235,1247,1266,1277,1298,1318,1328,1343,1351,1364],{"slug":1205,"name":1205,"fn":1206,"description":1207,"org":1208,"tags":1209,"stars":1220,"repoUrl":1221,"updatedAt":1222},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1210,1213,1214,1217],{"name":1211,"slug":1212,"type":16},"Creative","creative",{"name":1097,"slug":1098,"type":16},{"name":1215,"slug":1216,"type":16},"Generative Art","generative-art",{"name":1218,"slug":1219,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":1224,"name":1224,"fn":1225,"description":1226,"org":1227,"tags":1228,"stars":1220,"repoUrl":1221,"updatedAt":1234},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1229,1230,1231],{"name":1179,"slug":1180,"type":16},{"name":1097,"slug":1098,"type":16},{"name":1232,"slug":1233,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":1236,"name":1236,"fn":1237,"description":1238,"org":1239,"tags":1240,"stars":1220,"repoUrl":1221,"updatedAt":1246},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1241,1242,1243],{"name":1211,"slug":1212,"type":16},{"name":1097,"slug":1098,"type":16},{"name":1244,"slug":1245,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":1248,"name":1248,"fn":1249,"description":1250,"org":1251,"tags":1252,"stars":1220,"repoUrl":1221,"updatedAt":1265},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1253,1256,1257,1260,1262],{"name":1254,"slug":1255,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":1258,"slug":1259,"type":16},"Anthropic SDK","anthropic-sdk",{"name":1261,"slug":1248,"type":16},"Claude API",{"name":1263,"slug":1264,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":1267,"name":1267,"fn":1268,"description":1269,"org":1270,"tags":1271,"stars":1220,"repoUrl":1221,"updatedAt":1276},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1272,1273],{"name":1147,"slug":1148,"type":16},{"name":1274,"slug":1275,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":1278,"name":1278,"fn":1279,"description":1280,"org":1281,"tags":1282,"stars":1220,"repoUrl":1221,"updatedAt":1297},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1283,1286,1288,1291,1294],{"name":1284,"slug":1285,"type":16},"Documents","documents",{"name":1287,"slug":1278,"type":16},"DOCX",{"name":1289,"slug":1290,"type":16},"Office","office",{"name":1292,"slug":1293,"type":16},"Templates","templates",{"name":1295,"slug":1296,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":1299,"name":1299,"fn":1300,"description":1301,"org":1302,"tags":1303,"stars":1220,"repoUrl":1221,"updatedAt":1317},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1304,1305,1308,1311,1314],{"name":1097,"slug":1098,"type":16},{"name":1306,"slug":1307,"type":16},"Frontend","frontend",{"name":1309,"slug":1310,"type":16},"React","react",{"name":1312,"slug":1313,"type":16},"Tailwind CSS","tailwind-css",{"name":1315,"slug":1316,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":1319,"name":1319,"fn":1320,"description":1321,"org":1322,"tags":1323,"stars":1220,"repoUrl":1221,"updatedAt":1327},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1324,1325,1326],{"name":1194,"slug":1195,"type":16},{"name":1292,"slug":1293,"type":16},{"name":1183,"slug":1184,"type":16},"2026-04-06T17:56:20.695522",{"slug":1329,"name":1329,"fn":1330,"description":1331,"org":1332,"tags":1333,"stars":1220,"repoUrl":1221,"updatedAt":1342},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1334,1335,1338,1339],{"name":1254,"slug":1255,"type":16},{"name":1336,"slug":1337,"type":16},"API Development","api-development",{"name":1263,"slug":1264,"type":16},{"name":1340,"slug":1341,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":1245,"name":1245,"fn":1344,"description":1345,"org":1346,"tags":1347,"stars":1220,"repoUrl":1221,"updatedAt":1350},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1348,1349],{"name":1284,"slug":1285,"type":16},{"name":1244,"slug":1245,"type":16},"2026-04-06T17:56:02.483316",{"slug":1352,"name":1352,"fn":1353,"description":1354,"org":1355,"tags":1356,"stars":1220,"repoUrl":1221,"updatedAt":1363},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1357,1360],{"name":1358,"slug":1359,"type":16},"PowerPoint","powerpoint",{"name":1361,"slug":1362,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":1365,"name":1365,"fn":1366,"description":1367,"org":1368,"tags":1369,"stars":1220,"repoUrl":1221,"updatedAt":1379},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1370,1371,1372,1375,1378],{"name":1254,"slug":1255,"type":16},{"name":1147,"slug":1148,"type":16},{"name":1373,"slug":1374,"type":16},"Evals","evals",{"name":1376,"slug":1377,"type":16},"Performance","performance",{"name":1274,"slug":1275,"type":16},"2026-04-19T06:45:40.804",490]