Menu
Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| 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, Glob, Grep, AskUserQuestion |
Summarize the past week's daily entries into a weekly review note.
All private notes live in content/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: content/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}
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 content/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 |
Must read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
Generate interactive HTML walkthroughs with clickable Mermaid diagrams (flowcharts and ER diagrams) that explain codebase features, flows, architecture, and database schemas. Use when asked to "walkthrough", "explain this flow", "how does X work", "trace the code path", "annotated diagram", "code walkthrough", "explain the architecture of", "walk me through", "database schema", "explain the tables", "data model".
Create a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
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".
Query your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
Create Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".