Two Claude Code skills for working with the 3AVA Mail email API platform — a self-hosted, Resend-compatible transactional + marketing email system.
| Skill | Purpose |
|---|---|
mail3ava-usage |
Use the API — send emails, run campaigns, manage contact lists, verify domains, register webhooks. |
3ava-mail-docs |
Maintain the documentation site at docs.3ava.com (Astro Starlight) — write pages, build, deploy. |
3AVA Mail is a self-hosted email API that mirrors the Resend wire format. You bring your own SMTP relays, IP pools, and Postgres+Redis; the platform handles sending, IP warmup, list verification, AI-assisted campaign tooling, bounce/complaint handling, and webhooks.
- Public docs: https://docs.3ava.com/
- API base URL:
https://mail.3ava.com/api - Drop-in Resend SDK support (just override
baseUrl)
Drop the skill folders into your global Claude Code skills directory:
git clone https://github.com/nikvb/3ava-mail-skills.git /tmp/3ava-mail-skills
mkdir -p ~/.claude/skills
cp -r /tmp/3ava-mail-skills/mail3ava-usage ~/.claude/skills/
cp -r /tmp/3ava-mail-skills/3ava-mail-docs ~/.claude/skills/
rm -rf /tmp/3ava-mail-skillsOr one-liner per skill:
mkdir -p ~/.claude/skills/mail3ava-usage && \
curl -sL https://raw.githubusercontent.com/nikvb/3ava-mail-skills/main/mail3ava-usage/SKILL.md \
-o ~/.claude/skills/mail3ava-usage/SKILL.mdmkdir -p ~/.claude/skills/3ava-mail-docs && \
curl -sL https://raw.githubusercontent.com/nikvb/3ava-mail-skills/main/3ava-mail-docs/SKILL.md \
-o ~/.claude/skills/3ava-mail-docs/SKILL.mdAfter install, restart Claude Code (or any new session sees the skills automatically).
The mail3ava-usage skill ships with a placeholder API key. Replace it with your real one:
sed -i.bak 's|am_YOUR_API_KEY_HERE|am_<your-actual-key>|g' \
~/.claude/skills/mail3ava-usage/SKILL.mdGet a key from the dashboard at https://mail.3ava.com/ → API Keys → Create.
Tip: For shared development machines, prefer storing the key in
~/.bashrcasMAIL3AVA_KEY=...and edit the skill to reference$MAIL3AVA_KEYinstead of the literal value.
In any Claude Code session, just describe what you want:
- "Send a test email through mail.3ava.com to nick@example.com"
- "Create a campaign on hi2b.com for the spring newsletter"
- "Add a docs page for the new /v2/inbound endpoint"
- "Why is the docs build failing?"
Or invoke explicitly:
/mail3ava-usage send
/mail3ava-usage campaign
/3ava-mail-docs add-page
/3ava-mail-docs deploy
3ava-mail-skills/
├── README.md # this file
├── mail3ava-usage/
│ └── SKILL.md # API usage — endpoints, conventions, examples
└── 3ava-mail-docs/
└── SKILL.md # Docs maintenance — Astro Starlight, MDX gotchas
Each skill is a single SKILL.md file with YAML frontmatter (name, description, allowed-tools, argument-hint) followed by the skill body. Claude Code's harness reads everything in ~/.claude/skills/<name>/SKILL.md and surfaces the skill in the tool list.
The name, description, and argument-hint fields control how the skill is presented to the model:
name: invoked as/<name>in a chatdescription: governs auto-invocation — the model picks this skill when the user's message matches the descriptionallowed-tools: comma-separated whitelist of tools the skill body can callargument-hint: shown in the slash-command picker
See Anthropic's skill format docs for the canonical spec.
MIT — use, modify, redistribute freely. These skills are operational documentation for a private platform; the format and conventions are reusable for any similar email API.
PRs welcome. The skills evolve as the underlying platform adds endpoints — open an issue if you spot a stale curl example or a missing endpoint.