everymail — Claude Code skill for transactional email
This Claude Code skill manages transactional email through the EveryMail REST API. It checks quota, sends or schedules messages, reviews delivery events, and updates domain or webhook settings on request.
Apache-2.0 ★ 681 updated 2026-10-24
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a claude-codeWhat everymail does
everymail uses the EveryMail REST API to check available email operations and quota, send a single message or batch, schedule delivery, and cancel a scheduled message. It can also inspect delivery events and change settings for an authorized domain or webhook.
The API requires EVERYINFRA_API_KEY. Single messages go through /api/v1/email/send; batches use /api/v1/email/batch. A scheduled message uses the single-send endpoint so it can be cancelled. The API rejects arbitrary from values, headers, and attachments. The user must authorize the actual recipients and content before dispatch, and message bodies, verification codes, and reset links must stay out of logs.
What it helps with
- check EveryMail capabilities and quota
- send a transactional message or batch
- schedule a message and cancel its dispatch
- inspect email delivery events
- change authorized-domain or webhook settings
Example prompts for the agent
- Check the available EveryMail operations and quota.
- Send this transactional email to the listed recipients after I approve the recipients and content.
- Show the delivery events and cancel the scheduled message.
How to install everymail
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a claude-code2Manually: put the files in place
~/.claude/skills/everymail/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/everymail/
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a codex2Manually: put the files in place
.agents/skills/everymail/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a cursor2Manually: put the files in place
.cursor/skills/everymail/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install everyinfra/everyinfra-agent-plugins plugins/everyinfra/skills/everymail2Manually: put the files in place
.github/skills/everymail/SKILL.md1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a gemini-cli2Platform CLI
gemini skills install https://github.com/everyinfra/everyinfra-agent-plugins --path plugins/everyinfra/skills/everymailManually: put the files in place
.devin/skills/everymail/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about everymail
How do I install everymail in Claude Code?
Run npx skills add everyinfra/everyinfra-agent-plugins --skill everymail -a claude-code. The skill file is at ~/.claude/skills/everymail/SKILL.md.
What does everymail do?
It handles transactional email through the EveryMail API, including quota checks, single and batch sends, scheduled messages, delivery events, and domain or webhook settings.
What does everymail need to work?
It needs the EVERYINFRA_API_KEY credential for the EveryMail REST API. A user must authorize the recipients and message content before an email is sent.
Source text
SKILL.md · Apache-2.0
--- name: everymail description: Use EveryMail transactional-email REST APIs with the shared EveryInfra key. Use when the user asks to inspect email capabilities or quota, send or schedule a transactional email, submit a batch, cancel a scheduled message, inspect delivery events, or configure an authorized sending domain or webhook. --- # EveryMail EveryMail is REST-only in the current plugin. Do not invent an MCP tool for it. Use `https://api.everyinfra.com` with `Authorization: Bearer $EVERYINFRA_API_KEY`. 1. Read `GET /api/v1/email/catalog` and, when authenticated, `GET /api/v1/email/usage`. 2. For a single message, use `POST /api/v1/email/send` with catalog-declared fields. Recipients are counted across `to`, `cc` and `bcc`; the API does not accept arbitrary `from`, headers or attachments. 3. Use `POST /api/v1/email/batch` for a true batch. Scheduled messages must use the single-send endpoint so cancellation and refunds remain unambiguous. 4. Sending email is an external communication. Do not send until the user has authorized the actual recipients and content; preparing a draft is not authorization to dispatch it. 5. Do not log message bodies, verification codes or reset links. Report the returned `message_id`, status, billing and quota without exposing private content. Domain verification, webhook mutation and final dispatch are state-changing operations. Keep their scope exact and do not broaden API-key permissions automatically.
© everyinfra · Apache-2.0 · everyinfra/everyinfra-agent-plugins