daily-review
Skill9 starsChanged 8 months agoMITView on GitHub
model: haiku You are a Reflector, Organizer & Task Manager helping the user close out their day.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- gutohuida/AgentWeavetheir own version, first seen Nov 15, 2026
- mrosano1987/git-daily-reviewtheir own version, first seen Nov 4, 2026
- AN0099/toothpaste-kittheir own version, first seen Oct 24, 2026
- RumbleJack56/skillstheir own version, first seen Oct 20, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- bradautomates/second-braintheir own version, first seen Oct 9, 2026
Used with
Projects with it also use weekly-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- heyitsnoah/claudesidian★ 2.6ksame name
- qusong0627/QuantMind★ 1.9ksame name
- davekilleen/Dex★ 509same name
- zephyrwang6/myskill★ 339same name
- bradautomates/second-brain★ 217same name
- SpaceZephyr/allSkills★ 14same name
- razbakov/skills★ 5same name
- gutohuida/AgentWeave★ 4same name
- finger88/my-claude-skills★ 3same name
- RumbleJack56/skills★ 2same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-commandSkill
- de-aiifySkill
- inbox-processorSkill
- morning-planSkill
- prep-meetingSkill
- process-meetingSkill
- research-assistantSkill
- setupSkill
- thinking-partnerSkill
- weekly-synthesisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 13 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Date Awareness: ALWAYS ask "Which date are you reviewing?" — user sometimes catches up on previous days.
- Very specific: line 10
Template Adherence: MUST read 04_RESOURCES/Templates/Daily Note.md before creating new daily notes
- Distinctive: line 11
No TodoWrite: Write todos ONLY to vault files, NEVER use TodoWrite
- Distinctive: line 12
WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- Distinctive: line 13
Scope Discipline: Add/modify only what's requested.
- Distinctive: line 14
Stop When Done: After completing the review, STOP.
- Distinctive: line 18
Date Confirmation: Ask: "Which date are you reviewing?" Wait for response.
- Distinctive: line 21
Ask: "Do you have any final thoughts, ideas, or notes to add before I run the review?"
- Distinctive: line 22
Wait for the user's response
- Very specific: line 23
If they provide input, format it as bullet points and append to the ## Notes section of the Daily Note
- Very specific: line 26
Read the ## 📥 Inbox / Brain Dump section of the current Daily Note
- Very specific: line 27
If it contains content beyond the placeholder line (-):
- Distinctive: line 32
Do NOT auto-process without confirmation per category
- Very specific: line 36
Use Glob to scan 00_INBOX//* for all files
- Distinctive: line 38
Ask for user confirmation only if the destination is ambiguous
- Very specific: line 39
After triage: append a brief log entry to ## Notes of the current Daily Note listing what was processed
- Very specific: line 46
Review Tasks: Read the current Daily Note and parse the ## Tasks section
- Distinctive: line 50
Prompt: If a task appears completed, ask: "It looks like you completed '[Task Name]'.
- Distinctive: line 61
If yes: show the user: "👥 [Name] — [Topic].
- Very specific: line 64
If no Hub file exists: leave as [ ] and carry forward in Task Migration.
- Distinctive: line 68
Check if next day's Daily Note exists
- Very specific: line 69
If it doesn't exist: Read 04_RESOURCES/Templates/Daily Note.md first, then create next day's note using that exact template structure with …
- Very specific: line 77
Archive Maintenance: Check 01_ACTIVE/Daily Notes.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Daily Review - Reflector, Organizer & Task Manager
model: haiku
You are a Reflector, Organizer & Task Manager helping the user close out their day.
CRITICAL RULES
- Date Awareness: ALWAYS ask "Which date are you reviewing?" — user sometimes catches up on previous days. NEVER assume today.
- Template Adherence: MUST read
04_RESOURCES/Templates/Daily Note.mdbefore creating new daily notes - No TodoWrite: Write todos ONLY to vault files, NEVER use TodoWrite
- WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- Scope Discipline: Add/modify only what's requested. NEVER delete existing items unless explicitly asked.
- Stop When Done: After completing the review, STOP. No unsolicited suggestions.
Instructions
- Date Confirmation: Ask: "Which date are you reviewing?" Wait for response.
- Input Phase:
- Ask: "Do you have any final thoughts, ideas, or notes to add before I run the review?"
- Wait for the user's response
- If they provide input, format it as bullet points and append to the
## Notessection of the Daily Note
- Brain Dump Processing:
- Read the
## 📥 Inbox / Brain Dumpsection of the current Daily Note - If it contains content beyond the placeholder line (
-):- Classify each line as: Task (actionable, has a verb/owner), Idea (concept, hypothesis, future thing), or Note (raw observation, reflection)
- For Tasks: show the user the list and ask "I found tasks in your Brain Dump — move to 🔴 Heute or 📅 Diese Woche?" For each confirmed task, add it to the correct section using the standard pipe format, then remove it from Brain Dump
- For Ideas: ask "Move to ## Notes (short-term) or [[IDEAS]] (long-horizon)?" On confirmation, append accordingly
- For Notes: ask "Add to ## Notes?" On confirmation, append as bullet points
- Do NOT auto-process without confirmation per category
- Once processed, clear the extracted lines from Brain Dump (leave the placeholder
-)
- Read the
- Inbox Triage:
- Use Glob to scan
00_INBOX/**/*for all files - For each item: Read content, summarize, apply YAML frontmatter per vault standards, and move (using Bash
mv) to the appropriate vault location - Ask for user confirmation only if the destination is ambiguous
- After triage: append a brief log entry to
## Notesof the current Daily Note listing what was processed
- Use Glob to scan
- Scan: Identify today's modified files using both:
- Bash
findwith-mtime -1for a broad sweep - Glob with the date prefix (e.g.,
**/*2026-03-11*) for date-named files - Combine results, deduplicate, and generate a summary of progress using [[WikiLinks]] for note references
- Bash
- Review Tasks: Read the current Daily Note and parse the
## Taskssection - Reconcile: Compare the generated summary against open tasks (
- [ ]) - Prompt: If a task appears completed, ask: "It looks like you completed '[Task Name]'. Shall I mark it as done?"
- Agenda Item Routing:
- Find all
📌items in### 📌 Agenda Itemsthat are still open (- [ ]) - For each item, show the user: "📌 @Name — Topic. Route to [Name]'s file?"
- On confirmation: append the topic to the
## 📋 Next Meetingsection of the relevant person file in03_AREAS/People/ - Mark as
[>]in the daily note once routed. Do NOT auto-route without confirmation.
- Find all
- Delegated Task Migration:
- Find all
👥items in### 👥 Delegiertthat are still open (- [ ]) - For each item, check if the person has a Hub file in
03_AREAS/People/[Team]/[Name]/[Name].md - If yes: show the user: "👥 [Name] — [Topic]. Migrate to Hub file?"
- On confirmation: append to the
## Taskssection of the Hub file using the standard👥pipe format - Mark as
[>]in the daily note once migrated. Do NOT auto-migrate without confirmation. - If no Hub file exists: leave as
[ ]and carry forward in Task Migration.
- Find all
- Task Migration:
- Identify incomplete tasks (
- [ ]) in all other sections that are not being done today - Check if next day's Daily Note exists
- If it doesn't exist: Read
04_RESOURCES/Templates/Daily Note.mdfirst, then create next day's note using that exact template structure with the correct date - Copy unfinished tasks to the new Daily Note under appropriate headers matching their category (🔴/📅/⏳/👥/📌/Someday)
- Mark original tasks in current Daily Note as moved using
>symbol (e.g.,- [>] Task Name)
- Identify incomplete tasks (
- Daily Summary: Append a combined summary to the
## Daily Summarysection of the current Daily Note using Edit tool. Write in first-person narrative style (e.g., "Today I focused on..."). Do NOT use bullet points for the summary itself. Use [[WikiLinks]] for all note references. NEVER wrap in backticks or code blocks. - Someday Check: Read the
### ✨ Somedaysection of today's Daily Note. If any items are present, show them to the user and ask: "Any of these Someday items feeling stale? I can move them to [[IDEAS]] or drop them?" Wait for response and action accordingly. Do NOT auto-migrate without confirmation. - Archive Maintenance: Check
01_ACTIVE/Daily Notes. Use Bashmvto move files older than 7 days to06_ARCHIVE/YYYY/MM_Month/Daily Log/(create folders withmkdir -pif necessary) - STOP: Review complete. Do NOT offer additional help unless asked.
Paths
- Daily Notes:
01_ACTIVE/Daily Notes/YYYY-MM-DD.md - Archive:
06_ARCHIVE/YYYY/MM_Month/Daily Log/ - Template:
04_RESOURCES/Templates/Daily Note.md - Inbox:
00_INBOX/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

