What is weekly-review?

A recurring review of projects, personal responsibilities, recent sessions, and items waiting for attention.

It helps review the past week, inspect recent session notes, check the inbox, and look for open work across different areas of life and projects.

It helps reveal unfinished work, neglected areas, stale inbox items, and priorities after a busy week or break.

How teejayen/arc configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to teejayen/arc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/teejayen/arc/main/.claude/skills/weekly-review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/teejayen/arc

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/teejayen/arc/weekly-review/github.svg)](https://agentmods.dev/skills/teejayen/arc/weekly-review)

Your own site

<a href="https://agentmods.dev/skills/teejayen/arc/weekly-review"><img src="https://agentmods.dev/badge/skills/teejayen/arc/weekly-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/teejayen/arc/weekly-review"><img src="https://agentmods.dev/badge/skills/teejayen/arc/weekly-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 766 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00766
Opus 5.5	$0.00015	$0.00306
Sonnet 5.5	$0.00007	$0.00153
Haiku 4.5	$0.00004	$0.00077

Measured 2mo ago against content hash a0da5736542c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

weekly-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/weekly-review/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Weekly Review

Comprehensive review across all life areas and projects.

When to Use

Weekly (suggest: Sunday evening or Monday morning)
When feeling scattered or overwhelmed
After returning from break/holiday
User runs /review

Execution Steps

Step 1: Get context

date "+%Y-%m-%d %H:%M"

Read current state:

state/focus.md
state/projects.json
state/journal.jsonl (last 7 entries)
state/session-context.json

Step 2: Review sessions

List recent sessions (files are named YYYY-MM-DD-HHMM-topic.md):

ls -1 sessions/ | tail -10

Read the recent session files to understand what was explored last week.

Step 3: Check inbox

ls -la inbox/

Flag:

Item count
Anything older than 7 days (stale)
Patterns in what's accumulating

Step 4: Review each area

For each area in areas/:

What happened this week?
Any open loops?
Anything neglected?

Review the life areas defined in user-context.md. Common areas:

Career - Work status, professional development
Family - Upcoming commitments, quality time
Health - Exercise, fitness consistency
Finance - Any actions needed
Projects - Side project progress

Step 5: Review projects specifically

Read state/projects.json and for each project:

What moved forward?
What's blocked?
What's the next milestone?

Update state/projects.json with current status.

Step 6: Pattern detection

Query state/journal.jsonl for patterns:

Which topics keep recurring?
Energy levels over the week
Any areas consistently absent?

Step 7: Update focus.md

Rewrite state/focus.md with:

This week's priorities
What's on the mind
Any shifts in focus

Step 8: Generate review document

Create sessions/YYYY-MM-DD-weekly-review.md:

---
title: "Weekly Review: [date range]"
created: YYYY-MM-DD
tags: [review, weekly]
---

# Weekly Review: [start] to [end]

## Summary
[Overall sense of the week]

## By Area

### Career
- [Status/progress/notes]

### Family
- [Status/notes]

### Health
- [Status/notes]

### Projects
[For each project in projects.json:]

#### [Project Name]
- Status: [from projects.json]
- Progress: [what moved]
- Next: [upcoming milestone]

### Other Areas
- [Any notable updates]

## Patterns Noticed
- [Recurring themes from journal]
- [Energy patterns]
- [Neglected areas]

## Wins
- [What went well]

## Open Loops
- [Unresolved items needing attention]

## Next Week Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

## Inbox Status
- Items: [count]
- Stale: [count]
- Action: [process now / schedule time]

Read the full file on GitHub · 153 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 153 lines · 37 tokens per session scan A a0da5736542c

Subscribe to this mod's changes

weekly-review is a skill published in the GitHub repository teejayen/arc (5 stars, last pushed 9mo ago), licensed MIT. It adds 37 tokens to every session and 766 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Productivity

weekly-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
weekly-reviewteejayen/arc	Skill	5	9mo ago	MIT	A	37	Claude Code
orbit-notionnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	117	Claude Code, Codex
agentmailpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	30	Claude Code, Codex
Cortexdanielmiessler/LifeOS	Skill	20k	yesterday	MIT	A	184	Claude Code
rowboat-spacesrowboatlabs/rowboat	Skill	18k	yesterday	Apache-2.0	A	60	Claude Code, Codex
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex
pinchtab-mcppinchtab/pinchtab	Skill	11k	10d ago	MIT	A	52	Claude Code, Codex

arc: Skill for Claude Code