Skip to content

feat: add mailtrap-email-integration skill #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dieudonneAwa wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add mailtrap-email-integration skill #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 51 additions & 0 deletions mailtrap-email-integration/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
name: mailtrap-email-integration
description: Integrate transactional email sending with Mailtrap's API, covering sandbox testing, domain verification, and authentication patterns
author: dieudonneAwa
version: "1.0"
tags:
- email
- api
- integration
- testing
- smtp
---

# Mailtrap Email Integration

Patterns for integrating transactional email sending using Mailtrap's Email API and Sandbox, covering environment separation, authentication, domain verification, and delivery troubleshooting.

## When to Use

- Implementing email-sending features (confirmations, password resets, notifications)
- Setting up safe email testing in dev or staging without reaching real inboxes
- Debugging email delivery issues
- Verifying a sending domain before going to production

## Core Workflow

1. Use the Mailtrap Sandbox endpoint in dev/staging to capture emails safely
2. Authenticate requests using a Bearer token in the Authorization header
3. Verify your sending domain DNS records (SPF, DKIM, DMARC) before switching to production
4. Switch to the production sending endpoint only after domain verification is complete

## Key Patterns

**Sandbox vs production separation**
Route non-production environments to the Sandbox API endpoint so test emails never reach real inboxes. Use separate API tokens per environment.

**Authentication**
All requests require a Bearer token: `Authorization: Bearer YOUR_TOKEN`. Tokens are scoped per project; never share tokens across environments.

**Domain verification**
Production sending requires verified DNS records. Missing or incorrect SPF/DKIM/DMARC records cause silent delivery failures or spam placement.

**Error handling**
Always check the response status code. Treat send failures as fallible network calls and surface actionable errors rather than silently swallowing them.

## Anti-Patterns

- Using the production endpoint in dev or staging
- Hardcoding API tokens in source code
- Sending to real recipients before domain verification completes
- Ignoring non-200 response codes from the send API
Loading