Agentmail Toolkit
CheckedAgentmail Toolkit automates email workflows by triggering actions based on incoming emails, streamlining processes and boosting efficiency.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add agentmail-to/agentmail-skills --skill agentmail-toolkit -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
agentmail-to
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned agentmail-to/agentmail-skills at e0db938ca1.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- e0db938ca1
- Manifest
- agentmail-toolkit/SKILL.md
- Scanned
- 1 file, 142 lines
About this skill
What it does
The Agentmail Toolkit enables AI agents to manage email workflows, including sending, receiving, and organizing emails. It provides pre-built tools that can be integrated into popular agent frameworks like Vercel AI SDK, LangChain, Clawdbot/Pi Agent, OpenAI Agents SDK, LiveKit Agents, and others. This allows your agent to automate tasks related to email communication and streamline processes. The Node toolkit includes draft functionality not available in the Python version.
When to use it
- Automating responses to common customer inquiries via email.
- Creating an AI assistant that can manage a user's inbox, filtering important emails.
- Building an agent capable of sending automated notifications or reminders.
- Integrating email functionality into a voice-based AI agent (using LiveKit Agents).
- Developing agents to handle internal communication and task management through email.
Key capabilities
- Inbox Management: Create, list, get details of, and delete email inboxes.
- Email Sending: Send emails using the
send_messagetool. - Framework Integration: Supports integration with Vercel AI SDK, LangChain, Clawdbot/Pi Agent, OpenAI Agents SDK, and LiveKit Agents.
- Drafts (Node Toolkit Only): The Node toolkit includes tools for managing email drafts.
Example prompts
- "Create a new inbox called 'Customer Support'."
- "Send an email to [email protected] with the subject 'Meeting Confirmation' and body 'Hi John, just confirming our meeting tomorrow at 2pm.'"
- "List all of my inboxes."
Tips & gotchas
- API Key: You must set your
AGENTMAIL_API_KEYas an environment variable to use this toolkit. Obtain the key from console.agentmail.to. - Framework Specifics: Integration methods vary depending on the agent framework you are using (e.g., Vercel AI SDK vs. LangChain). Refer to the appropriate documentation for your chosen framework.
- Toolkit Differences: The Node and Python toolkits offer different sets of tools; specifically, the Node toolkit includes draft functionality while the Python version does not.