菜单
Foundational Obsidian vault context skill. Make sure to use this skill whenever the user mentions Obsidian, notes, vault, PARA, "in my notes", "check my vault", "second brain", or any interaction that touches the personal knowledge system. Provides vault structure, CLI reference, and PARA rules that all other obsidian skills build on.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | vault |
| description | Foundational Obsidian vault context skill. Make sure to use this skill whenever the user mentions Obsidian, notes, vault, PARA, "in my notes", "check my vault", "second brain", or any interaction that touches the personal knowledge system. Provides vault structure, CLI reference, and PARA rules that all other obsidian skills build on. |
Core knowledge layer for the Obsidian vault. Always load before any vault operation — this provides the map that makes every other skill accurate.
These skills act on the user's personal knowledge — the interpretation is theirs, not yours. This principle is shared by every ritual skill (daily, close-day, weekly, goals, spot-drift).
/Users/kriscard/obsidian-vault-kriscard
| Layer | Path | What belongs here |
|---|---|---|
| Inbox | 0 - Inbox/ | Unprocessed captures, raw ideas |
| Projects | 1 - Projects/ | Active deliverables with outcome + deadline |
| Areas | 2 - Areas/ | Ongoing responsibilities (no end date) |
| Resources | 3 - Resources/ | Reference material, TIL, wiki pages |
| Archives | 4 - Archives/ | Inactive projects, old resources |
PARA rule of thumb:
2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md # Daily notes
2 - Areas/Daily Ops/YYYY/YYYY-Www.md # Weekly notes (flat beside dailies)
2 - Areas/Goals/Quaterly/Quaterly Goals - QN YYYY.md # Quarterly goals (typo preserved)
2 - Areas/Goals/Monthly/M - Month YYYY.md # Monthly goals
2 - Areas/Goals/OKR Dashboard.base # OKR base query
3 - Resources/TIL/til-YYYY-MM-DD.md # TIL notes
0 - Inbox/ # Processing queue
Note: the quarterly folder is spelled "Quaterly" — preserve this to match the existing vault structure.
Use the native obsidian CLI for concrete operations. Common verbs: read, create, append,
prepend, move, files, search, search:context, tasks, task, orphans, deadends,
unresolved, backlinks, links, vault info=files, tags, property:read, property:set,
template:read, and base:query. Load references/cli-reference.md when exact syntax matters.
No patch command. The CLI cannot edit a specific section in place. To write to a note:
append/prepend when landing the content anywhere in the note is fine. When it must update or
replace a named section, ask the user: use the MCP obsidian_patch_content tool (supports
heading/block/frontmatter targeting), or recreate the note via read + create ... overwrite.
No daily:* commands. daily is only a flag on task/tasks, and that flag needs the Daily
Notes core plugin enabled (currently disabled). Work the daily note by its path:
TODAY="2 - Areas/Daily Ops/$(date +%Y)/$(date +%Y-%m-%d).md", then obsidian read path="$TODAY" /
append / prepend. Today's open tasks: obsidian tasks todo path="$TODAY" (note tasks path=
takes a file, not a folder).
If any obsidian command fails: tell the user "Obsidian CLI isn't working — update Obsidian with
CLI enabled."
Templates/ folder in vault root. Key templates:
Templates/Daily Notes.mdTemplates/Weekly Planning.mdTemplates/Project.mdTemplates/TIL.md| Priority | Load when | Reference |
|---|---|---|
| 1 — High | Full CLI command needed beyond the inline reference | references/cli-reference.md |
| 2 — High | obsidian-utils script commands or invocation syntax | references/obsidian-utils.md |
| 3 — Medium | Complete folder tree, metadata patterns, or naming conventions | references/detailed-structure.md |
| 4 — Medium | Tag taxonomy or tagging best practices | references/tagging-system.md |
| 5 — Medium | Which template to use for a note type | references/templates-guide.md |
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.
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.