/weekly-review
Guided weekly reflection across all relationships, commitments, and projects with pattern analysis. Use at end of week, or when user says "weekly review", "end of week", "reflect on this week", "weekly check-in", or "how did my week go". See also: `morning-brief` (daily),
$ npx -y skills add kbanc85/claudia --skill weekly-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition โ
- You can call itInvoke it directly when you want it.
- Slash command
/weekly-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
Guided weekly reflection across all relationships, commitments, and projects with pattern analysis. Use at end of week, or when user says "weekly review", "end of week", "reflect on this week", "weekly check-in", or "how did my week go". See also: `morning-brief` (daily),
SKILL.md
weekly-review.SKILL.mdname: weekly-review
description: Guided weekly reflection across all relationships, commitments, and projects with pattern analysis. Use at end of week, or when user says "weekly review", "end of week", "reflect on this week", "weekly check-in", or "how did my week go". See also: `morning-brief` (daily), `growth-check` (zoom out), `meditate` (session reflection).
effort-level: high
Weekly Review
Guided weekly reflection across all relationships, commitments, and projects.
The Flow
1. Opening Check-In
Start with energy and reflection:
- "How are you feeling about this week?"
- "What's on your mind going into this review?"
2. Wins Capture
Surface and celebrate:
- "What went well this week?"
- Check for completed commitments
- Note any positive signals from relationships
- Acknowledge progress
3. Commitment Audit
Review all commitments:
**Overdue:**
- What slipped and why?
- Recovery plan or decision to drop?
**Completed:**
- Mark as done
- Any follow-up needed?
**Coming Up:**
- Next week's deadlines
- Anything to start now?
4. Waiting Items Review
Check `context/waiting.md`:
- What arrived?
- What's overdue?
- Follow-ups needed?
5. Relationship Health
Scan all people files:
- Who needs attention?
- Any cooling relationships?
- Positive momentum to maintain?
6. Pattern Reflection
Surface observations from `context/patterns.md`:
- What's working?
- What keeps recurring that shouldn't?
- Any insights for next week?
7. Development Check
Reflect on growth (reference `context/me.md` if future direction exists):
- "What worked particularly well this week? Worth remembering or sharing?"
- "Any insights that could become content or methodology improvements?"
- "Progress toward your bigger goals?"
If they shared a future direction during onboarding, connect this week's work to that trajectory. Not every week needs to be about big goals, but it's worth asking.
8. Next Week Setup
Look ahead:
- Key priorities
- Important meetings
- Things to start
9. Learnings Capture
Before closing:
- Anything to remember for next time?
- Updates to context files?
- Insights worth capturing in `context/me.md`?
Output Format
**๐ Weekly Review โ [Week of Date]**
### ๐ Wins
- [Win 1]
- [Win 2]
- [Win 3]
### ๐ Commitments
**โ
Completed:**
- [Item] โ
**โ ๏ธ Overdue:**
- [Item] โ [decision: reschedule/drop/do now]
**๐
Next Week:**
- [Item] โ due [day]
### โณ Waiting On
**Received:**
- [Item] from [Person] โ
**Still Waiting:**
- [Item] from [Person] โ follow up [when]
### ๐ฅ Relationships
**Need Attention:**
- [Person] โ [why]
**Going Well:**
- [Person] โ [positive note]
### ๐ Patterns Noticed
- [Pattern or observation]
### ๐ฑ Development
**What worked well:**
- [Insight worth remembering or sharing]
**Progress toward goals:**
- [Connection to bigger picture, if applicable]
**Ideas captured:**
- [Content ideas, methodology improvements, lessons learned]
### ๐ฏ Next Week's Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
### ๐ Notes
- [Anything to remember]
---
Tone
- Reflective, not judgmental
- Celebrate wins genuinely
- Be honest about what slipped without making it feel like failure
- Forward-looking and energizing
- Suggest, don't prescribe
Timing
Ideal for Friday afternoon or Sunday evening. Adapt based on user preference.
Depth
The review can be quick (15 min) or thorough (45 min) depending on the week and user's energy. Ask: "Full review or quick check-in today?"
Read more
name: weekly-review description: Guided weekly reflection across all relationships, commitments, and projects with pattern analysis. Use at end of week, or when user says "weekly review", "end of week", "reflect on this week", "weekly check-in", or "how did my week go". See also: `morning-brief` (daily), `growth-check` (zoom out), `meditate` (session reflection). effort-level: high
Weekly Review
Guided weekly reflection across all relationships, commitments, and projects.
The Flow
1. Opening Check-In
Start with energy and reflection:
- "How are you feeling about this week?"
- "What's on your mind going into this review?"
2. Wins Capture
Surface and celebrate:
- "What went well this week?"
- Check for completed commitments
- Note any positive signals from relationships
- Acknowledge progress
3. Commitment Audit
Review all commitments:
**Overdue:**
- What slipped and why?
- Recovery plan or decision to drop?
**Completed:**
- Mark as done
- Any follow-up needed?
**Coming Up:**
- Next week's deadlines
- Anything to start now?
4. Waiting Items Review
Check `context/waiting.md`:
- What arrived?
- What's overdue?
- Follow-ups needed?
5. Relationship Health
Scan all people files:
- Who needs attention?
- Any cooling relationships?
- Positive momentum to maintain?
6. Pattern Reflection
Surface observations from `context/patterns.md`:
- What's working?
- What keeps recurring that shouldn't?
- Any insights for next week?
7. Development Check
Reflect on growth (reference `context/me.md` if future direction exists):
- "What worked particularly well this week? Worth remembering or sharing?"
- "Any insights that could become content or methodology improvements?"
- "Progress toward your bigger goals?"
If they shared a future direction during onboarding, connect this week's work to that trajectory. Not every week needs to be about big goals, but it's worth asking.
8. Next Week Setup
Look ahead:
- Key priorities
- Important meetings
- Things to start
9. Learnings Capture
Before closing:
- Anything to remember for next time?
- Updates to context files?
- Insights worth capturing in `context/me.md`?
Output Format
**๐ Weekly Review โ [Week of Date]** ### ๐ Wins - [Win 1] - [Win 2] - [Win 3] ### ๐ Commitments **โ Completed:** - [Item] โ **โ ๏ธ Overdue:** - [Item] โ [decision: reschedule/drop/do now] **๐ Next Week:** - [Item] โ due [day] ### โณ Waiting On **Received:** - [Item] from [Person] โ **Still Waiting:** - [Item] from [Person] โ follow up [when] ### ๐ฅ Relationships **Need Attention:** - [Person] โ [why] **Going Well:** - [Person] โ [positive note] ### ๐ Patterns Noticed - [Pattern or observation] ### ๐ฑ Development **What worked well:** - [Insight worth remembering or sharing] **Progress toward goals:** - [Connection to bigger picture, if applicable] **Ideas captured:** - [Content ideas, methodology improvements, lessons learned] ### ๐ฏ Next Week's Focus 1. [Priority 1] 2. [Priority 2] 3. [Priority 3] ### ๐ Notes - [Anything to remember] ---
Tone
- Reflective, not judgmental
- Celebrate wins genuinely
- Be honest about what slipped without making it feel like failure
- Forward-looking and energizing
- Suggest, don't prescribe
Timing
Ideal for Friday afternoon or Sunday evening. Adapt based on user preference.
Depth
The review can be quick (15 min) or thorough (45 min) depending on the week and user's energy. Ask: "Full review or quick check-in today?"
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Repo: kbanc85/claudia
Other skills on claudia.
- /auto-research
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this",
Open skill - /brain-monitor
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Open skill - /brain
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Open skill - /build-team
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my
Open skill - /capture-meeting
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Open skill - /client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
Open skill

