resend

01 前言 Front Matter

name: resend
license: MIT
metadata: { "author": "resend", "version": "2.1.0" }
description: Use when working with Resend email platform - routes to specific sub-skills for sending, receiving, audiences, or broadcasts.

03 SKILL.md 正文

Overview

Resend is an email platform for developers. This skill routes to feature-specific sub-skills.

Sub-Skills

Feature	Skill	Use When
Sending emails	`send-email`	Transactional emails, notifications, batch sends
Receiving emails	`resend-inbound`	Processing inbound emails, webhooks for received mail, attachments
AI Agent inbox	`agent-inbox`	Setting up email for AI agents with security measures against prompt injection

Quick Routing

Need to send emails? Use send-email skill

Single or batch transactional emails
Attachments, scheduling, templates
Delivery webhooks (bounced, delivered, opened)

Need to receive emails? Use resend-inbound skill

Setting up inbound domain (MX records)
Processing email.received webhooks
Retrieving email content and attachments
Forwarding received emails

Setting up an AI agent inbox? Use agent-inbox skill

Configuring email for ThinkFleet or similar AI agents
Webhook setup with ngrok/tunneling for local development
Security levels to prevent prompt injection attacks
Trusted sender allowlists and content filtering

Common Setup

API Key

Store in environment variable:

export RESEND_API_KEY=re_xxxxxxxxx

SDK Installation

See send-email skill for installation instructions across all supported languages.

Resources

04 同仓库更多 Skills

ThinkfleetAI/thinkfleet-engine

healthkit-sync

iOS HealthKit data sync CLI commands and patterns. Use when working with healthsync CLI, fetching Apple Health data (steps, heart rate, sleep, workouts), pairing iOS devices over local network, or understanding the iOS Health Sync project architecture including mTLS certificate pinning, Keychain storage, and audit logging.

★ 0

ThinkfleetAI/thinkfleet-engine

conventional-commits

Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.

★ 0