Menu
Run your weekly review. Checks drift, graduates ideas, audits vault health.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use whenever loading vault context, writing to the vault, ingesting captures, or starting a work session. Detects stale/conflicting notes, downgrades unverified old information, and annotates context with freshness labels. Guarded mode: warns and labels, never blocks (except completion claims lacking repo evidence).
Initialize an Obsidian vault for project tracking and personal context. Walks through vault creation, repo discovery, and scaffold setup.
any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report
Capture a thought, idea, or project concept into your Obsidian vault. Modes -- quick (fast idea), route (to specific project), incubate (new project inception), auto (choose based on context).
Close your day. Reviews what you accomplished, surfaces remaining loops, and offers to graduate ideas.
Create a new Obsidian vault for any topic and seed it with an initial knowledge base from web research. Use when the user wants to explore a new idea, start a research project, or create a dedicated space for a tangent they want to investigate later.
| name | weekly |
| description | Run your weekly review. Checks drift, graduates ideas, audits vault health. |
Tip: You can also use
/ritualwhich auto-selects based on time of day.
You are running the user's weekly review. This is a longer, more reflective workflow.
Call obsidian_check_in to get current state.
Call obsidian_drift with lookback_days=7. The tool extracts stated intentions from daily notes automatically (it looks for keywords like "intention", "goal", "commitment").
Present the drift analysis: coverage percentage, gaps, surprises. If no intentions were found in the vault, ask the user: "What were your intentions for this week?" and include their answer in the weekly summary.
Call obsidian_graduate_candidates with lookback_days=7.
If candidates found, present them and ask which to promote.
For each approved candidate, call obsidian_graduate_execute.
Call obsidian_vault_structure.
Report:
If orphan count is high, suggest linking strategies.
Call obsidian_log_daily with a summary section:
## Weekly Review
**Week of:** {date range}
### Drift
{drift summary}
### Graduated Ideas
{list of graduated notes, or "None this week"}
### Vault Health
{orphan count, dead ends, action items}
### Intentions for Next Week
{ask user or carry forward}
Ask: "What are your intentions for next week?"
Log their response to the daily note as stated intentions (these feed future drift analysis).