Menu
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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
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.
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 | goals |
| description | 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. |
| user-invocable | true |
| argument-hint | [quarterly | monthly | weekly — omit to choose] |
Check-in and update goal notes across quarterly, monthly, and weekly levels. Goal reviews only matter if they connect to action — this skill always ends with concrete next steps, not just status updates.
Shared principle (canonical version in the vault skill): never guess, deduce, or fill gaps with
assumptions about the user's notes, priorities, or intent. If you don't know — a date range, what
counts as a win, which goals are active — ask. Before writing any synthesis or judgment into a
note, show your draft with its source and get explicit confirmation. Missing data is not permission
to invent.
If $ARGUMENTS is provided, validate it against quarterly, monthly, or weekly. If it is
missing or anything else, ask via AskUserQuestion:
"Which goals review would you like?"
- Quarterly
- Monthly
- Weekly
# OKR dashboard
obsidian base:query path="2 - Areas/Goals/OKR Dashboard.base" format=json 2>/dev/null
# Active projects (goal alignment check)
obsidian files folder="1 - Projects/" format=json
Read this week's note using the same flat path logic as the weekly skill. Derive the ISO week-year
from the week being reviewed, not hardcoded placeholders:
WEEK="<ISO week-year>-W<week>" # e.g. 2026-W01; use ISO week-year for cross-year weeks
YEAR="<ISO week-year>"
obsidian read path="2 - Areas/Daily Ops/$YEAR/$WEEK.md"
Check: are this week's planned lanes connected to monthly goals? Identify any monthly goal with no
verified weekly evidence as a question. For next week, confirm up to one Roofr, Markly, Learning,
and Public Artifact outcome; not-planned is valid.
Update the weekly note's named lane and Next Week Prepared sections after approval.
MONTHLY="2 - Areas/Goals/Monthly/M - $(date +'%B %Y').md"
obsidian read path="$MONTHLY" 2>/dev/null || \
obsidian create path="$MONTHLY" template="Monthly Goals"
Check quarterly progress: which quarterly objectives is this month advancing? Flag at-risk goals only when source-bound evidence exists: a missed milestone, elapsed due date, explicit blocker, or user-confirmed concern. Otherwise frame it as a question to verify.
Update with: progress status per goal, adjustments, and next month's focus.
Read the current quarterly note:
# Note: folder and file use "Quaterly" spelling — preserve exactly.
# Derive Q<N> and YYYY from the review date.
QTR_PATH="2 - Areas/Goals/Quaterly/Quaterly Goals - Q<N> YYYY.md"
obsidian read path="$QTR_PATH" 2>/dev/null
For a mid-quarter check-in: assess progress, flag at-risk objectives only from missed milestones, elapsed due dates, explicit blockers, or user-confirmed concerns, and surface blockers.
For a quarter wrap + new quarter: review previous quarter outcomes (hit / partial / missed), extract learnings, then set new quarterly objectives broken into monthly milestones.
Ask via AskUserQuestion: "Is this a check-in or quarter transition?"
For new quarter setup, create the new quarterly note:
obsidian create path="2 - Areas/Goals/Quaterly/Quaterly Goals - Q<N> YYYY.md" \
template="Quarterly Goals"
Update the relevant note with:
The CLI has no patch. If the update can append to the note, use obsidian append. If it must
change a specific section, ask the user: MCP obsidian_patch_content (heading-targeted) or read +
create ... overwrite. Always show a preview before writing and wait for explicit approval.
Quaterly (not "Quarterly") — this is a known vault typo. Match it
exactly or file creation will break.