Analyze relationships in a bounded set of Obsidian notes: candidate links, repeated patterns, contradictions, and follow-up opportunities. Load when user asks to find connections, suggest wikilinks, or surface contradictions. Do NOT use for inbox triage, weekly synthesis, or note promotion.
Route raw Obsidian inbox captures into keep/promote/project/archive/deep-read. Load when user asks to triage inbox, sort captures, or process fleeting notes. Do NOT use for relationship analysis, synthesis, health diagnosis, or note creation.
Decide whether material should become a stable, reusable, linkable Obsidian note. Load when user asks to upgrade, promote, or stabilize material into a formal note. Do NOT use for inbox triage, link discovery, or weekly synthesis.
Vault operation safety layer for all Obsidian MCP operations. Load when any vault read/write/search/tag/edit/verify is needed. Do NOT use alone for workflow decisions; combine with companion skill.
Diagnose drift across the OpenCode + Obsidian context stack when vault notes, config, or host reality no longer align. Load when context feels stale or records disagree with reality. Do NOT use for triage, synthesis, or vault CRUD.
Diagnose whether an Obsidian knowledge workflow produces cognitive return or is becoming a passive archive. Load when vault feels archival or dead. Do NOT use for inbox triage, link review, synthesis, or direct restructuring.
Extract time-window meaning from recent Obsidian notes: emerging thesis, contradictions, gaps, exactly one action, exactly one question. Load when user asks for weekly synthesis, what recent notes mean, or next action. Do NOT use for inbox triage, link-only review, or note promotion.