In short:
ak-emailreuses what you already said about the recipients, message, CTA and brand voice, only asks about important missing parts, then writes the subject, preview, body and CTA. The default result is a draft file, sent to no one. Sending or scheduling only happens with an authorized sending tool and complete, exact details.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need a newsletter, a cold email, a drip sequence or the design of an automated flow with branches.
flowchart LR
A["Email request"] --> B["ak-email"]
B --> C["Draft file or flow design"]
C --> D["Stop, nothing sent"]
C --> E["Send or schedule through an authorized tool"]
E --> F["Check the provider's receipt"]Four concepts to know:
| Concept | Question | Example |
|---|---|---|
| Job type | What do you need written? | newsletter for a newsletter, cold for a first cold email, launch for a launch, nurture for nurturing leads |
| flow or sequence | Do you need a branching flow diagram, or full copy for every email? | flow cart produces an abandoned-cart flow design with a "bought, so exit" branch; sequence welcome produces one ready-written file per email |
| A draft is not a send | Has this file reached anyone? | The welcome flow design sits in a file; nobody received it, and no flow was turned on in your email platform |
| Gate before sending | What does it take to send or schedule? | An authorized sending tool, final content, a recipient list, a sending account, a send time with time zone such as 9:00 on 10/28 Asia/Saigon time |
Requirements you include, such as an unsubscribe link, consent to receive mail, suppression lists and recipient segments, are kept unchanged in the draft and when sending.
Sample prompt for a monthly newsletter:
/ak-email newsletter The October newsletter for customers of <product name>.
Recipients: customers on a paid plan.
Message: 2 new features and one quick tip.
CTA: open the new features page.
Keep the unsubscribe link at the bottom of the email.This skill has no flags.
Below is the detailed version: the run flow, 5 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-email: newsletters, sequences and automated flows, drafts by default" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-email". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-email
