- 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
- Read today's memory log:
memory/YYYY-MM-DD.md(use today's date) - Read recent Discord messages (optional): scan the guild channels for today's messages if memory log is sparse
- 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
- Write the journal entry to
vault/daily-recap/YYYY-MM-DD.md(createdaily-recap/folder if it doesn't exist) - Update memory: append a note to
memory/YYYY-MM-DD.mdthat 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, <auto-detected topic tags>]
---
# 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
- Keep bullets concise — this is a summary, not a transcript
- Auto-detect tags from content (topics, tools, projects mentioned)
- Do NOT paraphrase Ryan's words in the Requests section — quote the gist faithfully
- If memory log is empty or missing, write "No activity logged" in each section rather than skipping the entry
- The entry file path must be:
vault/daily-recap/YYYY-MM-DD.md - Never overwrite an existing entry — if one exists, append a
## Addendumsection instead
Cron 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.