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…
Run a structured weekly review covering projects, habits, goals, and planning.
Install Weekly Review
$ npx skills add espennilsen/pi --skill weekly-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install espennilsen/pi 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/espennilsen/pi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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/espennilsen/pi/tree/main/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 espennilsen/pi --skill weekly-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install espennilsen/pi weekly-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/espennilsen/pi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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 espennilsen/pi --skill weekly-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install espennilsen/pi weekly-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/espennilsen/pi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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/espennilsen/pi.git --path 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 espennilsen/pi --skill weekly-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install espennilsen/pi weekly-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/espennilsen/pi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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 espennilsen/pi 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 espennilsen/pi --skill weekly-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/espennilsen/pi.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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 espennilsen/pi --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 espennilsen/pi weekly-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/espennilsen/pi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/espennilsen/pi/tree/main/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
- 122
- Token cost
- ~527 tokens
- SKILL.md length
- 166 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run a structured weekly review covering projects, habits, goals, and planning.
- Works in 4 steps: Gather Context → Review Structure → Ask Espen → …
- Asked for a weekly review
- SKILL.md covers Purpose, Process and Tone
- Calls git and sqlite3
What it does
Weekly Review is an agent skill from espennilsen/pi. Run a structured weekly review covering projects, habits, goals, and planning. Use when asked for a weekly review, week summary, or weekly planning session.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Journaling and reflection. The licence is MIT.
When your agent uses it
- Asked for a weekly review
- Weekly planning session
Example prompts
- “/weekly-review”
Workflow steps
4 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 79d019b. 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
Shell commands in SKILL.md call:
gitsqlite3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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 527 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 166 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from espennilsen/pi at commit 79d019b, republished under its MIT licence (© espennilsen). 166 words, ~527 tokens.
Download SKILL.mdSave it as
.claude/skills/weekly-review/SKILL.md (or your agent's skills folder).- name
- weekly-review
- description
- Run a structured weekly review covering projects, habits, goals, and planning. Use when asked for a weekly review, week summary, or weekly planning session.
Weekly Review
Purpose
Help Espen reflect on the past week and plan the next one. Covers professional projects, personal development, health, and learning goals.
Process
1. Gather Context
Read recent activity to build a picture of the week:
# Recent daily notes (last 7)
VAULT="/Users/espen/Library/CloudStorage/OneDrive-Espennilsen.net/2-Areas/Digital_Life/Obsidian/e9n"
ls -t "$VAULT/Notes/Daily/" | head -7# Recent git activity across projects
for d in /Users/espen/Dev/e9n.dev /Users/espen/Dev/pi /Users/espen/Dev/Starheim /Users/espen/Dev/x10s-pi; do
echo "=== $(basename $d) ==="
git -C "$d" log --oneline --since="7 days ago" --no-merges 2>/dev/null | head -5
done# Hannah job stats for the week
sqlite3 /Users/espen/Dev/pi/hannah.db "
SELECT COUNT(*) as jobs, printf('\$%.4f', SUM(cost_total)) as cost, SUM(total_tokens) as tokens
FROM jobs WHERE created_at >= datetime('now', '-7 days');
"2. Review Structure
Present findings organized as:
🏆 Wins — What went well, what was accomplished 📋 Active Projects — Status of each active project, progress this week 🎯 Goals Check-in — Health, learning, personal development progress ⚡ Blockers — What's stuck and why 📅 Next Week — Top 3 priorities, scheduled commitments, experiments to try
3. Ask Espen
After presenting the review, ask:
- "Anything I missed or got wrong?"
- "What should be the #1 priority next week?"
- "Any new projects or ideas to capture?"
4. Capture (with permission)
If Espen wants, create a weekly review note in the vault:
Weekly Reviews/YYYY-WNN Review.mdAlways confirm before writing to the vault.
Tone
Supportive but honest. Celebrate wins. Don't sugarcoat missed goals — frame them as data for adjustment, not failure. Channel stoic philosophy: focus on what's within control, let go of what isn't.
© espennilsen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/weekly-review of espennilsen/pi.
Open the folder on GitHubat commit 79d019b
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 skillespennilsen/pi | 122 | — | ~527 | 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 espennilsen/pi
All 36 skills in this repoGitHub
espennilsen/pi
Interact with GitHub repos, PRs, issues, CI, and notifications via the pi-github extension commands and gh CLI.
Skill Creator
espennilsen/pi
Create, review, and improve skills for Pi agents. An agent skill from espennilsen/pi.
Dry Code Review
espennilsen/pi
Perform a comprehensive DRY (Don't Repeat Yourself) code review on a codebase.
Extract Design System
espennilsen/pi
Reverse-engineer a design system from a live website (public URL or localhost).
PDF Reader
espennilsen/pi
Read and extract content from PDF files — text, tables, metadata, and images.
Google Workspace
espennilsen/pi
Manage Google Workspace via the gws CLI — Drive, Gmail, Sheets, Docs, Slides, People, Chat, Meet, Forms, and cross-service workflows.
Related
Categories
Questions about Weekly Review
What does Weekly Review do?
Run a structured weekly review covering projects, habits, goals, and planning. Weekly Review is an agent skill from espennilsen/pi. Run a structured weekly review covering projects, habits, goals, and planning.
When should I use Weekly Review?
Weekly Review fits situations like: asked for a weekly review; weekly planning session.
How do I install Weekly Review in Claude Code?
Run `npx skills add espennilsen/pi --skill weekly-review -a claude-code`. Or copy the skill folder (skills/weekly-review in espennilsen/pi) 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 espennilsen/pi --skill weekly-review -a codex`. Or copy the skill folder (skills/weekly-review in espennilsen/pi) 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 espennilsen/pi --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 the command-line tools its instructions call (git and sqlite3).
Does Weekly Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. 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. Review the folder before installing.
What licence does Weekly Review use?
Weekly Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Weekly Review use?
About 527 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
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?
espennilsen (a GitHub user) maintains it in espennilsen/pi, which has 122 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on September 21, 2026.
Source: espennilsen/pi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.