Skip to main content
Commands, package names, and image names on this page come from the open-source project that Mibyan Desktop is built on, and can differ from the Mibyan Desktop installer. For the supported Mibyan install and update path, see Install and update.
Use when an agent needs AgentMail CLI email inboxes.

​
Skill metadata

​
Reference: full SKILL.md

The following is the complete skill definition that Mibyan loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

​
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:
  • Export an API key:
No API key yet? Use signup.md.

​
How to Run

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

​
Quick Reference

​
Procedure

  1. Install agentmail-cli@latest and verify agentmail inboxes list --format json.
  2. If no API key is available, complete signup.md.
  3. Use core.md for inbox, send, read, reply, forward, label, thread, and attachment flows.
  4. 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