daily-digest
Skill0 starsChanged 7 months agoMITView on GitHub
Generates a personalized daily briefing from project data. Use when user says "daily digest", "morning briefing", "what should I focus on", "give me my digest", "what's important today". Requires discovery-dashboard for full functionality.
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
- prateekjain/ChiefOfStaff★ 4same name
- razbakov/skills★ 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 repository37 other files it gives its agents.
- ablation-study-frameworkSkill
- async-http-websocket-patternsSkill
- brain-dumpSkill
- chaos-controlled-behavior-systemSkill
- database-reset-and-seedSkill
- duckdb-analytics-layerSkill
- event-driven-backtest-engineSkill
- event-study-full-pipelineSkill
- event-study-stats-suiteSkill
- failure-learning-systemSkill
- fastapi-sse-live-dashboardSkill
- goal-task-decompositionSkill
- high-information-gain-interviewerSkill
- idea-extraction-batch-pipelineSkill
- idea-grouping-taxonomySkill
- interview-belief-extractorSkill
- journal-captureSkill
- journal-reviewSkill
- keyword-filter-frameworkSkill
- langgraph-agentic-pipelineSkill
- llm-as-judge-eval-frameworkSkill
- multi-tab-dashboard-rendererSkill
- multi-tier-memory-systemSkill
- parquet-storage-with-walSkill
- project-insightsSkill
- pydantic-typed-config-loaderSkill
- quality-trend-detectionSkill
- research-gap-finderSkill
- safe-commitSkill
- simtom-knowledge-isolationSkill
- statistical-signal-detectionSkill
- streaming-dataset-pipelineSkill
- structured-data-extraction-pipelineSkill
- structured-logging-setupSkill
- system-health-monitoringSkill
- textual-tui-reactiveSkill
- vector-db-ingestionSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
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 20
Read your journal file (JSONL format) — last 7 days of entries.
“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
Generates a concise daily briefing by reading journal entries, project data, and open tasks to surface the highest-priority items.
Instructions
Step 1: Read recent journal entries
Read your journal file (JSONL format) — last 7 days of entries.
Step 2: Gather project state
For each active project, check:
- Open action_items from brainstorm entries
- Pending next_steps from progress entries
- Unresolved decisions older than 14 days
- Any predictions past their resolution date
Step 3: Generate the digest
Structure as follows:
Priority Tasks
- Pull action_items from recent brainstorms and next_steps from progress
- Group by project
- Highlight time-sensitive or blocking items
Overdue Items
- Predictions past resolution date without outcome
- Projects with 0 entries in 7+ days
- Old unresolved decisions
Pattern Alerts
- Same anti-pattern appearing 2+ times this week
- Decisions without reflections in any project
- Projects with lots of brainstorms but no progress entries (ideas without execution)
Step 4: Deliver as concise pulse
10-15 lines maximum. Lead with the most actionable items. Skip empty sections — don't generate noise.
Example Output
Daily Digest — Mar 9, 2026
PRIORITY TASKS:
- [my-app] Fix response verbosity — logging when user asked for advice
- [tools] Finish remaining edge analyses
- [research] Test autoresearch repo
OVERDUE:
- Prediction "50 users by March" resolves this week — no outcome logged
PATTERNS:
- 4 projects touched this week, 3 went dark
- my-app has 5 brainstorms, 0 progress entries — shipping gapCustomization
Edit the project list and journal path to match your setup. The digest format is intentionally minimal — extend the sections if you need more detail.
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.

