[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XWGSBZB0CZBVE7A9VAD41":3,"skill-same:01M77XWGSBZB0CZBVE7A9VAD41":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77XWGSBZB0CZBVE7A9VAD41","mailtrap-email-integration",null,"Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication. Use when implementing email-sending features, debugging delivery issues, or setting up safe dev\u002Fstaging email testing.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-mailtrap-email-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mailtrap-email-integration\ndescription: Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication. Use when implementing email-sending features, debugging delivery issues, or setting up safe dev\u002Fstaging email testing.\norigin: HCP\n---\n\n# Mailtrap Email Integration\n\nPatterns for adding transactional email sending to an application using Mailtrap's Email API and Sandbox, covering authentication, environment separation, and common delivery pitfalls.\n\n## When to Activate\n\n- Implementing a \"send email\" feature (signup confirmation, password reset, notifications, receipts)\n- Debugging why emails aren't arriving in dev\u002Fstaging\n- Setting up a project's first email-sending integration\n- Reviewing code that calls an email API directly without sandbox separation\n\n## Core Concepts\n\n**Sandbox vs. Production separation.** Mailtrap provides a Sandbox API that captures emails without delivering them, used for dev\u002Fstaging so test emails never reach real inboxes. Production sending uses a separate, verified-domain endpoint. Never point a dev environment at the production sending endpoint.\n\n**Authentication.** Requests use a Bearer token in the `Authorization` header. Tokens are scoped per project; sandbox and production typically use different tokens.\n\n**Domain verification.** Production sending requires verifying a sending domain via DNS records (SPF, DKIM, DMARC) before Mailtrap will deliver to real recipients. Skipping this causes silent delivery failures or spam-folder placement.\n\n## Code Examples\n\n```typescript\n\u002F\u002F Sending via Mailtrap's Email API (production)\nasync function sendEmail(to: string, subject: string, html: string) {\n  const response = await fetch(\"https:\u002F\u002Fsend.api.mailtrap.io\u002Fapi\u002Fsend\", {\n    method: \"POST\",\n    headers: {\n      \"Authorization\": `Bearer ${process.env.MAILTRAP_API_TOKEN}`,\n      \"Content-Type\": \"application\u002Fjson\",\n    },\n    body: JSON.stringify({\n      from: { email: \"no-reply@yourverifieddomain.com\", name: \"Your App\" },\n      to: [{ email: to }],\n      subject,\n      html,\n    }),\n  });\n\n  if (!response.ok) {\n    throw new Error(`Email send failed: ${response.status}`);\n  }\n  return response.json();\n}\n```\n\n```typescript\n\u002F\u002F Same call, routed to Sandbox in non-production environments\nconst MAILTRAP_ENDPOINT = process.env.NODE_ENV === \"production\"\n  ? \"https:\u002F\u002Fsend.api.mailtrap.io\u002Fapi\u002Fsend\"\n  : `https:\u002F\u002Fsandbox.api.mailtrap.io\u002Fapi\u002Fsend\u002F${process.env.MAILTRAP_INBOX_ID}`;\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It's a Problem | Instead |\n| --- | --- | --- |\n| Using the production sending endpoint in dev\u002Ftest | Real test emails reach real inboxes, risking spam complaints and leaked test data | Route non-production environments to the Sandbox endpoint |\n| Hardcoding API tokens in source | Credential leak risk if committed to version control | Load tokens from environment variables \u002F secrets manager |\n| Sending before domain verification completes | Emails silently fail or land in spam | Verify SPF\u002FDKIM\u002FDMARC records before enabling production sending |\n| No retry\u002Ferror handling on send failures | Silent notification failures (e.g., user never gets password reset email) | Check response status, log failures, surface actionable errors |\n\n## Best Practices\n\n- Keep sandbox and production tokens in separate environment variables, never share one token across environments\n- Verify sending domain DNS records before any production launch involving email\n- Log delivery failures with enough context to debug (recipient, template, timestamp, response code)\n- Treat email sending as a fallible network call: wrap in try\u002Fcatch, never assume success\n\n## Related Skills\n\n`api-and-interface-design`, `security-and-hardening`, `ci-cd-and-automation`\n","# Mailtrap Email Integration\n\nPatterns for adding transactional email sending to an application using Mailtrap's Email API and Sandbox, covering authentication, environment separation, and common delivery pitfalls.\n\n## When to Activate\n\n- Implementing a \"send email\" feature (signup confirmation, password reset, notifications, receipts)\n- Debugging why emails aren't arriving in dev\u002Fstaging\n- Setting up a project's first email-sending integration\n- Reviewing code that calls an email API directly without sandbox separation\n\n## Core Concepts\n\n**Sandbox vs. Production separation.** Mailtrap provides a Sandbox API that captures emails without delivering them, used for dev\u002Fstaging so test emails never reach real inboxes. Production sending uses a separate, verified-domain endpoint. Never point a dev environment at the production sending endpoint.\n\n**Authentication.** Requests use a Bearer token in the `Authorization` header. Tokens are scoped per project; sandbox and production typically use different tokens.\n\n**Domain verification.** Production sending requires verifying a sending domain via DNS records (SPF, DKIM, DMARC) before Mailtrap will deliver to real recipients. Skipping this causes silent delivery failures or spam-folder placement.\n\n## Code Examples\n\n```typescript\n\u002F\u002F Sending via Mailtrap's Email API (production)\nasync function sendEmail(to: string, subject: string, html: string) {\n  const response = await fetch(\"https:\u002F\u002Fsend.api.mailtrap.io\u002Fapi\u002Fsend\", {\n    method: \"POST\",\n    headers: {\n      \"Authorization\": `Bearer ${process.env.MAILTRAP_API_TOKEN}`,\n      \"Content-Type\": \"application\u002Fjson\",\n    },\n    body: JSON.stringify({\n      from: { email: \"no-reply@yourverifieddomain.com\", name: \"Your App\" },\n      to: [{ email: to }],\n      subject,\n      html,\n    }),\n  });\n\n  if (!response.ok) {\n    throw new Error(`Email send failed: ${response.status}`);\n  }\n  return response.json();\n}\n```\n\n```typescript\n\u002F\u002F Same call, routed to Sandbox in non-production environments\nconst MAILTRAP_ENDPOINT = process.env.NODE_ENV === \"production\"\n  ? \"https:\u002F\u002Fsend.api.mailtrap.io\u002Fapi\u002Fsend\"\n  : `https:\u002F\u002Fsandbox.api.mailtrap.io\u002Fapi\u002Fsend\u002F${process.env.MAILTRAP_INBOX_ID}`;\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It's a Problem | Instead |\n| --- | --- | --- |\n| Using the production sending endpoint in dev\u002Ftest | Real test emails reach real inboxes, risking spam complaints and leaked test data | Route non-production environments to the Sandbox endpoint |\n| Hardcoding API tokens in source | Credential leak risk if committed to version control | Load tokens from environment variables \u002F secrets manager |\n| Sending before domain verification completes | Emails silently fail or land in spam | Verify SPF\u002FDKIM\u002FDMARC records before enabling production sending |\n| No retry\u002Ferror handling on send failures | Silent notification failures (e.g., user never gets password reset email) | Check response status, log failures, surface actionable errors |\n\n## Best Practices\n\n- Keep sandbox and production tokens in separate environment variables, never share one token across environments\n- Verify sending domain DNS records before any production launch involving email\n- Log delivery failures with enough context to debug (recipient, template, timestamp, response code)\n- Treat email sending as a fallible network call: wrap in try\u002Fcatch, never assume success\n\n## Related Skills\n\n`api-and-interface-design`, `security-and-hardening`, `ci-cd-and-automation`\n",{"name":5,"origin":24,"description":7},"HCP","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-mailtrap-email-integration",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill mailtrap-email-integration",{"tool":40,"command":41},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill mailtrap-email-integration",{"tool":43,"command":44},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill mailtrap-email-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-mailtrap-email-integration\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","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\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]