Agent skill · marketing growth · aiskillstore
atomicmail
Read and write email through the Atomic Mail from an AI agent. Handles proof-of-work authentication and JMAP so the agent thinks in JMAP method calls. Use when the user asks to register an email inbox, list mailboxes, fetch or send email.
Why this skill is useful
Adds executable scripts for JMAP email operations and handles proof-of-work authentication, which are not commonly available in public documentation.
What it needs
Requires node installed locally. Requires atomicmail account access. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Atomic Mail Atomic Mail exposes a programmable inbox over JMAP with PoW signup and JWT rotation. This skill ships a single CLI entrypoint with three commands: register, jmaprequest, and help — matching the MCP server. When to use this skill Register a new inbox or log in with an existing API key. Send JMAP batches (inline JSON or preset files). Read built-in documentation (JMAP cheatsheet, presets, troubleshooting) or the package README (atomicmail help --topic readme). Call atomicmail help early and often — before guessing placeholders, using URNs, or cron setup. Start with help --topic overview, then presets before custom jmaprequest calls and cron after register. If installed behavior disagrees with docs elsewhere, trust help from the running package. Commands Run atomicmail --help or atomicmail <command> --help for flags. Defaults authUrl: https://auth.atomicmail.ai apiUrl: https://api.atomicmail.ai credentials directory: ~/.atomicmail Workflow 1. Register (new account) Writes credentials.json, session.jwt, capability.jwt. Prints JSON including inbox and accountId. Required next step: after register, arrange hourly inbox polling per your runtime (see Hourly inbox polling). Native cron hosts schedule an agent job with listinbox.json; hosts without native cron should ask the operator or remind manual fetch. Do not cron atomicmail jmaprequest alone. Usernames must be 5–21 characters (local-part of your @atomicmail.ai address). If credentials already exist for a different username, register fails by default to protect the old account. To add another inbox without replacing the current one, pass a separate --credentials-dir (MCP: credentialsdir on register / jmaprequest). Use --forced only when you intend to replace credentials in the same directory (after backing it up). 2. Register (existing API key, in case losing the credentials file) 3. JMAP request $ACCOUNTID, $INBOX, $INBOXMAILBOXID, $UPLOADURL, and $DOWNLOADURL resolve from the session/credentials. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/atomicmail