Menu
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
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
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.
Drift check for Obsidian: compare stated intentions against 30 days of vault behavior and surface verified priority gaps or avoidance questions. Use when the user asks "what am I avoiding?", "am I drifting?", "check my priorities vs behavior", "what's getting neglected?", or runs /spot-drift.
| name | daily |
| description | Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily. |
| user-invocable | true |
A 5–10 minute workday startup. The note is a cockpit the user revisits, not an AI-generated report.
Derive the real local date and weekday.
Completion: the run has a confirmed workday date or explicit weekend override.
Batch existence checks before creating anything.
| Period | Condition | Path | Template |
|---|---|---|---|
| Daily | every confirmed workday | 2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md | Daily Notes |
| Weekly | Monday | 2 - Areas/Daily Ops/YYYY/YYYY-Www.md | Weekly Planning |
| Monthly | first workday on/after month start | 2 - Areas/Goals/Monthly/M - Month YYYY.md | Monthly Goals |
| Quarterly | first workday on/after quarter start | 2 - Areas/Goals/Quaterly/Quaterly Goals - QN YYYY.md | Quarterly Goals |
Use obsidian read, then obsidian template:read ... resolve, then obsidian create. Never create an empty note. Preserve the Quaterly spelling.
Completion: today's note exists and every due periodic note exists or a concrete CLI failure is reported.
Read:
## Carry Forward section;MOCs/bases/Active Projects.base, falling back to 1 - Projects/;Treat carry-forward items as candidates, never commitments. Detect overload when the weekly note contains more than one outcome in a lane or today's note already contains multiple competing outcomes.
Completion: the user can see the relevant weekly lanes, exact carry-forward candidates with sources, and any overload warning.
Propose concise candidates from the gathered context, then ask the user to choose or write:
Do not choose these silently. Do not prepend carry-forward automatically. The user may edit the AI proposal manually in Obsidian instead of answering in chat; reread the note before writing anything else.
Completion: the outcome and next action are explicitly user-confirmed.
Write only the confirmed values into Daily Outcome, Next Action, and Active Focus Block.
Prefer a heading-targeted Obsidian patch tool when available. Otherwise show the exact replacement and use a read + overwrite flow only after approval. Never append duplicate headings.
Leave Parking Lot, Work Notes, Ideas Worth Sharing, and Ready to Resume ready for manual use during the day.
Completion: the daily note contains exactly one confirmed outcome, next action, and focus finish line.
Return only:
If Obsidian CLI fails, say: "Obsidian CLI isn't working — update Obsidian with CLI enabled."