Daily Summary

When to use

The user wants a synthesis of recent daily-note activity — usually because they're returning to the vault after a gap, preparing a weekly review, or hunting for ideas worth expanding. The horizon defaults to 7 days; the user may specify (/daily-summary 30d).

Procedure

1. Call vault_info to confirm the vault is accessible and to learn the daily-note pattern.
2. Call list_daily_notes(since="7d") (or the user-specified horizon). If fewer than 3 daily notes returned, tell the user and stop — there's nothing to synthesize.
3. Call read_notes_batch(paths=[...returned paths]) with the daily-note paths. Respect the 200K-char cap.
4. Identify themes. Aim for 3–7 named threads, each with a one-sentence claim and 2–4 supporting daily-note references.
5. For each theme, pick 1–2 wikilinks from the daily notes that look central. Use find_related if a theme would benefit from atomic-note context.
6. Draft a synthesis note. Path: Syntheses/Daily summary {YYYY-MM-DD to YYYY-MM-DD}.md. Frontmatter: created: , tags: [synthesis, daily-summary], period_start, period_end. Body uses the template in §Output format.
7. Surface the proposed body to the user IN CHAT. Wait for approval (or --unattended).
8. After approval, call create_note(path=..., body=..., frontmatter=..., confirm=true).
9. Reply with the new path and a 2-sentence top-line.

Output format

# Daily summary, {YYYY-MM-DD} to {YYYY-MM-DD}

## Threads

### {Theme 1 — short imperative sentence}
{One paragraph of synthesis, referencing daily notes with wikilinks.}
- [[Daily Notes/YYYY-MM-DD]]: {short pull-quote or paraphrase}
- ...

### {Theme 2 ...}

## Loose ends
- {Question I left unresolved} — see [[Daily Notes/YYYY-MM-DD]]

## Sources
- [[Daily Notes/YYYY-MM-DD]] ... (every daily note read, in chronological order)

Anti-patterns

• Don't summarize line-by-line. Surface threads, not transcripts.
• Don't invent themes the daily notes don't actually contain. If the period is sparse, say so.
• Don't edit the source daily notes — read-only.
• Don't run more than one find_related per theme. The synthesis is from what the user already wrote, not from new search.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: bettyguo
• Source: bettyguo/obsidian_mcp
• License: MIT

Install and usage instructions live in the source repository linked above.