agent-email-inbox
SkillUse when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted inbound email. Always use this skill when the user wants to receive emails and act on them programmatically, even if they do
Install
git clone https://github.com/resend/resend-skills.git ~/.claude/skills/agent-email-inboxWhat is agent-email-inbox?
Use when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted inbound email. Always use this skill when the user wants to receive emails and act on them programmatically, even if they don't mention "agent" — the skill contains critical security patterns (sender allowlists, content filtering, sandboxed processing) that prevent untrusted email from controlling your system.
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
Inherit all session tools
Declares no tool restrictions — inherits every session tool
~122 tokens of context used while enabled, before you invoke anything
Documentation
README · ~9 min readAI Agent Email Inbox
Overview
This skill covers setting up a secure email inbox that allows your application or AI agent to receive and respond to emails, with content safety measures in place.
Core principle: An AI agent's inbox receives untrusted input. Security configuration is important to handle this safely.
Why Webhook-Based Receiving?
Resend uses webhooks for inbound email, meaning your agent is notified instantly when an email arrives. This is valuable for agents because:
- Real-time responsiveness — React to emails within seconds, not minutes
- No polling overhead — No cron jobs checking "any new mail?" repeatedly
- Event-driven architecture — Your agent only wakes up when there's actually something to process
- Lower API costs — No wasted calls checking empty inboxes
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just skills.
Skillssimilar to this one
All skills →hook-development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse,
32.8K stars
access
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
32.8K stars
Claude-to-IM-skill
Bridge Claude Code / Codex to IM platforms — chat with AI coding agents from Telegram, Discord, or Feishu/Lark.
2.8K stars
MCP Servers
All mcp servers →slack-mcp-server
The most powerful MCP Slack Server with no permission requirements, Apps support, GovSlack, DMs, Group DMs and smart history fetch logic.
1.8K stars
yuna0x0-hackmd-mcp
Interact with your HackMD notes and teams seamlessly. Manage your notes, view reading history, and…
64 stars
gmail
Read emails, send messages, and manage labels in your Gmail account.
58 stars
Plugins
All plugins →discord
Discord messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /discord:access.
32.9K stars
telegram
Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.
32.9K stars
imessage
iMessage messaging bridge with built-in access control. Reads chat.db directly, sends via AppleScript. Manage pairing, allowlists, and policy via /imessage:access.
32.9K stars