[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FYBFP8S1PVC40X515W58P":3,"skill-same:01M71FYBFP8S1PVC40X515W58P":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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71FYBFP8S1PVC40X515W58P","email-best-practices",null,"Use when building email features, emails going to spam, high bounce rates, setting up SPF\u002FDKIM\u002FDMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_resend_email_best_practices\u002Fskill.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"email","best practices","email best practices","logic","high","github","gdpr","can","when","use","best-practices","emails","agent-skills","implementing","up","spam","authentication","retry","resend","setting","2026-11-10 10:12:30",false,"---\nname: email-best-practices\ndescription: Use when building email features, emails going to spam, high bounce rates, setting up SPF\u002FDKIM\u002FDMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.\nlicense: MIT\nmetadata:\n  author: Resend\n  version: \"1.0.2\"\n  homepage: https:\u002F\u002Fresend.com\u002Fagent-skills\n  source: https:\u002F\u002Fgithub.com\u002Fresend\u002Femail-best-practices\n  openclaw:\n    links:\n      repository: https:\u002F\u002Fgithub.com\u002Fresend\u002Femail-best-practices\n      documentation: https:\u002F\u002Fresend.com\u002Fdocs\u002Femail-best-practices-skill\n---\n\n# Email Best Practices\n\nGuidance for building deliverable, compliant, user-friendly emails.\n\n## Architecture Overview\n\n```\n[User] → [Email Form] → [Validation] → [Double Opt-In]\n                                              ↓\n                                    [Consent Recorded]\n                                              ↓\n[Suppression Check] ←──────────────[Ready to Send]\n        ↓\n[Idempotent Send + Retry] ──────→ [Email API]\n                                       ↓\n                              [Webhook Events]\n                                       ↓\n              ┌────────┬────────┬─────────────┐\n              ↓        ↓        ↓             ↓\n         Delivered  Bounced  Complained  Opened\u002FClicked\n                       ↓        ↓\n              [Suppression List Updated]\n                       ↓\n              [List Hygiene Jobs]\n```\n\n## Quick Reference\n\n| Need to... | See |\n|------------|-----|\n| Set up SPF\u002FDKIM\u002FDMARC, fix spam issues | Deliverability (`.\u002Freferences\u002Fdeliverability.md`) |\n| Build password reset, OTP, confirmations | Transactional Emails (`.\u002Freferences\u002Ftransactional_emails.md`) |\n| Plan which emails your app needs | Transactional Email Catalog (`.\u002Freferences\u002Ftransactional_email_catalog.md`) |\n| Build newsletter signup, validate emails | Email Capture (`.\u002Freferences\u002Femail_capture.md`) |\n| Send newsletters, promotions | Marketing Emails (`.\u002Freferences\u002Fmarketing_emails.md`) |\n| Ensure CAN-SPAM\u002FGDPR\u002FCASL compliance | Compliance (`.\u002Freferences\u002Fcompliance.md`) |\n| Decide transactional vs marketing | Email Types (`.\u002Freferences\u002Femail_types.md`) |\n| Handle retries, idempotency, errors | Sending Reliability (`.\u002Freferences\u002Fsending_reliability.md`) |\n| Process delivery events, set up webhooks | Webhooks & Events (`.\u002Freferences\u002Fwebhooks_events.md`) |\n| Manage bounces, complaints, suppression | List Management (`.\u002Freferences\u002Flist_management.md`) |\n\n## Start Here\n\n**New app?**\nStart with the Catalog (`.\u002Freferences\u002Ftransactional_email_catalog.md`) to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (`.\u002Freferences\u002Fdeliverability.md`) (DNS authentication) before sending your first email.\n\n**Spam issues?**\nCheck Deliverability (`.\u002Freferences\u002Fdeliverability.md`) first—authentication problems are the most common cause. Gmail\u002FYahoo reject unauthenticated emails.\n\n**Marketing emails?**\nFollow this path: Email Capture (`.\u002Freferences\u002Femail_capture.md`) (collect consent) → Compliance (`.\u002Freferences\u002Fcompliance.md`) (legal requirements) → Marketing Emails (`.\u002Freferences\u002Fmarketing_emails.md`) (best practices).\n\n**Production-ready sending?**\nAdd reliability: Sending Reliability (`.\u002Freferences\u002Fsending_reliability.md`) (retry + idempotency) → Webhooks & Events (`.\u002Freferences\u002Fwebhooks_events.md`) (track delivery) → List Management (`.\u002Freferences\u002Flist_management.md`) (handle bounces).\n","# Email Best Practices\n\nGuidance for building deliverable, compliant, user-friendly emails.\n\n## Architecture Overview\n\n```\n[User] → [Email Form] → [Validation] → [Double Opt-In]\n                                              ↓\n                                    [Consent Recorded]\n                                              ↓\n[Suppression Check] ←──────────────[Ready to Send]\n        ↓\n[Idempotent Send + Retry] ──────→ [Email API]\n                                       ↓\n                              [Webhook Events]\n                                       ↓\n              ┌────────┬────────┬─────────────┐\n              ↓        ↓        ↓             ↓\n         Delivered  Bounced  Complained  Opened\u002FClicked\n                       ↓        ↓\n              [Suppression List Updated]\n                       ↓\n              [List Hygiene Jobs]\n```\n\n## Quick Reference\n\n| Need to... | See |\n|------------|-----|\n| Set up SPF\u002FDKIM\u002FDMARC, fix spam issues | Deliverability (`.\u002Freferences\u002Fdeliverability.md`) |\n| Build password reset, OTP, confirmations | Transactional Emails (`.\u002Freferences\u002Ftransactional_emails.md`) |\n| Plan which emails your app needs | Transactional Email Catalog (`.\u002Freferences\u002Ftransactional_email_catalog.md`) |\n| Build newsletter signup, validate emails | Email Capture (`.\u002Freferences\u002Femail_capture.md`) |\n| Send newsletters, promotions | Marketing Emails (`.\u002Freferences\u002Fmarketing_emails.md`) |\n| Ensure CAN-SPAM\u002FGDPR\u002FCASL compliance | Compliance (`.\u002Freferences\u002Fcompliance.md`) |\n| Decide transactional vs marketing | Email Types (`.\u002Freferences\u002Femail_types.md`) |\n| Handle retries, idempotency, errors | Sending Reliability (`.\u002Freferences\u002Fsending_reliability.md`) |\n| Process delivery events, set up webhooks | Webhooks & Events (`.\u002Freferences\u002Fwebhooks_events.md`) |\n| Manage bounces, complaints, suppression | List Management (`.\u002Freferences\u002Flist_management.md`) |\n\n## Start Here\n\n**New app?**\nStart with the Catalog (`.\u002Freferences\u002Ftransactional_email_catalog.md`) to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (`.\u002Freferences\u002Fdeliverability.md`) (DNS authentication) before sending your first email.\n\n**Spam issues?**\nCheck Deliverability (`.\u002Freferences\u002Fdeliverability.md`) first—authentication problems are the most common cause. Gmail\u002FYahoo reject unauthenticated emails.\n\n**Marketing emails?**\nFollow this path: Email Capture (`.\u002Freferences\u002Femail_capture.md`) (collect consent) → Compliance (`.\u002Freferences\u002Fcompliance.md`) (legal requirements) → Marketing Emails (`.\u002Freferences\u002Fmarketing_emails.md`) (best practices).\n\n**Production-ready sending?**\nAdd reliability: Sending Reliability (`.\u002Freferences\u002Fsending_reliability.md`) (retry + idempotency) → Webhooks & Events (`.\u002Freferences\u002Fwebhooks_events.md`) (track delivery) → List Management (`.\u002Freferences\u002Flist_management.md`) (handle bounces).\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"source":51,"version":52,"homepage":53,"openclaw":54},"Resend","https:\u002F\u002Fgithub.com\u002Fresend\u002Femail-best-practices","1.0.2","https:\u002F\u002Fresend.com\u002Fagent-skills",{"links":55},{"repository":51,"documentation":56},"https:\u002F\u002Fresend.com\u002Fdocs\u002Femail-best-practices-skill","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_resend_email_best_practices",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill email-best-practices",{"tool":72,"command":73},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill email-best-practices",{"tool":75,"command":76},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill email-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_resend_email_best_practices\u002Fskill.md",true,[],[81,110,133,154,173,196],{"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":109},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[91,92,93,94,95,96,97,98,99,100,101,102,103,37,32,104,105,106,107,108],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":109},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[116],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[91,118,119,95,120,121,122,123,37,124,32,125,104,126,127,128,129,130,131,132],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":109},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[139],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[91,141,142,95,25,123,143,32,144,125,104,145,146,147,148,149,150,151,152,153],"react best practices","vercel react best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":109},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[160],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[162,95,163,150,164,165,166,167,153,168,169,33,32,170,125,104,171,172,105,91],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":109},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[183,184,185,186,25,187,188,189,132,151,123,190,191,143,192,33,193,194,195,32],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":219},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[202],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[204,205,206,207,208,101,209,167,210,37,211,212,32,91,213,214,215,216,217,218],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]