Daily Recap
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly coherent for creating an Obsidian daily recap, but it also allows silent scheduled runs that may scan broad Discord guild channels without clear scope or approval.
Use this skill only if you are comfortable with automated daily summaries being written to Obsidian. Before enabling cron or Discord access, restrict it to known paths and specific channels, and make sure it will not summarize private or unrelated messages.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could read unrelated Discord channel messages during a recap, including on scheduled runs, exposing more workspace communication than the user may expect.
This requests access to Discord guild content without specifying an account, guild, channel allowlist, message type, consent boundary, or why non-agent messages are needed for a recap of agent activity.
Read recent Discord messages (optional): scan the guild channels for today's messages if memory log is sparse
Limit Discord access to explicit guilds/channels and agent-related messages, require user approval before scanning, and disclose any required Discord credential or integration scope.
If connected to a cron job, the agent may read logs, optionally inspect Discord messages, and write recap files without interactive review each time.
The artifact explicitly supports autonomous scheduled execution. It does not install persistence itself, but it instructs silent completion of the workflow when triggered.
This skill is designed to run nightly via a cron job ... When triggered by cron, run the full workflow silently
Use cron only if you intentionally want unattended recaps, and pair it with narrow data-source configuration and logging of what sources were read.
Daily recap files may preserve personal requests, research, created files, decisions, and other activity details in a persistent vault.
The skill reads persistent memory and creates durable summaries in Obsidian and the memory log. This is central to the stated purpose, but the resulting notes may retain sensitive activity details.
Read today's memory log: `memory/YYYY-MM-DD.md` ... Write the journal entry to `vault/daily-recap/YYYY-MM-DD.md` ... Update memory: append a note
Review the vault and memory locations, avoid including secrets or private third-party content, and consider redaction rules for sensitive topics.