playbooks

home / skills / resend / resend-skills / resend-skills

resend-skills skill

/SKILL.md

This skill routes to Resend sub-skills for sending, receiving, or AI inbox handling to streamline email workflows.

This is most likely a fork of the resend-skills skill from openclaw
npx playbooks add skill resend/resend-skills --skill resend-skills

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
3.2 KB
---
name: resend
description: Use when working with Resend email platform - routes to specific sub-skills for sending, receiving, audiences, or broadcasts.
license: MIT
metadata:
    author: resend
    version: "2.5.0"
    homepage: https://resend.com
    source: https://github.com/resend/resend-skills
inputs:
    - name: RESEND_API_KEY
      description: Resend API key for sending and receiving emails. Get yours at https://resend.com/api-keys
      required: true
    - name: RESEND_WEBHOOK_SECRET
      description: Webhook signing secret for verifying event payloads. Found in the Resend dashboard under Webhooks after creating an endpoint.
      required: false
---

# Resend

## 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-email-inbox` | Setting up email for AI agents, or any system where untrusted email content triggers actions — includes 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-email-inbox` skill
- Configuring email for Moltbot/Clawdbot 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

**Automated system processes untrusted email content and takes actions?** Use `agent-email-inbox` skill
- Even without AI/LLM involvement, any system that interprets freeform email content from external senders and triggers actions (refunds, database changes, forwarding) needs security. Untrusted input triggering actions = attack vector.

**Sending + receiving together?** You need both `resend-inbound` and `send-email`
- Auto-replies, email forwarding, or any receive-then-send workflow requires both skills
- Set up inbound first, then sending
- Note: batch sending does not support attachments or scheduling — use single sends when forwarding with attachments

**Marketing emails or newsletters?** Use [Resend Broadcasts](https://resend.com/broadcasts)
- The sub-skills above are for transactional email. Marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking should use Resend Broadcasts, not batch sending.

## Common Setup

### API Key

Store in environment variable:
```bash
export RESEND_API_KEY=re_xxxxxxxxx
```

### SDK Installation

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

## Resources

- [Resend Documentation](https://resend.com/docs)
- [API Reference](https://resend.com/docs/api-reference)
- [Dashboard](https://resend.com/emails)

Overview

This skill routes developer workflows to Resend-specific sub-skills for sending, receiving, audiences, and broadcasts. It helps choose the right sub-skill for transactional sends, inbound processing, or secure AI-agent inbox setups. Use it to map high-level email requirements to concrete Resend features and integrations.

How this skill works

The skill inspects the email workflow requirements and directs you to the appropriate sub-skill: send-email for transactional sends, resend-inbound for receiving and webhook processing, or agent-email-inbox for secure agent inbox setups. It also highlights when you need multiple sub-skills together (for example, receive-then-send flows) and points out limitations like batch-send attachment support.

When to use it

  • You need to send transactional or batch emails (notifications, receipts, alerts).
  • You must process inbound mail, attachments, or email.received webhooks.
  • You are configuring an inbox for an AI agent or any system that executes actions from untrusted email content.
  • You need both receiving and sending in a single workflow (auto-replies, forwards).
  • You want guidance on when to use Resend Broadcasts for marketing vs. transactional flows.

Best practices

  • Set RESEND_API_KEY in environment variables and never commit keys to source control.
  • Configure inbound MX and verify webhooks before routing production traffic.
  • Use agent-email-inbox security features: allowlists, content filtering, and prompt-injection defenses when external content can trigger actions.
  • Split responsibilities: inbound processing should validate and sanitize before any state-changing operations or sends.
  • When forwarding attachments or scheduling per-recipient content, prefer single sends rather than batch sends.

Example use cases

  • Send transaction emails with templates and delivery webhooks using send-email.
  • Receive customer replies and extract attachments or metadata via resend-inbound webhooks.
  • Set up a secure agent inbox for an AI assistant that must avoid prompt injection and handle untrusted messages.
  • Implement an auto-reply system that receives inbound mail, validates it, then issues a transactional send (requires both resend-inbound and send-email).
  • Decide to use Resend Broadcasts for newsletters and large marketing lists instead of batch transactional sends.

FAQ

Do I need multiple sub-skills to forward received emails with attachments?

Yes. Forwarding with attachments typically requires inbound processing via resend-inbound and then a single send via send-email, since batch sends don’t support attachments or per-recipient scheduling.

How do I secure an inbox used by an AI agent?

Use agent-email-inbox features: trusted sender allowlists, strict content filtering, webhook authentication, and explicit checks that prevent untrusted content from becoming executable prompts or automated state changes.

When should I use Resend Broadcasts vs. these sub-skills?

Use Resend Broadcasts for marketing newsletters, large subscriber lists, and unsubscribe/engagement tracking. Use the sub-skills here for transactional, developer-driven email workflows and inbound processing.