How do I install the Agentmail skill?

Run npx skillmds@latest add gabrielmoreira/agentmail in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Agentmail skill do?

Use when an agent needs AgentMail CLI email inboxes. It is listed under AI & ML on SkillMD.

Is Agentmail safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentmail?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentmail free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Agentmail?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentmail by gabrielmoreira — Agent Skill

Name: Agentmail
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

AgentMail Skill

AgentMail gives an agent its own email inbox for sending mail, receiving replies, completing email OTP flows, and running inbound email loops. Use it for agent-owned inboxes, not a user's existing IMAP/SMTP mailbox.

Use the agentmail CLI first. Use MCP only when the harness expects MCP tools; use REST only when the CLI is missing a required operation.

When to Use

The agent needs an email address it owns.
The task involves email OTP flows, replies, threads, labels, or attachments.
The agent needs webhook or WebSocket delivery for inbound mail.

Prerequisites

Run commands through the terminal tool.
Install the CLI:

npm install -g agentmail-cli@latest

Export an API key:

export AGENTMAIL_API_KEY="am_..."

No API key yet? Use signup.md.

How to Run

Use --format json whenever another command or script needs IDs.

agentmail inboxes list --format json

Quick Reference

AgentMail agent reference: hosted copy.
AgentMail: product landing page.
Console: API keys and account management.
Docs: full product documentation.
signup.md: self-signup and OTP verification.
core.md: inboxes, messages, threads, labels, attachments.
webhooks.md: events to a public HTTPS server.
websockets.md: events to a local agent process.
mcp.md: MCP integration.

Procedure

Install agentmail-cli@latest and verify agentmail inboxes list --format json.
If no API key is available, complete signup.md.
Use core.md for inbox, send, read, reply, forward, label, thread, and attachment flows.
Add webhooks.md or websockets.md only when polling is not enough.

Pitfalls

Prefer AGENTMAIL_API_KEY over --api-key.
Never expose AGENTMAIL_API_KEY in prompts, logs, URLs, or committed files.
Use stable client_id values for retried create operations.
Prefer extracted_text or extracted_html for LLM input when present.
React to message.received, not messages the agent sent.

Verification

agentmail inboxes list --format json

---name: agentmaildescription: Use when an agent needs AgentMail CLI email inboxes.license: MIT--- # AgentMail Skill AgentMail gives an agent its own email inbox for sending mail, receiving replies, completing email OTP flows, and running inbound email loops. Use it for agent-owned inboxes, not a user's existing IMAP/SMTP mailbox. Use the `agentmail` CLI first. Use MCP only when the harness expects MCP tools; use REST only when the CLI is missing a required operation. ## When to Use - The agent needs an email address it owns. - The task involves email OTP flows, replies, threads, labels, or attachments. - The agent needs webhook or WebSocket delivery for inbound mail. ## Prerequisites - Run commands through the `terminal` tool. - Install the CLI: ```bash npm install -g agentmail-cli@latest ``` - Export an API key: ```bash export AGENTMAIL_API_KEY="am_..." ``` No API key yet? Use [signup.md](references/signup.md). ## How to Run Use `--format json` whenever another command or script needs IDs. ```bash agentmail inboxes list --format json ``` ## Quick Reference - [AgentMail agent reference](https://agentmail.md): hosted copy. - [AgentMail](https://agentmail.to): product landing page. - [Console](https://console.agentmail.to): API keys and account management. - [Docs](https://docs.agentmail.to): full product documentation. - [signup.md](references/signup.md): self-signup and OTP verification. - [core.md](references/core.md): inboxes, messages, threads, labels, attachments. - [webhooks.md](references/webhooks.md): events to a public HTTPS server. - [websockets.md](references/websockets.md): events to a local agent process. - [mcp.md](references/mcp.md): MCP integration. ## Procedure 1. Install `agentmail-cli@latest` and verify `agentmail inboxes list --format json`. 2. If no API key is available, complete [signup.md](references/signup.md). 3. Use [core.md](references/core.md) for inbox, send, read, reply, forward, label, thread, and attachment flows. 4. Add [webhooks.md](references/webhooks.md) or [websockets.md](references/websockets.md) only when polling is not enough. ## Pitfalls - Prefer `AGENTMAIL_API_KEY` over `--api-key`. - Never expose `AGENTMAIL_API_KEY` in prompts, logs, URLs, or committed files. - Use stable `client_id` values for retried create operations. - Prefer `extracted_text` or `extracted_html` for LLM input when present. - React to `message.received`, not messages the agent sent. ## Verification ```bash agentmail inboxes list --format json ```

Frequently asked questions

Agentmail