Skill Market

agentmail

Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to).

GitHub
githubcommunityaiai-agentai-agentsanthropicchatgptclaude
0.0
0 installs245.9K GitHub starsby NousResearch

Skill Introduction

Overview
Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to).

Core value

Turns reusable Testing know-how into an installable skill, helping users complete github, community, ai, ai-agent work faster.

Target users

  • Developers, testers, and maintainers who handle Testing tasks in Focus Code.
  • Teams that already trust workflows or content from NousResearch.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, ai, ai-agent that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Testing, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, ai, ai-agent, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install agentmail-698fb8
View source

Detail Preview

SKILL.md

Primary filemarkdown5 KB

name: agentmail description: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. hermes-agent@agentmail.to). version: 1.0.0 platforms: [linux, macos, windows] metadata: hermes: tags: [email, communication, agentmail, mcp] category: email

AgentMail — Agent-Owned Email Inboxes

Requirements

  • AgentMail API key (required) — sign up at https://console.agentmail.to (free tier: 3 inboxes, 3,000 emails/month; paid plans from $20/mo)
  • Node.js 18+ (for the MCP server)

When to Use

Use this skill when you need to:

  • Give the agent its own dedicated email address
  • Send emails autonomously on behalf of the agent
  • Receive and read incoming emails
  • Manage email threads and conversations
  • Sign up for services or authenticate via email
  • Communicate with other agents or humans via email

This is NOT for reading the user's personal email (use himalaya or Gmail for that). AgentMail gives the agent its own identity and inbox.

Setup

1. Get an API Key

2. Configure MCP Server

Add to ~/.hermes/config.yaml (paste your actual key — MCP env vars are not expanded from .env):

mcp_servers:
  agentmail:
    command: "npx"
    args: ["-y", "agentmail-mcp"]
    env:
      AGENTMAIL_API_KEY: "am_your_key_here"

3. Restart Hermes

hermes

All 11 AgentMail tools are now available automatically.

Available Tools (via MCP)

ToolDescription
list_inboxesList all agent inboxes
get_inboxGet details of a specific inbox
create_inboxCreate a new inbox (gets a real email address)
delete_inboxDelete an inbox
list_threadsList email threads in an inbox
get_threadGet a specific email thread
send_messageSend a new email
reply_to_messageReply to an existing email
forward_messageForward an email
update_messageUpdate message labels/status
get_attachmentDownload an email attachment

Procedure

Create an inbox and send an email

  1. Create a dedicated inbox:
    • Use create_inbox with a username (e.g. hermes-agent)
    • The agent gets address: hermes-agent@agentmail.to
  2. Send an email:
    • Use send_message with inbox_id, to, subject, text
  3. Check for replies:
    • Use list_threads to see incoming conversations
    • Use get_thread to read a specific thread

Check incoming email

  1. Use list_inboxes to find your inbox ID
  2. Use list_threads with the inbox ID to see conversations
  3. Use get_thread to read a thread and its messages

Reply to an email

  1. Get the thread with get_thread
  2. Use reply_to_message with the message ID and your reply text

Example Workflows

Sign up for a service:

1. create_inbox (username: "signup-bot")
2. Use the inbox address to register on the service
3. list_threads to check for verification email
4. get_thread to read the verification code

Agent-to-human outreach:

1. create_inbox (username: "hermes-outreach")
2. send_message (to: user@example.com, subject: "Hello", text: "...")
3. list_threads to check for replies

Pitfalls

  • Free tier limited to 3 inboxes and 3,000 emails/month
  • Emails come from @agentmail.to domain on free tier (custom domains on paid plans)
  • Node.js (18+) is required for the MCP server (npx -y agentmail-mcp)
  • The mcp Python package must be installed: pip install mcp
  • Real-time inbound email (webhooks) requires a public server — use list_threads polling via cronjob instead for personal use

Verification

After setup, test with:

hermes --toolsets mcp -q "Create an AgentMail inbox called test-agent and tell me its email address"

You should see the new inbox address returned.

References

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet