.claude/skills/vault/SKILL.md
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
npx skillsauth add alfredolopez80/multi-agent-ralph-loop vaultInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Karpathy-inspired knowledge pipeline: Ingest -> Compile -> Query.
The vault is a PRIVATE directory OUTSIDE the public repo:
$HOME/Documents/Obsidian/MiVault/ (configurable)This skill teaches HOW to use the vault (framework). It does NOT contain vault data.
/vault initCreate vault structure:
VAULT_DIR="${VAULT_DIR:-$HOME/Documents/Obsidian/MiVault}"
# 3-layer structure
mkdir -p "$VAULT_DIR"/{global/{raw/articles,raw/papers,raw/images,wiki,output,decisions},projects,_templates}
# Create vault index
echo "# Vault Index" > "$VAULT_DIR/_vault-index.md"
echo "# Project Index" > "$VAULT_DIR/projects/_project-index.md"
Or run: scripts/setup-obsidian-vault.sh
/vault save <classification> <content>Save a learning to the vault:
| Classification | Destination | Example |
|---|---|---|
| GREEN | $VAULT_DIR/global/wiki/{category}/ | Generic patterns (TypeScript, React) |
| YELLOW | $VAULT_DIR/projects/{project}/wiki/ | Project-specific knowledge |
| RED | DISCARDED (never saved) | Contains secrets or sensitive info |
/vault search <query>Search vault for relevant knowledge:
global/wiki/ + projects/{current-project}/projects/{other-project}/ (isolation)/vault indexUpdate all _index.md files in the vault:
.md files in global/wiki/ and projects/*/wiki/_vault-index.md and projects/_project-index.md/vault compileCompile raw notes into wiki articles (Karpathy pipeline):
raw/ and lessons/ directorieswiki/_index.md.claude/rules/learned/Graduation criteria:
/vault demote <rule>Revert a graduated rule back to vault if incorrect:
.claude/rules/learned/{category}.mdstatus: demoted| Component | Integration |
|---|---|
| session-accumulator.sh | PostToolUse hook captures learnings during session |
| vault-graduation.sh | SessionStart hook promotes high-confidence learnings to rules |
| /exit-review | End-of-session GREEN/YELLOW/RED classification |
| smart-memory-search.sh | Adds vault as 5th search source (parallel) |
| pre-compact-handoff.sh | Saves vault context before compaction |
global/wiki/ + projects/{its-own-name}/projects/{other-project}/ directlyglobal/wiki/| Excuse | Rebuttal | |---|---| | "The vault is just another notes system" | The vault graduates to rules. Notes don't change behavior. | | "I'll save it to memory instead" | Memory is ephemeral (25KB). Vault is curated knowledge. | | "Classification is overhead" | 3 seconds to classify saves hours of future searching. | | "RED content is useful for context" | RED = secrets. Never store. Period. |
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
development
End-of-session learning classification. Reviews accumulated learnings and classifies each as GREEN (generic, goes to global wiki), YELLOW (project-specific, goes to project wiki), or RED (sensitive, discarded). Triggered at session end via Stop hook. Use when: (1) session ending, (2) manual review of learnings. Triggers: /exit-review, 'review learnings', 'classify learnings'.