Resend

Manage received (inbound) emails and attachments via Resend API. Use when user asks about their emails, received messages, or email attachments.

Security Scan

The skill's requirements and runtime instructions match its stated purpose (querying inbound emails via the Resend API); nothing requested is disproportionate, though you should verify the npm package provenance before installing globally.

Purpose & Capability

Name/description (manage inbound emails via Resend) align with required items: the 'resend' CLI binary and a RESEND_API_KEY are exactly what this task needs.

Instruction Scope

SKILL.md only instructs running the resend CLI and using --json/jq for parsing; it does not ask the agent to read unrelated files, other env vars, or send data to unexpected endpoints.

Install Mechanism

No formal install spec in the metadata (instruction-only). SKILL.md recommends npm install -g @mjrussell/resend-cli — installing a global npm package is standard but you should verify the package's publisher and that it is the official Resend CLI before running a global install.

Credentials

Only RESEND_API_KEY is required (declared). That is proportional and expected for read access to inbound emails. The SKILL.md explicitly recommends creating an API key with read permissions.

Persistence & Privilege

Skill is user-invocable, not always-included, and does not request system-wide persistence or modify other skills—privilege level is appropriate.

Assessment

This skill appears coherent for querying inbound emails via Resend. Before installing or using it: 1) Confirm the CLI package name/author (@mjrussell/resend-cli) is the official/resend-backed release to avoid installing a malicious npm package. 2) Create a scoped API key with only the necessary read permissions and avoid using broad or long-lived keys; revoke it if you stop using the skill. 3) Installing the CLI globally (npm -g) affects your system PATH—prefer a vetted package or use a container/virtual environment if unsure. 4) The skill is instruction-only and only needs RESEND_API_KEY and the resend binary; no other secrets or file reads are requested. If you want extra assurance, ask for the official upstream package link or repository before installing.

Resend CLI

CLI for the Resend email API. Query received (inbound) emails and attachments.

Installation

npm install -g @mjrussell/resend-cli

Setup

1. Sign up at resend.com
2. Set up inbound email routing for your domain
3. Create API key at API Keys → Create API key (needs read permissions)
4. Set environment variable: export RESEND_API_KEY="re_your_key"

Commands

List Emails

resend email list              # List recent emails (default 10)
resend email list -l 20        # List 20 emails
resend email list --json       # Output as JSON

Get Email Details

resend email get <id>          # Show email details
resend email get <id> --json   # Output as JSON

Attachments

resend email attachments <email_id>                    # List attachments
resend email attachment <email_id> <attachment_id>     # Get attachment metadata
resend email attachments <email_id> --json             # Output as JSON

Domains

resend domain list             # List configured domains
resend domain get <id>         # Get domain details with DNS records
resend domain list --json      # Output as JSON

Usage Examples

User: "Do I have any new emails?"

resend email list -l 5

User: "Show me the latest email"

resend email list --json | jq -r '.data.data[0].id'  # Get ID
resend email get <id>

User: "What attachments are on that email?"

resend email attachments <email_id>

User: "What domains do I have set up?"

resend domain list

User: "Show me the full content of email X"

resend email get <email_id>

Notes

• This CLI only supports received (inbound) emails, not sending
• Use --json flag and pipe to jq for scripting
• Email IDs are UUIDs shown in list output