adopt
Scaffold the PKM system onto an existing Obsidian vault. Scans your vault structure, maps folders interactively, and generates configuration — no template…
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.
$ npx -y skills add ballred/obsidian-claude-pkm --skill weekly --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/weeklyContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
Facilitates your weekly review process by creating a review note and guiding reflection on the past week while planning the next.
Invoke with `/weekly` or ask Claude to help with your weekly review.
/weekly
1. **Creates Weekly Review Note**
2. **Guides Review Process**
3. **Automates Housekeeping**
The skill guides you through:
1. **"What were your top 3 wins this week?"**
2. **"What were your main challenges?"**
3. **"What's your ONE big thing next week?"**
# 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: ## Notes
Suggest moving daily notes older than 30 days to Archives.
For each active project:
Calculate habit success rates from daily notes:
The weekly skill uses session tasks to show progress through the 3-phase review.
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..."
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.
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 updates
When invoking `/weekly`, you can request the team-based approach:
/weekly "Use the team approach for a thorough review"
The team lead: 1. Spawns three agents to work in parallel 2. Collector reads daily notes and extracts highlights 3. Goal-analyzer reads all goal files and calculates progress 4. Project-scanner reads all project CLAUDE.md files for status 5. Team lead synthesizes findings into the weekly review note
This makes the review faster (parallel collection) and more thorou
Not another PKM starter kit. This is an execution system that connects your 3-year vision to what you do today — and holds you accountable with AI. Every layer connects. /daily surfaces your ONE Big Thing from the weekly review. /weekly shows project progress.
Scaffold the PKM system onto an existing Obsidian vault. Scans your vault structure, maps folders interactively, and generates configuration — no template…
Find broken wiki-links in the vault. Read-only analysis — scans for [[links]] and verifies target files exist. No writes, no dependencies.
Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily…
Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives.…
Monthly review and planning. Roll up weekly reviews, check quarterly milestones, set next month's focus. Use at end of month or start of new month.
Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or…