LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
A skill your agent uses when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says…
Install Weekly Review
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills weekly-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .claude/skills/weekly-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .claude/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills weekly-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .agents/skills/weekly-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .agents/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills weekly-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .cursor/skills/weekly-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .cursor/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path productivity/weekly-review/skills/weekly-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills weekly-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .gemini/skills/weekly-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .gemini/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills weekly-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .github/skills/weekly-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .github/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill weekly-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills weekly-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/productivity/weekly-review/skills/weekly-review .opencode/skills/weekly-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/productivity/weekly-review/skills/weekly-review into .opencode/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
weekly-review- GitHub stars
- 28k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 566 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says…
- Works in 3 steps: GET CLEAR (steps 1-3) → GET CURRENT (steps 4-8, all mandatory) → GET CREATIVE (steps 9-10)
- Someone wants to run a weekly review
- SKILL.md covers What this does, Phase 1 — GET CLEAR (steps 1-3), Phase 2 — GET CURRENT (steps… and Phase 3 — GET CREATIVE (steps…, plus 5 more sections
- Runs Python scripts from its folder; calls python
What it does
Weekly Review is an agent skill from alirezarezvani/claude-skills. Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `assets/example_weekly_review.md`, `assets/weekly_review_checklist.md` and `references/gtd_weekly_review_canon.md`).
It sits in Knowledge Management, covering Journaling and reflection. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Someone wants to run a weekly review
- Close open loops
- Audit stalled projects and commitments
- Get their system back to trusted
Example prompts
- “/cs:weekly-review”
- “/weekly-review”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Weekly Review loads about 1.4k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 566 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 566 words, ~1,439 tokens.
Download SKILL.mdSave it as
.claude/skills/weekly-review/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- weekly-review
- description
- Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
- argument-hint
- [optional: directory or notes to review]
- license
- MIT
- metadata.version
- 1.0.0
- metadata.build_pattern
- Path-B ritual skill — GTD weekly-review loop preserved + deterministic scanner/gate/auditor scripts added
- metadata.distinct_from
- reflect (per-conversation reflection, not a recurring cadence); capture (intake that feeds the system, not the review that maintains it); project-management…
Weekly Review — GTD Loop → Trusted System
Portability: Reasoning-led skill with 3 stdlib Python scripts. No external APIs, no LLM calls in scripts. Works in Claude Code CLI and Claude.ai web. The scripts do the inventory and the gating; Claude and the user do the thinking.
What this does
A personal system is only trustworthy if it gets reviewed — David Allen calls the weekly review the critical success factor of the whole method. This skill walks the three phases in order and refuses to call the review COMPLETE while any of the five mandatory GET CURRENT steps is unaccounted for. Evidence first: scan the workspace for open loops before asking the user to recall anything, because their memory is exactly what the method says not to trust.
Phase 1 — GET CLEAR (steps 1-3)
Collect loose inputs, process every inbox to zero (clarify, don't do — anything over two minutes becomes a next action), then a mind sweep to empty the head. Start with evidence:
# Inventory open loops: unchecked checkboxes, TODO/FIXME markers, stale files
python scripts/open_loop_scanner.py --dir ~/notes --stale-days 14Route every loop found to a list — next action, waiting-for, someday/maybe, or trash.
Phase 2 — GET CURRENT (steps 4-8, all mandatory)
Review the next-action lists (mark done, prune dead), the previous calendar (missed commitments become actions), the upcoming calendar (prepare, don't react), the waiting-for list (chase or drop), and every project for exactly one next action. Then gate honestly:
python scripts/weekly_review_gate.py --list # show the numbered ten-step checklist
python scripts/weekly_review_gate.py --done "1,2,3,4,5,6,7,8" --skip "9:no someday list yet"The gate computes completion %, names every missing step, and exits 0 (COMPLETE) or 2 (INCOMPLETE). An unskipped missing GET CURRENT step always forces INCOMPLETE.
Phase 3 — GET CREATIVE (steps 9-10)
Review someday/maybe (activate, keep, or kill), capture new ideas while the head is clear, then audit the whole commitment portfolio:
python scripts/commitment_auditor.py --input commitments.jsonFlags STALLED / NO-NEXT-ACTION / SOMEDAY-CANDIDATE, prints the health formula with the score, and issues HEALTHY / DRIFTING / OVERCOMMITTED. End the review with one named next action.
Scripts
| Script | Role |
|---|---|
scripts/open_loop_scanner.py | Inventories unchecked checkboxes, TODO/FIXME markers, and stale files across a directory; grouped counts + per-file locations; --json. |
scripts/weekly_review_gate.py | The ten-step three-phase checklist; --done/--skip/--list; completion % + named gaps → COMPLETE (exit 0) / INCOMPLETE (exit 2). |
scripts/commitment_auditor.py | Flags stalled and actionless commitments, computes the 0-100 health score with the formula shown → HEALTHY / DRIFTING / OVERCOMMITTED. |
Show full SKILL.md (218 more words)Show less
References
references/gtd_weekly_review_canon.md— why the weekly review is the critical success factor; the three-phase structure; cadence discipline (7 sources)references/open_loop_psychology.md— Zeigarnik effect, plan-making research, attention residue: why open loops tax attention (6 sources)references/review_cadence_design.md— horizons of focus, habit anchoring, timeboxing, failure modes, restart-after-lapse (7 sources)
Assets
assets/weekly_review_checklist.md— fillable three-phase checklistassets/example_weekly_review.md— a full worked review (scan → checklist → gate → audit → next action)
Rules
- All five GET CURRENT steps are mandatory; skip only with a stated reason, and the gate still names it.
- Never self-certify — the gate issues the verdict; relay its exit code, don't soften it.
- Process, don't do: during the review, anything over two minutes becomes a next action, not a detour.
- Timebox 60-90 minutes; past two hours, gate what's done honestly and schedule the remainder.
- A lapsed habit restarts with a shorter pass and zero guilt — a review is maintenance, not judgment.
Distinct From (don't reach for the wrong sibling)
productivity/reflect— reflects on one conversation or piece of work, once. The weekly review is a recurring cadence over the whole system.productivity/capture— the intake funnel (brain dump → actions). Capture feeds the system; this review keeps it trusted.project-managementsprint retros — a team ceremony about a shared iteration. This is a personal trusted-system audit.
Version: 1.0.0 · Build pattern: Path-B ritual skill — GTD weekly-review loop preserved + deterministic gate/scanner/auditor scripts added.
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references, assets) in productivity/weekly-review/skills/weekly-review of alirezarezvani/claude-skills.
- SKILL.md
- assets/example_weekly_review.md
- assets/weekly_review_checklist.md
- references/gtd_weekly_review_canon.md
- references/open_loop_psychology.md
- references/review_cadence_design.md
- scripts/commitment_auditor.py
- scripts/open_loop_scanner.py
- scripts/weekly_review_gate.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Weekly Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Weekly Review this skillalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| Munger Perspectivealchaincyf/munger-skill | 379 | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Daily Journalhuytieu/COG-second-brain | 1.3k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Letterboxd Diaryjoe-bell/skills | 211 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Em Grid Scorermanager-dot-dev/manager-skills | 114 | — | ~5.8k | Automated safety check: Pass | MIT |
Similar skills
Munger Perspective
alchaincyf/munger-skill
查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研， 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。
Daily Journal
huytieu/COG-second-brain
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.
Letterboxd Diary
joe-bell/skills
Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.
Em Grid Scorer
manager-dot-dev/manager-skills
Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.
Digital Brain
foryourhealth111-pixel/Vibe-Skills
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Weekly Review
What does Weekly Review do?
A skill your agent uses when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says…. Weekly Review is an agent skill from alirezarezvani/claude-skills. Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review".
When should I use Weekly Review?
Weekly Review fits situations like: someone wants to run a weekly review; close open loops; audit stalled projects and commitments; get their system back to trusted.
How do I install Weekly Review in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill weekly-review -a claude-code`. Or copy the skill folder (productivity/weekly-review/skills/weekly-review in alirezarezvani/claude-skills) into .claude/skills/weekly-review in your project. Claude Code loads it when a task matches its description.
How do I install Weekly Review in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill weekly-review -a codex`. Or copy the skill folder (productivity/weekly-review/skills/weekly-review in alirezarezvani/claude-skills) into .agents/skills/weekly-review in your project. Codex loads it when a task matches its description.
Can I use Weekly Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill weekly-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-review, .gemini/skills/weekly-review, .github/skills/weekly-review and .opencode/skills/weekly-review in your project.
What does Weekly Review need to run?
Going by SKILL.md and its folder, Weekly Review needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Weekly Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Weekly Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Weekly Review use?
Weekly Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Weekly Review use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.7k tokens, read only when the agent opens those files.
What are the alternatives to Weekly Review?
Skills that share tags, products or a category with Weekly Review: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 379 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Weekly Review?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.