菜单
Read and write notes in the Obsidian vault. Use for task logs, knowledge capture, and building context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Keep an Obsidian vault project's Topics folder up to date from its Tasks (and Events), and graduate evergreen Topics into shared domain folders. Use when the user wants to refresh or maintain a project's topics, find missing or new topics, add task-to-topic backlinks, audit topic interlinking, fix orphan topics, resolve duplicate/alias collisions, convert a dated retrospective into a Task, or promote a cross-cutting Topic out of the project into a domain folder (graduation). Assumes each project under the vault has Topics/ and Tasks/ sub-folders (and usually Events/).
Resolve and operate on Channing's Obsidian vault task notes by frontmatter type. Use when the user references a task note, Jira/GitHub issue tracked by a vault task, asks to inspect or continue task context, or asks to update/capture task state. Routes task-type values such as investigation, implementation, review, experiment, and note to the appropriate specialist skill.
Resolve and operate on Channing's Obsidian vault task notes by frontmatter type. Use when the user references a task note, Jira/GitHub issue tracked by a vault task, asks to inspect or continue task context, or asks to update/capture task state. Routes task-type values such as investigation, implementation, review, experiment, and note to the appropriate specialist skill.
Append a Decision Log entry, rewrite Current State, or resolve an Open Question on the active task note in Channing's vault. Use when the user says "log this decision", "update the task note", "add to the decision log", "current state has changed", "answer to the open question is X", asks for a prompt to continue the task in a new session, or otherwise asks to capture, record, or log something about the task being worked on.
Maintain a project's Research layer in an Obsidian vault — scaffold a research note from a question, spawn experiment tasks with backlinks, roll experiment findings up into the research note, sync open questions, and on conclusion graduate durable findings into Topics. Use when the user wants to start a piece of research, add an experiment to a research question, update a research note from its experiments, review open questions, or conclude a research question. Sibling of obsidian-topic-maintainer; assumes projects under the vault have Research/, Tasks/, Topics/ (and usually Events/) sub-folders.
Ask Perplexity a question by driving Channing's logged-in Chrome session, and report its answer. Use when the user says "ask Perplexity", "what does Perplexity say", "run this past Perplexity", or wants a Perplexity-sourced answer or second opinion. Avoids the paid Perplexity MCP server.
| name | vault |
| description | Read and write notes in the Obsidian vault. Use for task logs, knowledge capture, and building context. |
Location: ~/Documents/Notes/ (vault name: Notes)
~/Documents/Notes; do not use the obsidian CLI.[[YYYY-MM-DD]].date for all timestamps; never hardcode placeholders.status: open.| Type | Path |
|---|---|
| Tasks | Projects/<project>/Tasks/<YYYY-MM-DD HHMMSS> <ID> <title>.md |
| Daily notes | Journal/Daily Notes/<YYYY>/<YYYY-MM>/<YYYY-MM-DD>.md |
| Weekly notes | Journal/Weekly Notes/<YYYY>-W<WW>.md |
| Events | Projects/<project>/Events/<YYYY-MM-DD> <event type> <title>.md |
| Glossary | Projects/<project>/Glossary/ |
| Topics | Projects//Topics |
| Research | Projects/<project>/Research/<Title>.md |
| Templates | Vault Metadata/Templates/ |
VAULT="$HOME/Documents/Notes"
date +"%Y-%m-%d %H%M%S" # task filename
date +"%Y-%m-%d %H:%M" # log entry header
date -Iseconds # frontmatter
Use normal Unix tools (rg, find, sed, awk, perl, stat, mkdir, cp, mv, printf). Quote paths because project names contain spaces.
When creating a task note:
date +"%Y-%m-%d %H%M%S" for the filename timestamp.RH-1234.Vault Metadata/Templates/ and choose the relevant vault template.Tasks/; extract reusable steps into Recipes/.Task section ownership:
Current State, Decision Log, and Open Questions are maintained through task-note-update.task-note-update requires it.Link if it improves navigation, not just because a term matches.
Use aliased WikiLinks for ticket references:
[[2026-02-13 141534 RH-6949 Performance issue|RH-6949]]
Every mention of a Jira issue number in summaries, blockers, carryover, or task updates should be a WikiLink to its task note when a matching note exists.
Worth capturing when: principle applies across contexts, caused debugging time, method that saves time later, non-obvious choice with reasoning worth preserving, link to documentation.
Where to capture:
| Destination | When |
|---|---|
| Existing note | Extends/refines an existing topic (search first) |
| New note | Substantial, standalone, referenceable |
| Task log only | One-off detail that won't generalise |
| Project recipe | Repeatable steps specific to this project |