メニュー
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.
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.
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).
Use when asked to find contradictions or inconsistencies in thinking, or when /contradict is invoked. Do NOT use for pressure-testing a single belief — use /challenge for that.
| name | bloom |
| description | 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. |
Expand a topic into its question space as a tree — questions that nest and relate, not a flat enumeration, with Level 3 meta-framings that challenge how the topic is posed.
Don't: flatten the bloom into a list. Don't surface only obvious sub-questions — Level 3 reframings that challenge the topic's framing are where the value is.
task: "Vault access (bash only, no MCP tools): obsidian search query='TERM' limit=10, obsidian read file='Note Name' (no .md). Map how '[argument]' branches into sub-questions across the vault. Level 1: immediate follow-on questions. Level 2: adjacent topics and domains with shared structure. Level 3: meta-questions that challenge how '[argument]' is framed. Note which branches are already explored in the vault vs. blank. Suggest 1–2 unexplored branches most worth pursuing. Output as a structured tree, not a flat list."skill: "bloom"If Qwen is unavailable:
obsidian search query='[argument]' limit=10 via bash; read relevant notes.