everymail Skill
通过共享的 EveryInfra 密钥使用 EveryMail 事务邮件 REST API。当用户需要查询邮件功能或配额、发送或定时事务邮件、提交批量任务、取消定时消息、查看投递事件,或配置授权发送域名和 webhook 时使用。
安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。
技能指令原文(SKILL.md)
EveryMail
EveryMail is REST-only in the current plugin. Do not invent an MCP tool for it. Use
https://api.everyinfra.com with an Authorization: Bearer header. In Claude the plugin's API key setting reaches only the MCP
server, so ask the user how they want to supply the key for REST calls; never read it from a file
or an environment variable.
- Read
GET /api/v1/email/catalogand, when authenticated,GET /api/v1/email/usage. - For a single message, use
POST /api/v1/email/sendwith catalog-declared fields. Recipients are
counted across to, cc and bcc; the API does not accept arbitrary from, headers or
attachments.
- Use
POST /api/v1/email/batchfor a true batch. Scheduled messages must use the single-send
endpoint so cancellation and refunds remain unambiguous.
- 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.
- 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.