Resend

**Overall**: Solid, focused skill for interacting with inbound email data via Resend. Best suited for users who already use Resend for inbound routing and need to inspect emails, attachments, or domains through natural language. It is read-only and does not handle sending emails. **Strengths** - Good coverage of inbound use cases: list emails, get email details, list/get attachments, list/get domains. - JSON output enables structured responses and further automated processing by the assistant. - Command set is simple and well-aligned with common queries about “new emails”, “latest email”, and attachments. **Limitations & Risks** - Inbound-only: cannot send emails or manage outbound campaigns; limited to what Resend has received. - Dependent on correct Resend configuration (inbound routing, API key env var). Misconfiguration means the skill will appear “empty”. - Handles potentially sensitive content (private emails and attachments), so privacy and data-handling policies must be strictly followed. - Email IDs are UUIDs; referencing a specific message often requires listing then selecting an ID, which can add an extra step. **Recommended Scenarios** - You are already using Resend for inbound routing and want the assistant to check for new messages, show the latest email, or surface attachments. - You need to inspect domain and DNS setup for Resend inbound domains via natural-language queries. - You want to build higher-level workflows (summarization, extraction, triage) on top of structured inbound email data without implementing direct API calls yourself.