메뉴
Vault argues back. Pulls your own history to challenge current thinking. Use when making decisions, proposing architecture, or before committing to a direction. The vault is not a yes-man -- it remembers what you've learned the hard way.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Bridge unrelated vault domains. Find structural analogues between different areas. The vault's link graph knows connections you haven't seen.
Surface unnamed patterns from recent vault activity. Reads N days of notes and finds recurring themes you haven't explicitly named. The vault notices what you don't.
Promote scattered vault mentions into dedicated notes. When an idea, pattern, or concept reaches critical mass (3+ mentions across contexts), it deserves its own page. Graduate it from scattered references to first-class citizen.
Ingest external content and REWRITE existing vault pages with new context. Not just "add a note" -- one source touches 5-15 existing pages. Resolves contradictions, updates claims, creates synthesis pages. The vault grows by integration, not accumulation.
Save everything worth keeping from the current conversation to the Obsidian vault. Use when conversation produces decisions, research, tasks, project updates, or insights. Also triggers on session wrap-up ("done", "that's it", "thanks").
Load vault context progressively -- identity, navigation, current state. Use at session start or when context about the vault is needed. Token-budgeted: start light, go deeper only as needed.
| name | vault-challenge |
| description | Vault argues back. Pulls your own history to challenge current thinking. Use when making decisions, proposing architecture, or before committing to a direction. The vault is not a yes-man -- it remembers what you've learned the hard way. |
The vault challenges your current thinking using your own history.
Read _CLAUDE.md at vault root for folder map.
Identify the claim -- what is the user proposing, deciding, or assuming? If no explicit topic, challenge the most recent significant decision in conversation.
Deep vault search -- spawn 3 parallel search agents:
log.md for past instances where the user tried something similar. What happened? What was the lesson?Build the challenge:
## Challenge: [one-line summary of what's being questioned]
### Your Own Words
> [Direct quotes from vault notes that contradict or complicate the current plan]
### What Happened Last Time
[Concrete outcome from past attempt, with date and source note]
### The Steel-Man Counter
[Strongest possible argument against the current direction, built from vault evidence]
### What This Doesn't Mean
[Acknowledge where the current plan IS strong -- fair challenge, not nihilism]
### Questions You Should Answer Before Proceeding
1. [Specific question derived from evidence]
2. [Another]
3. [Another]
If no counter-evidence found -- say so honestly. "Vault has nothing against this -- either it's genuinely new territory or your notes don't cover this domain yet."
Append to log.md: ## [YYYY-MM-DD] challenge | [topic] -- [outcome: challenged/clear]
_CLAUDE.md Language section). The templates below are structural examples in English -- translate ALL headings, labels, and descriptions. E.g., Chinese user sees "## 挑战：", "### 你自己说过的话", "### 上次发生了什么", not English headings. Only direct quotes from vault notes stay in their original language.