[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWPRF03VSDVGHGBT40YKBD":3,"skill-same:01M7CWPRF03VSDVGHGBT40YKBD":47},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CWPRF03VSDVGHGBT40YKBD","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.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fmailtrap-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: 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":24,"description":7},"ECC","main","a73152352c0612252131e5cf84e91312a6cf17dc","utilities\u002Fmailtrap-email-integration","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill mailtrap-email-integration",{"tool":39,"command":40},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill mailtrap-email-integration",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill mailtrap-email-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fmailtrap-email-integration\u002FSKILL.md",true,[],[48,55,62,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\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},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\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},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\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},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]