// Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
| name | weekly-review |
| description | Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary". |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion |
Summarize the past week's daily entries into a weekly review note.
All private notes live in src/content/notes/private/ with flat structure (no subfolders).
YYYY-Www.md (ISO week number)2024-W02.md for week 2 of 2024Calculate the current ISO week:
Find date range for the week being reviewed (default: current week).
Search for all daily notes in the week's date range:
Glob: src/content/notes/private/YYYY-MM-DD.md
Filter to notes where date falls within the week.
Read each daily note found and extract:
Display to user:
question: "What were the main themes this week?"
header: "Themes"
options:
- label: "Auto-generate"
description: "Identify themes from daily entries"
- label: "Manual"
description: "I'll describe the themes"
If user chooses manual, gather their input.
Frontmatter:
---
title: "Week {N}, {YYYY}"
type: weekly
week: YYYY-Www
date: { week end date YYYY-MM-DD }
dailies:
- "[[YYYY-MM-DD]]"
- "[[YYYY-MM-DD]]"
private: true
---
Body structure:
## Week Summary
{user themes or auto-generated summary}
## Key Events
- {aggregated from Done Today sections}
## Learnings
- {consolidated from daily Learnings sections}
## Public Notes Created
- [[note-1]] - {brief context}
- [[note-2]] - {brief context}
## Wiki Health
- **Total pages:** {N} wiki, {N} sources
- **Added this week:** {N} notes, {N} sources
- **Issues found:** {summary or "none"}
- **MOC suggestions:** {top 3 or "none"}
Run a quick lint pass on the wiki as part of the weekly cadence. This catches issues early before they compound.
3.3.1 Quick Lint Scan
Use Grep and Glob to check for:
[[ in recently modified files, verify targets exist)3.3.2 MOC Gap Check (optional)
If the moc-curator cluster script is available, run:
python3 .claude/skills/moc-curator/scripts/cluster-notes.py --mode=moc-gaps
Summarize top 3 MOC suggestions (if any).
3.3.3 Format Results
Add a ## Wiki Health section to the weekly note:
## Wiki Health
- **Total pages:** {N} wiki, {N} sources
- **Added this week:** {N} notes, {N} sources
- **Broken links:** {count} ({list if any})
- **Low-tag notes:** {count}
- **Orphans this week:** {count}
- **MOC suggestions:** {top 3 or "none"}
- **Recommendation:** {e.g., "run /reviewing-notes for full audit" or "wiki is healthy"}
If no daily notes exist for the week, still offer to run just the wiki health check.
Present the generated weekly review:
question: "Does this weekly summary look good?"
header: "Review"
options:
- label: "Save"
description: "Create the weekly review file"
- label: "Edit"
description: "Make changes before saving"
Save to src/content/notes/private/{YYYY-Www}.md.
Confirm with:
Full weekly review template:
---
title: "Week N, YYYY"
type: weekly
week: YYYY-Www
date: YYYY-MM-DD
dailies:
- "[[2024-01-08]]"
- "[[2024-01-09]]"
- "[[2024-01-10]]"
- "[[2024-01-11]]"
- "[[2024-01-12]]"
private: true
---
## Week Summary
High-level themes and patterns from the week.
## Key Events
- Monday: ...
- Tuesday: ...
- Notable accomplishment
## Learnings
- Insight 1 from [[2024-01-08]]
- Insight 2 from [[2024-01-10]]
## Public Notes Created
- [[book-title]] - Finished reading and captured notes
- [[podcast-episode]] - Great episode on X topic
Before saving:
YYYY-Www.md format (w lowercase)type: weekly and private: truedailies array lists all daily notes included[[slug]] format| Situation | Handling |
|---|---|
| No daily notes found | Warn user, offer to create anyway |
| Partial week (< 7 days) | Proceed with available entries |
| Weekly review already exists | Offer to update or skip |
| User wants different week | Allow specifying week number |
Ingest a new source into the LLM Wiki. Save the full captured resource under src/content/notes/sources/ first, then create or update the maintained wiki summary/synthesis entry, index, and log. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Query the maintained wiki layer first, then fall back to sources when needed. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that the wiki might answer.
Curate wiki maps and clustering pages for the LLM Wiki. Use when asked to "curate MOCs", "update maps", "find clusters", "what MOCs need updating", or "organize my notes".
Audit the maintained wiki for quality and maintenance issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links".
Generate a weekly newsletter summarizing resources added last week. Use when asked to "weekly newsletter", "newsletter", "what did I add this week", "generate newsletter", or "Monday newsletter".
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".