daily-email-summary
Skill0 starsChanged 2 months agoMITView on GitHub
Fetch the last 24 hours of email and send a summary email back to the user. Use when the user invokes /daily-email-summary or asks to summarize today's/recent emails.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-briefSkill
- draft-letterSkill
- meeting-notesSkill
- onboard-brainSkill
- person-briefSkill
- plan-daySkill
- process-inboxSkill
- recallSkill
- rememberSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If no email connector is available, say so and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Using the email connector available in this session (for Gmail: search_threads, get_thread, get_message, send_message), find all emails received in the last 24 hours (from now, going back one day) in the inbox.
For each email, note the sender, subject, and a one to two sentence summary of the content. Group the summary by sender or topic where it makes sense, and call out anything that looks like it needs a reply or action from the user (e.g. OTPs, security alerts, interview requests, deadlines), with a suggested next step. Keep the whole summary concise and scannable — use short bullet points, not long paragraphs.
Exclude any thread that is itself a previous "Daily Email Summary" email sent by this skill.
Then send this summary as a new email to {{OWNER_EMAIL}} with subject "Daily Email Summary - <today's date>". Do not reply to or modify any of the original emails — only read them and send the one summary email.
If no email connector is available, say so and stop.
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.

