Daily Recap
by @newageinvestments25-byte
Generate a daily recap/summary of all agent activity and save it to Obsidian. Use when asked to do a daily recap, end-of-day summary, or when a cron job fire...
clawhub install nai-daily-recapπ About This Skill
name: daily-recap description: Generate a daily recap/summary of all agent activity and save it to Obsidian. Use when asked to do a daily recap, end-of-day summary, or when a cron job fires for the nightly recap. Reads today's memory log, summarizes what was asked, researched, built, and done, then writes a journal entry to vault/daily-recap/YYYY-MM-DD.md with appropriate tags.
Daily Recap
At the end of each day, compile a summary of all agent activity and journal it into Obsidian.
Workflow
1. Read today's memory log: memory/YYYY-MM-DD.md (use today's date)
2. Read recent Discord messages (optional): scan the guild channels for today's messages if memory log is sparse
3. Compile the recap covering:
- What Ryan asked/requested
- Research performed and key findings
- Things built or created (files, skills, scripts, configs)
- Decisions made or outcomes reached
- Anything notable or worth remembering
4. Write the journal entry to vault/daily-recap/YYYY-MM-DD.md (create daily-recap/ folder if it doesn't exist)
5. Update memory: append a note to memory/YYYY-MM-DD.md that the recap was written
Journal Entry Format
Use this YAML frontmatter and structure:
---
date: YYYY-MM-DD
time: 23:59 ET
type: daily-recap
source: agent
tags: [daily-recap, ]
Daily Recap β YYYY-MM-DD
Requests & Tasks
Brief bullet per task Ryan asked about Research
Brief bullet per topic researched (include key finding if notable) Built / Created
Brief bullet per file, skill, config, or script created or modified Decisions & Outcomes
Any significant decisions made, options chosen, or conclusions reached Notable
Anything else worth remembering (errors, surprises, ideas flagged)
*Auto-generated by Atlas at end of day.*
Rules
vault/daily-recap/YYYY-MM-DD.md## Addendum section insteadCron Usage
This skill is designed to run nightly via a cron job (e.g., at 11:59 PM ET). When triggered by cron, run the full workflow silently and confirm completion in the cron delivery message.
π Constraints
vault/daily-recap/YYYY-MM-DD.md## Addendum section instead