メニュー
Use when asked to prepare a weekly reflection or summary of learnings, or when /weekly-learnings is invoked. Do NOT use for accountability or pattern analysis — use /weekly-signals for that.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
General-purpose Obsidian vault skill — use this whenever the user wants to do anything with their vault or personal notes. Covers reading notes by name, searching vault content, creating new notes, appending to existing ones, checking backlinks, and working with daily notes. Trigger immediately on phrases like: "look up my note on X", "add this to my vault", "what does my note say about Y", "find notes about Z", "log this to my vault", "update my daily note", "create a note for...", "what links to X", "search my vault for...", "show me what I know about...", "check my notes on...", or any time the user mentions Obsidian, their vault, or personal notes. If the user is asking about something they might have written down, reach for this skill first.
Use when asked to audit backlinks or repair the knowledge graph structure, or when /backlinks is invoked. Do NOT use for finding conceptual bridges between ideas — use /connect for that.
Map the branching question space from a topic — sub-questions, adjacent domains, meta-framings. Use when /bloom is invoked or Shane asks "what questions does X open up", "bloom on X". Do NOT use to trace how thinking evolved — that's /trace.
Use when Shane wants to pressure-test a belief, steelman an opposing view, or invoke /challenge. Do NOT use for confirming or validating a position.
Use when asked how knowledge has accumulated or compounded around a topic, or when /compound is invoked. Do NOT use for tracing evolution of thinking over time — use /trace for that.
Surface non-obvious cross-references between vault notes — connecting two concepts that aren't already explicitly linked. Use when /connect is invoked, when the user says "what does X have to do with Y", "is there a thread between these notes", "what connects these ideas", or when reviewing two superficially unrelated topics for shared structure. Do NOT use for direct backlinks (use /backlinks) or for surfacing patterns within a single topic (use /emerge).
| name | weekly-learnings |
| description | Use when asked to prepare a weekly reflection or summary of learnings, or when /weekly-learnings is invoked. Do NOT use for accountability or pattern analysis — use /weekly-signals for that. |
Synthesize the week's vault additions into a written reflection — key learnings, recurring themes, and open questions — as prose, not a bullet dump of activities.
Don't: use this for accountability analysis — that's /weekly-signals. Don't produce a bullet dump — synthesize into actual insights.
task: "Synthesize this week's vault additions and highlights into a meaningful weekly reflection or email update. What were the key learnings, themes, and open questions?"skill: "weekly-learnings"If Qwen is unavailable:
obsidian read file='Daily Notes/[date]' via bash for each date in the weekobsidian search query='[key theme or topic from the week]' limit=15 via bash to surface active notes from this week[argument] was provided, scope the reflection to that topic