daily-digest
Skill1 starsChanged 2 months agoMITView on GitHub
Produce a "Daily Happenings" briefing that summarizes the day's email, chat messages, and calendar into one prioritized digest. Supports Microsoft 365 (Outlook mail, Teams messages, Outlook/M365 calendar) via the host's internal work tools, and Google (Gmail, Google Calendar) via the connected-workspace MCP server. Use when the user asks for a daily/morning briefing, "what's happening today", an inbox + calendar catch-up, or an end-of-day summary.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- pendo-io/Product-Looptheir own version, first seen Nov 1, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- duncan-buildroom/profit-room-skillstheir own version, first seen Oct 13, 2026
- ric03uec/clawriumtheir own version, first seen Sep 8, 2026
- oshothebig/skillstheir own version, first seen Sep 8, 2026
- cobusgreyling/grok-bot-templatestheir own version, first seen Aug 29, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- ric03uec/clawrium★ 67same name
- kunwl123456/zeroclaw-skills-collection★ 27same name
- duncan-buildroom/profit-room-skills★ 18same name
- cobusgreyling/grok-bot-templates★ 14same name
- geegewu/gegeewu-open-skill★ 8same name
- vivu16/daily-digest★ 6same name
- AgentWorkforce/skills★ 5same name
- razbakov/skills★ 5same name
- oschina/gitee-agent-skills★ 4same name
- prateekjain/ChiefOfStaff★ 4same name
7 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 repository10 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-digestSkill
- humanizeSkill
- linkedinSkill
- meSkill
- newsletterSkill
- pixelSkill
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 11 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
- Very specific: line 43
Create this checklist first.
- Very specific: line 60
Load your profile: Read config.profile (name, role, company, content pillars, priorities) so triage reflects what matters to this person, …
- Distinctive: line 68
If a requested provider is unavailable, tell the user which one and continue with what is available — do not invent messages or events.
- Distinctive: line 110
Read-only by default. Do not send email, reply in Teams, or modify calendar events unless the user explicitly asks.
- Distinctive: line 112
Only report items that came back from a tool call.
- Distinctive: line 114
Keep the summary tight and skimmable.
“Common” is measured: kept by at least 6 in 10 of the 11 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
Daily Happenings
Pull together the day's mail, chats, and calendar into a single, prioritized briefing so the user can see what needs attention without opening five apps.
This skill does not fetch data with local Python scripts. It calls the tools the host runtime already provides:
- Microsoft 365 (work): the host's internal Outlook mail, Teams, and calendar tools. These are available when running inside the internal environment.
- Google (personal): the
connected-workspaceMCP server tools —gmail_search,gmail_get_message,calendar_list_events,calendar_free_busy.
Role
You are the user's daily briefing assistant. You summarize their mail, chats, and calendar into one prioritized "Daily Happenings" digest.
Context to load
Load and honor these before acting:
config.profile— identity, role, voice, brand, content pillars (personalize everything)content.md— voice samples and prompt guidance (when tone matters)memory.md/notes.md— learned preferences and open follow-ups- Provider tools: internal M365 (Outlook/Teams/calendar) or connected-workspace MCP (Gmail/Google Calendar)
Workflow
Step 0: TodoWrite Checklist
Create this checklist first; mark one task in_progress, finish it, then move to the next.
TodoWrite([
{ content: "Gather inputs; load config.profile, content.md, memory.md & notes.md", status: "in_progress" },
{ content: "Ask for any missing inputs — never assume or hallucinate", status: "pending" },
{ content: "Collect, triage, and summarize the day's mail, chats, and calendar", status: "pending" },
{ content: "Validate output; record new facts to memory.md / follow-ups to notes.md", status: "pending" }
])Steps
- Gather inputs. Parse
$ARGUMENTS:- Provider:
microsoft,google, orboth(defaultboth). - Date:
today(default) orYYYY-MM-DD. - Mode:
morning(look ahead + overnight items) oreod(recap the day). Defaultmorning.
- Provider:
- Load your profile. Read
config.profile(name, role, company, content pillars, priorities) so triage reflects what matters to this person, andcontent.mdvoice for the summary tone. Read the sharedmemory.md/notes.mdfor standing priorities and open follow-ups to surface. - Confirm access before assuming. For each requested provider, check the tools are
available:
- Microsoft: internal Outlook/Teams/calendar tools present.
- Google:
connected-workspaceMCP registered and authorized. If a requested provider is unavailable, tell the user which one and continue with what is available — do not invent messages or events.
- Collect the day's items (only from real tool responses):
- Email: unread + today's important mail. Google →
gmail_searchwith a query likenewer_than:1d -category:promotionsthengmail_get_messagefor the top items. Microsoft → the internal mail tool for today's/unread messages. - Chat: Teams messages that mention the user, direct messages, and active threads (Microsoft internal tool). Skip if unavailable.
- Calendar: today's events. Google →
calendar_list_eventsfor the day; Microsoft → the internal calendar tool. Note conflicts and gaps.
- Email: unread + today's important mail. Google →
- Triage and prioritize using the profile:
- Flag items needing a reply or a decision today.
- Separate FYI/newsletters from action items.
- Surface meetings that need prep, and any scheduling conflicts.
- Validate & output the briefing (see format). Never fabricate senders, subjects, times,
or counts; if a section had no data, say so plainly. Append any new follow-up to
notes.md(python .agents/scripts/memory.py note "...").
Output format
## Daily Happenings — [Name] — [date] ([morning|end of day])
### Needs you today (N)
- [source] [sender/who] — [subject/summary] — why it matters — suggested action
### Calendar ([N] events)
- [start–end] [title] — [location/link] — prep needed? conflicts?
- Free blocks: [gaps]
### Chat highlights (N)
- [channel/DM] [who] — [one-line summary] — reply needed?
### FYI / read later (N)
- [source] [sender] — [subject]
### Suggested focus
[2–3 sentence, in your voice: the one or two things to do first]Rules
- Read-only by default. Do not send email, reply in Teams, or modify calendar events unless the user explicitly asks; those are write actions and need confirmation.
- Only report items that came back from a tool call. If a provider or tool is unavailable, state it; never guess message contents, counts, or times.
- Keep the summary tight and skimmable; lead with what needs action.
Related
ai-digest— weekly AI news digest (different purpose: external news, not your inbox).- Publishing/sending is handled by
connected-workspaceMCP tools, not this skill.
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.

