Weekly Status

Step 3: Read diary entries

Build paths as Diary/YYYY/MM/YYYY-MM-DD.md for each file found. Call mcp__obsidian__read_multiple_notes with all paths (max 10 per batch — if N > 10, split into multiple calls). Set includeFrontmatter: false.

Step 4: Filter content

Parse each entry's bullet points:

• Include regular bullets (-) and checked tasks (- [x]) — these are completed work.
• Exclude unchecked tasks (- [ ]) from the summary. However, collect any - [ ] items that have a 📅 YYYY-MM-DD due date falling within the next 7 days (today+1 through today+7) for the "Next week" section.
• Skip empty or trivial entries (e.g., entries containing only "- ").

Step 5: Resolve links

GitHub links — match pattern https://github.com/[owner]/[repo]/(pull|issues)/[number]:

• For each unique URL, run via Bash:
  • PRs: gh pr view <URL> --json title,state --jq '"\\(.title) (\\(.state))"'
  • Issues: gh issue view <URL> --json title,state --jq '"\\(.title) (\\(.state))"'
• Skip malformed links with empty hrefs like [text]().
• If gh fails, fall back to WebFetch or include the raw link.

Wikilinks — match pattern [[note-name]]:

• Identify linked notes that are project/topic references (skip date references like [[2026-04-01]]).
• Read up to 5 unique linked notes via mcp__obsidian__read_note.
• Produce a 1-2 sentence summary of each linked note's content.

Step 6: Compose output

Last Week section:

• Title: ## Last Week
• Structure as a nested bullet list: top-level bullets are subject areas/themes, nested bullets are distinct tasks achieved within that subject area.
• Group by theme/project, not by day.
• Deduplicate: if the same activity spans multiple days, merge into one nested bullet describing the arc.
• Weave link context inline with valid Markdown hyperlinks: "Opened quickstart docs PR (#10, merged)" rather than listing raw URLs or plain text references. Every PR/issue mention must be a clickable [text](url) link.
• For wikilinked notes, include a parenthetical summary on first reference.
• Use past tense. Keep nested bullets concise (1-2 sentences each). Aim for 8-15 total task bullets across all subject areas (scale up slightly for larger ranges).

Next Week section (conditional):

• If any - [ ] tasks with due dates in the next 7 days were found, add ## Next Week after the Last Week section.
• List each task as a plain bullet (-), stripped of all Obsidian Tasks emoji (⏫, 🔼, 📅, ✅, etc.) and date annotations. Output only the task description text.
• If no upcoming tasks were found, omit this section entirely.

Step 7: Copy to clipboard as rich text

After displaying the composed Markdown in the conversation:

1. Write the exact Markdown output from Step 6 to /tmp/weekly-status.md using the Write tool.
2. Run via Bash: pandoc -f markdown -t html /tmp/weekly-status.md | wl-copy --type text/html && rm /tmp/weekly-status.md
3. Tell the user: "Formatted status copied to clipboard — paste directly into Gmail."

If the Bash command fails (e.g., wl-copy cannot connect to a Wayland display), inform the user that clipboard copy failed and they can copy the Markdown from the conversation instead. Do not retry.

Output template

## Last Week

- **Theme/Project Name**
  - Completed contribution or activity
  - Another task with PR context (title, merged/open)
- **Another Theme**
  - Activity with [[linked note]] context (brief summary)

## Next Week
- Task description without emoji or dates
- Another upcoming task

Edge cases

• Invalid argument: If the argument is not a positive integer, ignore it and default to 7.
• Cross-month range: List all month directories when the N-day range spans boundaries.
• Large N (> 30): Batch read_multiple_notes calls (max 10 per batch). Warn the user if many entries exist — output may be lengthy.
• No entries found: Tell the user no diary files exist for the range.
• Empty entries: Skip entries containing only whitespace or bare "- ".
• gh CLI unavailable: Fall back to WebFetch or include raw link without metadata.
• No upcoming tasks: Omit the "Next week" section entirely.
• Clipboard unavailable: If wl-copy fails (no Wayland session, SSH without display forwarding), inform the user and skip clipboard copy. The Markdown output in the conversation is still usable.