daily-digest
Skill4 starsChanged 8 months agoMITView on GitHub
Generate a portfolio-wide daily briefing and update Notion
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
- oschina/gitee-agent-skills★ 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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brand-setupSkill
- deploySkill
- ecosystem-scoutSkill
- process-approvalsSkill
- publish-contentSkill
- qa-checkSkill
- send-outreachSkill
- submit-for-approvalSkill
- venture-bootstrapSkill
- venture-health-checkSkill
- venture-intakeSkill
- venture-staffingSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
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 24
Read portfolio/registry.md to get all active ventures (exclude KILLED, PAUSED, MATURE).
- Distinctive: line 41
If the venture repo isn't cloned locally, use:
- Very specific: line 84
Write the digest to digests/daily/{YYYY-MM-DD}.md.
- Distinctive: line 88
Search for the "Digests" database in Notion and create a new page:
- Distinctive: line 97
If this was triggered manually (not by scheduled task), display the digest to the founder.
“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 Digest — Portfolio Briefing
Generate the founder's daily briefing across all ventures.
Step 1: Read Portfolio State
Read portfolio/registry.md to get all active ventures (exclude KILLED, PAUSED, MATURE).
Step 2: Gather Venture States
For each active venture, read its state. Use Bash to pull latest if the repo is cloned locally:
cd $PROJECTS_DIR/{slug} && git pull --quiet 2>/dev/nullThen read:
CLAUDE.md— for venture context and current focusplans/current.md— for active plan and task statusmetrics/— for latest KPIs (if any files exist)decisions/— for recent decisions (check dates)docs/changelog.md— for recent changes
If the venture repo isn't cloned locally, use:
gh repo clone {user}/{slug} $PROJECTS_DIR/{slug} -- --quiet 2>/dev/nullStep 3: Generate Digest
Spawn the reporter agent to generate the digest:
Generate a daily portfolio digest for today ({date}).
Data for each venture:
{pass the state data gathered in Step 2}
Use this format:
# Daily Briefing — {date}
## Decisions Needed
- [Venture] What needs founder input and why
## Progress Today
| Venture | Stage | Activity | Result |
|---------|-------|----------|--------|
## Key Metrics
| Venture | MRR | Users | Health | Trend |
|---------|-----|-------|--------|-------|
## Blockers
- [Venture] What's blocked and what would unblock it
## Tomorrow's Plan
- [Venture] What agents will work on next
If there are no decisions needed, omit that section.
If a venture has no metrics yet (early stage), show "—" for metrics.
Keep it concise — the founder should be able to scan this in 2 minutes.Step 4: Save Digest
Write the digest to digests/daily/{YYYY-MM-DD}.md.
Step 5: Update Notion
Search for the "Digests" database in Notion and create a new page:
- Title: "Daily Briefing — {date}"
- Type: Daily
- Content: The full digest in Notion markdown format
Also update the "Ventures" database entries with latest health scores and activity dates.
Step 6: Display to User
If this was triggered manually (not by scheduled task), display the digest to the founder.
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.

