send-email
Skill65 starsChanged 7 months agoMITView on GitHub
Send email to [Your Name] via Resend API. Use when user says "email me", "send me an email", "send to my inbox", "email this to me", "send this to my email", or wants something delivered to email. Locked to [Your Name]'s gmail. NOT for Slack messages, DMs, or any other messaging. Do NOT use for "message me", "DM me", or "send to Slack".
- Reads credentials
28 other projects use a version of this.
Adopted by
Most recently taken up by
- brennantim/claude-skillstheir own version, first seen Nov 16, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- freejam099-alt/Edge-Aitheir own version, first seen Oct 25, 2026
- aaronjmars/miroshark-aeontheir own version, first seen Oct 21, 2026
- aeonfun/aeontheir own version, first seen Oct 20, 2026
- jeffliu05042/send-email-skilltheir own version, first seen Oct 20, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
aaronjmarsSkillauto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +10 more from aaronjmars
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- google-ai-edge/gallery★ 25ksame name
- floatpane/matcha★ 1.2ksame name
- jegly/Box★ 1ksame name
- aaronjmars/aeon★ 794same name
- aeonfun/aeon★ 793same name
- microsoft/vscode-java-pack★ 357same name
- refly-ai/refly-skills★ 204same name
- MoizIbnYousaf/marketing-cli★ 33same name
- aaronjmars/miroshark-aeon★ 20same name
- MiroShark/miroshark-aeon★ 20same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- buildSkill
- debugSkill
- financial-advisorSkill
- generate-image-openaiSkill
- good-morningSkill
- pdfSkill
- planeSkill
- reply-xSkill
- researchSkill
- search-historySkill
- simplify-julesSkill
- skill-creatorSkill
- stop-slopSkill
- thinkSkill
- watch-contactsSkill
- wrap-upSkill
- writeSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 60
Before sending, check how many emails have been sent today:
- Distinctive: line 68
If at 3/3, inform the user the limit is hit and suggest Slack as an alternative.
- Very specific: line 73
Markdown content: Write clean markdown. build-digest-email.sh handles conversion.
- Distinctive: line 74
Length: No hard limit, but emails should be scannable.
- Distinctive: line 89
No manual key handling needed.
- Very specific: line 93
Every send (success or failure) is logged to ~/.claude/email-send-log.jsonl.
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Critical Constraints
- Recipient is hardcoded.
[your-email]. Cannot be changed. Cannot email anyone else. - Rate limit: 3 emails per calendar day. Exit code 2 = rate limit hit. Do not retry.
- From address:
Jules <playbook@[previous-domain]>(verified Resend sender, still active post-rebrand).
Sending Email
Two paths: HTML (rich formatting via markdown pipeline) and plain text (quick notifications).
HTML email (structured content, reports, summaries)
Pipe markdown through build-digest-email.sh into jules-send-email.sh:
echo "## Summary\n\n- Point one\n- Point two\n\n**Key takeaway:** Thing." \
| bash .claude/scripts/build-digest-email.sh "Report Title" \
| bash .claude/scripts/jules-send-email.sh --subject "Subject Line" --html -build-digest-email.sh converts markdown to branded HTML with the caramel/cream template. Pass the report title as the first argument (appears in the header bar). Reads markdown from stdin, outputs HTML to stdout.
Plain text email (quick notes, reminders, notifications)
bash .claude/scripts/jules-send-email.sh --subject "Reminder" --body "Follow up with Michael from AITX this week."HTML from a file
bash .claude/scripts/jules-send-email.sh --subject "Subject" --html /path/to/body.htmlDry run (preview without sending)
bash .claude/scripts/jules-send-email.sh --subject "Test" --body "anything" --dry-runShows recipient, from address, subject, and today's send count. Does not consume a send.
When to Use HTML vs Plain Text
| Content | Path |
| Session notes, briefings, reports, summaries | HTML (markdown pipeline) |
| Simple reminders, quick notifications, one-liners | Plain text (--body) |
| Anything with headers, lists, tables, or code blocks | HTML (markdown pipeline) |
Rate Limit Check
Before sending, check how many emails have been sent today:
grep -c "\"date\":\"$(date +%Y-%m-%d)\"" ~/.claude/email-send-log.jsonl 2>/dev/null || echo 0Report to user: "X/3 emails sent today."
If at 3/3, inform the user the limit is hit and suggest Slack as an alternative.
Composing Guidance
- Subject lines: Specific and scannable. "Session Notes: Quiz Migration" not "Update". [Your Name] filters by subject.
- Markdown content: Write clean markdown.
build-digest-email.shhandles conversion. Tables, code blocks, headers, lists all work. - Length: No hard limit, but emails should be scannable. Use headers to break up long content.
- When writing raw HTML (not using the markdown pipeline): consult
references/html-best-practices.mdfor email client CSS constraints.
Error Handling
| Exit Code | Meaning | Action |
| 0 | Sent successfully | Report the email ID and today's count |
| 1 | Missing args, API key not found, or HTTP error | Check the error message. API key: container has RESEND_API_KEY in env; Mac uses 1Password (op://Dev Secrets/Quiz App - All Env/RESEND_API_KEY) |
| 2 | Daily rate limit (3/day) reached | Inform user. Suggest Slack. Do not retry. |
API Key Resolution
The send script uses RESEND_API_KEY from the environment. The overnight batch injects it via op read at startup. For manual runs, the service account token in the shell environment handles it automatically.
No manual key handling needed.
Send Log
Every send (success or failure) is logged to ~/.claude/email-send-log.jsonl. Each entry includes date, time, subject, HTTP status, and today's count. This is the rate limiter's data source.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

