Skip to content
TrustedSkillsbeta
Back to all skills

Agent Mail

Listed
dicklesworthstone·vlatest·agents

Dicklesworthstone's agent-mail automatically drafts, sends, and organizes emails based on your specified instructions and context.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill agent-mail -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dicklesworthstone

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 3 places.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • skills/agent-mail/references/FIX-MCP-CONFIG.md:105remote script piped into a shell
      curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/mcp_agent_mail/main/scripts/install.sh" | bash -s -- --yes
    • skills/agent-mail/references/INSTALL.md:17remote script piped into a shell
      curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/mcp_agent_mail/main/scripts/install.sh?$(date +%s)" | bash -s -- --yes
    • skills/agent-mail/references/INSTALL.md:23remote script piped into a shell
      curl -fsSL ... | bash -s -- --port 9000 --yes

  • 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

    Only contacts known or declared hosts: 127.0.0.1, raw.githubusercontent.com.

    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.

    Hosts contacted

    127.0.0.1localraw.githubusercontent.comsource host

  • 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.

  • Pinned to a commit: passed

    Scanned dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations at 4d332440c3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
4d332440c3
Manifest
skills/agent-mail/SKILL.md
Scanned
10 files, 1,838 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

Agent Mail provides a coordination layer for coding agents using HTTP and FastMCP, enabling them to communicate and collaborate effectively. It allows agents to draft, send, and organize emails (messages) within a project namespace, ensuring they avoid conflicts and maintain context during development. This system utilizes memorable agent identities, file reservations, threaded messaging with importance levels, and facilitates direct communication between humans and agents.

When to use it

  • Collaborative Coding: When multiple AI agents are working on the same codebase or related files.
  • Context Management: To ensure all agents have access to the necessary information and avoid missing critical updates.
  • Human-Agent Communication: When a human needs to directly communicate with an agent for clarification or guidance.
  • File Editing Coordination: When multiple agents need to edit files concurrently, preventing overwrites and conflicts.

Key capabilities

  • Memorable Agent Identities: Agents are assigned names like "GreenCastle" for easy identification.
  • Advisory File Reservations (Leases): Agents can reserve files before editing to signal intent.
  • Threaded Messaging: Messages are organized into threads with importance levels (low, normal, high, urgent).
  • Contact Policies: Control who can message whom within a project (open, auto, contacts_only, block_all).
  • Human Overseer Messaging: Allows direct communication between humans and agents.
  • Pre-commit Guard: Optionally blocks commits that conflict with file reservations.
  • Searchable Message History: Provides a searchable record of all messages exchanged within a project.

Example prompts

While Agent Mail is primarily an agent coordination tool, examples of interaction might include:

  • "Reserve the files src/auth/**/*.ts and src/middleware/auth.ts for editing."
  • "Send a high-importance message to BlueLake regarding the authentication module implementation."
  • "What are the recent messages related to the 'database connection' thread?"

Tips & gotchas

  • Project Key: Ensure agents working on related tasks use the same project_key for proper coordination.
  • File Reservations: Always reserve files before editing to prevent conflicts with other agents.
  • Server Startup: The server is started using ./scripts/run_server_with_token.sh in the ~/projects/mcp_agent_mail directory, and accessed via http://127.0.0.1:8765/mail.