daily-digest
Skill4 starsChanged 7 months agoMITView on GitHub
Use this skill when the user asks for a daily summary, today's to-dos, "what's on my plate today", "daily digest", "daily-digest", "show my notifications", "pending PRs and issues". Requires Gitee MCP Server to be configured.
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
- deepakkamboj/personal-assistant-skillstheir own version, first seen Oct 11, 2026
- ric03uec/clawriumtheir own version, first seen Sep 8, 2026
- oshothebig/skillstheir own version, first seen Sep 8, 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
- prateekjain/ChiefOfStaff★ 4same name
- razbakov/skills★ 4same name
- deepakkamboj/personal-assistant-skills★ 1same 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 repository13 other files it gives its agents.
- close-issue-flowSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- implement-issueSkill
- merge-pr-checkSkill
- quick-fix-suggestionSkill
- repo-explorerSkill
- review-prSkill
- search-and-forkSkill
- search-reposSkill
- stale-pr-reminderSkill
- triage-issuesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
2
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 25
Use get_user_info to retrieve the currently authenticated user's information, used for filtering (e.g., only show tasks assigned to me).
- Very specific: line 29
Use list_user_notifications to get recent notifications:
- Distinctive: line 101
If there is nothing pending:
- Distinctive: line 113
If there are many repositories, prioritize time-sensitive items
“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
Note: If you have
mcporterinstalled locally, you should usemcporterto invoke the MCP tool instead of directly calling the MCP tool. ThemcporterCLI provides a more convenient interface and better error handling.
Daily Digest via Gitee MCP
Aggregate unread notifications, pending PRs, and open Issues from Gitee to generate a daily work summary.
Prerequisites
- Gitee MCP Server configured (tools:
list_user_notifications,list_repo_pulls,list_repo_issues,get_user_info) - Optional: user can provide a list of repositories to focus on (otherwise inferred from notifications)
Steps
Step 1: Get Current User Info
Use get_user_info to retrieve the currently authenticated user's information, used for filtering (e.g., only show tasks assigned to me).
Step 2: Fetch Unread Notifications
Use list_user_notifications to get recent notifications:
- Filter for unread notifications
- Categorize by type: PR-related, Issue-related, @mentions, comment replies
Step 3: Fetch Pending PRs
For repositories the user cares about (extracted from notifications or specified by the user), use list_repo_pulls:
- Filter for
state=openPRs - Focus on:
- PRs assigned to me for review
- My own PRs waiting for review
- PRs with new comments that need a reply
Step 4: Fetch Open Issues
Use list_repo_issues:
- Filter for
state=openIssues assigned to me - Filter for open Issues I created
Step 5: Generate Daily Digest
# Daily Work Digest
📅 [date] 👤 [username]
---
## 📬 Unread Notifications ([N])
### @Mentions
- [repo] [Issue/PR title] - [notification summary]
### PR Comments
- [repo] PR #N [title] - [comment summary]
### Issue Updates
- [repo] Issue #N [title] - [update summary]
---
## 🔀 Pending PRs
### Needs My Review
| Repo | PR | Author | Updated |
|------|----|--------|---------|
| [repo] | #N [title] | [@author] | [time] |
### My PRs Awaiting Review
| Repo | PR | Status | Updated |
|------|----|--------|---------|
| [repo] | #N [title] | [Awaiting review / Has new comments] | [time] |
---
## 📋 My Open Issues
| Repo | Issue | Priority | Status |
|------|-------|----------|--------|
| [repo] | #N [title] | P1 | In progress |
---
## Today's Suggestions
**Handle first:**
1. [Most urgent item, e.g., a review request blocking someone else]
2. [Second priority item]
**Can defer:**
- [Low priority items]If there is nothing pending:
# Daily Work Digest
📅 [date]
All clear! No pending PRs, Issues, or unread notifications.Notes
- The digest focuses on information aggregation, not deep analysis
- If there are many repositories, prioritize time-sensitive items
- Notifications may span multiple repositories — group them clearly
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.

