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…
Facilitate weekly review process with reflection, goal alignment, and planning.
Install Weekly
$ npx skills add ballred/obsidian-claude-pkm --skill weekly -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ballred/obsidian-claude-pkm weekly --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/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vault-template/.claude/skills/weekly .claude/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .claude/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weeklyType 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 ballred/obsidian-claude-pkm --skill weekly -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ballred/obsidian-claude-pkm weekly --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/vault-template/.claude/skills/weekly .agents/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .agents/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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 ballred/obsidian-claude-pkm --skill weekly -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ballred/obsidian-claude-pkm weekly --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/vault-template/.claude/skills/weekly .cursor/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .cursor/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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/ballred/obsidian-claude-pkm.git --path vault-template/.claude/skills/weekly--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 ballred/obsidian-claude-pkm --skill weekly -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ballred/obsidian-claude-pkm weekly --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/vault-template/.claude/skills/weekly .gemini/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .gemini/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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 ballred/obsidian-claude-pkm weeklyInstalls 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 ballred/obsidian-claude-pkm --skill weekly -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .github/skills && cp -r skills-src/vault-template/.claude/skills/weekly .github/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .github/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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 ballred/obsidian-claude-pkm --skill weekly -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ballred/obsidian-claude-pkm weekly --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ballred/obsidian-claude-pkm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/vault-template/.claude/skills/weekly .opencode/skills/weekly && 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" agent skill from https://github.com/ballred/obsidian-claude-pkm/tree/main/vault-template/.claude/skills/weekly into .opencode/skills/weekly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly", 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- GitHub stars
- 1.9k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 608 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Facilitate weekly review process with reflection, goal alignment, and planning.
- Works in 3 steps: Reflection (10 minutes) → Goal Alignment + Project Rollup (10… → Planning (10 minutes)
- Tasks that involve Journaling and reflection
- SKILL.md covers Usage, What This Skill Does, Review Process Steps and Interactive Prompts, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Weekly is an agent skill from ballred/obsidian-claude-pkm. Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
Its SKILL.md is about 1.7k 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 repository describes itself as: A complete starter kit for an Obsidian + Claude Code personal knowledge management system. The licence is MIT.
When your agent uses it
- Tasks that involve Journaling and reflection
Example prompts
- “/weekly”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet
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 ef1e4da. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrepTaskCreateTaskUpdateTaskListTaskGet
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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 loads about 1.7k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 608 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 ballred/obsidian-claude-pkm at commit ef1e4da, republished under its MIT licence (© ballred). 608 words, ~1,671 tokens.
Download SKILL.mdSave it as
.claude/skills/weekly/SKILL.md (or your agent's skills folder).- name
- weekly
- description
- Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
- allowed-tools
- Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet
- user-invocable
- true
Weekly Review Skill
Facilitates your weekly review process by creating a review note and guiding reflection on the past week while planning the next.
Usage
Invoke with /weekly or ask Claude to help with your weekly review.
/weeklyWhat This Skill Does
Creates Weekly Review Note
- Uses weekly review template
- Names it with current week's date
- Places in Goals folder
Guides Review Process
- Reviews last week's accomplishments
- Identifies incomplete tasks
- Plans upcoming week
- Aligns with monthly goals
Automates Housekeeping
- Archives old daily notes
- Updates project statuses
- Cleans up completed tasks
Review Process Steps
Step 1: Reflection (10 minutes)
- Review daily notes from past week
- Identify wins and challenges
- Capture lessons learned
Step 2: Goal Alignment + Project Rollup (10 minutes)
- Check monthly goal progress
- Adjust weekly priorities
- Ensure alignment with yearly goals
- Auto-scan
Projects/*/CLAUDE.mdfor current status - Compile project progress table for the review note
Step 3: Planning (10 minutes)
- Set ONE big thing for the week
- Include project next-actions when planning week
- Schedule important tasks
- Block time for deep work
Interactive Prompts
The skill guides you through:
"What were your top 3 wins this week?"
- Celebrates progress
- Builds momentum
- Documents achievements
"What were your main challenges?"
- Identifies obstacles
- Plans solutions
- Learns from difficulties
"What's your ONE big thing next week?"
- Forces prioritization
- Creates focus
- Drives meaningful progress
Weekly Review Checklist
- Review all daily notes
- Process inbox items
- Update project statuses
- Check upcoming calendar
- Review monthly goals
- Plan next week's priorities
- Block time for important work
- Clean digital workspace
- Archive completed items
- Commit changes to Git
Weekly Review Note Format
# Weekly Review: YYYY-MM-DD
## Last Week's Wins
1.
2.
3.
## Challenges & Lessons
- Challenge:
- Lesson:
## Goal Progress
### Monthly Goals
- [ ] Goal 1 (XX%)
- [ ] Goal 2 (XX%)
### This Week's Contribution
- [Task] -> [[Goal]]
## Project Progress
| Project | Phase | Progress | Next Action |
|---------|-------|----------|-------------|
| [[ProjectA]] | Active | 60% | [Next step] |
| [[ProjectB]] | Planning | 10% | [Next step] |
## Next Week Planning
### ONE Big Thing
>
### Key Tasks
- [ ]
- [ ]
- [ ]
### Project Next-Actions
- [ ] [ProjectA] - [specific next step]
- [ ] [ProjectB] - [specific next step]
### Time Blocks
- Monday:
- Tuesday:
- Wednesday:
- Thursday:
- Friday:
## NotesAutomation Features
Auto-Archive
Suggest moving daily notes older than 30 days to Archives.
Project Status Update
For each active project:
- Update completion percentage
- Note blockers
- Set next actions
Habit Tracking
Calculate habit success rates from daily notes:
- Count habit checkboxes
- Show completion percentage
- Identify patterns
Best Practices
Consistent Timing
- Same day each week (Sunday recommended)
- Same time if possible
- Block calendar time
- Treat as non-negotiable
Preparation
- Clean inbox before review
- Have calendar ready
- Gather project updates
- Review any feedback
Follow-through
- Share highlights with team/family
- Update external systems
- Communicate changes
- Celebrate wins
Task-Based Progress Tracking
The weekly skill uses session tasks to show progress through the 3-phase review.
Show full SKILL.md (237 more words)Show less
Phase Tasks
Create tasks at skill start:
TaskCreate:
subject: "Phase 1: Collect"
description: "Gather daily notes from past week, extract wins and challenges"
activeForm: "Collecting daily notes and extracting highlights..."
TaskCreate:
subject: "Phase 2: Reflect"
description: "Calculate goal progress, analyze alignment gaps"
activeForm: "Calculating goal progress and alignment..."
TaskCreate:
subject: "Phase 3: Plan"
description: "Identify ONE Big Thing, plan daily focus areas for next week"
activeForm: "Planning next week's focus..."Dependencies
Phases must run in order:
TaskUpdate: "Phase 2: Reflect", addBlockedBy: [phase-1-collect-id]
TaskUpdate: "Phase 3: Plan", addBlockedBy: [phase-2-reflect-id]Reflect is blocked until Collect completes. Plan is blocked until Reflect completes. This provides visibility into the 30-minute review process.
Mark each task in_progress when starting, completed when done using TaskUpdate.
Task tools are session-scoped and don't persist between Claude sessions—your actual weekly review content is saved in the review note.
Agent Team Workflow (Optional)
For a faster, more thorough weekly review, use agent teams to parallelize the collection phase:
Team Lead (coordinator)
├── collector agent — Read all daily notes, extract wins/challenges/tasks
├── goal-analyzer agent — Read goal files, calculate progress, find gaps
└── project-scanner agent — Scan Projects/*/CLAUDE.md, get status updatesHow to Use
When invoking /weekly, you can request the team-based approach:
/weekly
"Use the team approach for a thorough review"The team lead:
- Spawns three agents to work in parallel
- Collector reads daily notes and extracts highlights
- Goal-analyzer reads all goal files and calculates progress
- Project-scanner reads all project CLAUDE.md files for status
- Team lead synthesizes findings into the weekly review note
This makes the review faster (parallel collection) and more thorough (dedicated analysis per area).
Vault Health Check (Ad-hoc)
The weekly review can optionally include a vault health check using multiple agents:
- note-organizer: Scan for broken links, orphan notes
- goal-aligner: Check daily-to-goal alignment
- inbox-processor: Check for unprocessed items
Request with: "Include a vault health check in my weekly review"
Integration
Works with:
/daily- Reviews daily notes from the week/monthly- Weekly reviews feed monthly rollup/project- Project status in review/push- Commit after completing review/onboard- Load context for informed review- Goal tracking skill - Progress calculations
© ballred, 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 vault-template/.claude/skills/weekly of ballred/obsidian-claude-pkm.
Open the folder on GitHubat commit ef1e4da
Compare with similar skills
Weekly 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 this skillballred/obsidian-claude-pkm | 1.9k | — | ~1.7k | Automated safety check: Pass | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| Munger Perspectivealchaincyf/munger-skill | 377 | 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 ballred/obsidian-claude-pkm
All 13 skills in this repoDaily Notes Workflow
ballred/obsidian-claude-pkm
Creates today's daily note in an Obsidian vault and guides morning, midday and evening routines for planning, task review and reflection.
Cascading Goal Tracker
ballred/obsidian-claude-pkm
Tracks three-year, yearly, monthly, and weekly goals in linked Markdown files, calculating completion percentages and flagging stalled goals.
Obsidian Vault Operations
ballred/obsidian-claude-pkm
Reads, creates and edits notes in an Obsidian vault while preserving wiki-links, YAML frontmatter, tags and template variables.
Obsidian Project Tracker
ballred/obsidian-claude-pkm
Creates, tracks and archives projects linked to yearly goals in an Obsidian vault, with a status dashboard and a CLAUDE.md context file for each project.
Push
ballred/obsidian-claude-pkm
Commit and push vault changes to Git with smart commit messages.
Obsidian PKM Vault Upgrade
ballred/obsidian-claude-pkm
Updates an obsidian-claude-pkm vault's system files to the latest version, with a backup, per-file diff review and no changes to your own notes.
Related
Categories
Questions about Weekly
What does Weekly do?
Facilitate weekly review process with reflection, goal alignment, and planning. Weekly is an agent skill from ballred/obsidian-claude-pkm. Facilitate weekly review process with reflection, goal alignment, and planning.
When should I use Weekly?
Weekly fits situations like: tasks that involve Journaling and reflection.
How do I install Weekly in Claude Code?
Run `npx skills add ballred/obsidian-claude-pkm --skill weekly -a claude-code`. Or copy the skill folder (vault-template/.claude/skills/weekly in ballred/obsidian-claude-pkm) into .claude/skills/weekly in your project. Claude Code loads it when a task matches its description.
How do I install Weekly in Codex?
Run `npx skills add ballred/obsidian-claude-pkm --skill weekly -a codex`. Or copy the skill folder (vault-template/.claude/skills/weekly in ballred/obsidian-claude-pkm) into .agents/skills/weekly in your project. Codex loads it when a task matches its description.
Can I use Weekly 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 ballred/obsidian-claude-pkm --skill weekly -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, .gemini/skills/weekly, .github/skills/weekly and .opencode/skills/weekly in your project.
What does Weekly need to run?
SKILL.md names no scripts, command-line tools or credentials: Weekly is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet.
Does Weekly 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 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 use?
Weekly 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 use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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?
Skills that share tags, products or a category with Weekly: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 377 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?
ballred (a GitHub user) maintains it in ballred/obsidian-claude-pkm, which has 1,876 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on February 18, 2026.
Source: ballred/obsidian-claude-pkm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.