[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GEHDFN0HF0PY0EARACWDG":3,"skill-same:01M70GEHDFN0HF0PY0EARACWDG":77},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70GEHDFN0HF0PY0EARACWDG","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fmailtrap-email-integration\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"email","integration","mailtrap email integration","sandbox","domain","transactional","safe","features","delivery","email api","verification","guides","api","when","debugging","implementing","issues","up","testing","authentication","2026-11-10 10:12:30",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: ECC\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":54,"description":7},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fmailtrap-email-integration",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill mailtrap-email-integration",{"tool":69,"command":70},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill mailtrap-email-integration",{"tool":72,"command":73},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill mailtrap-email-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fmailtrap-email-integration\u002FSKILL.md",true,[],[78,86,94,101,108,115],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":93},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":93},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":93},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]