---
description: Query the SecondBrain vault knowledge graph for cross-project evergreen knowledge — conventions, tool behavior, client facts, patterns that generalize beyond one repo
---

**Scope:** vault at `~/Documents/SecondBrain` — cross-project evergreen knowledge, not codebase structure. For codebase structure and module relationships in the current repo, use `memory-project`.

Use this skill when you need to retrieve evergreen knowledge from the SecondBrain vault (conventions, tool/API behavior, client facts, cross-project patterns). For **episodic questions** ("what did we do last week", "when did X happen"), use memsearch instead.

## Query commands

```bash
# Explore a topic (start here)
graphify query "<topic>" --budget 2000

# Trace a relationship between two notes
graphify path "<note-a>" "<note-b>"

# Deep-dive a specific node
graphify explain "<node-name>"

# Bounded depth-first traversal
graphify query "<topic>" --dfs --budget 2000
```

## Tag-scoped retrieval (separate path — use with caution)

Facet-tag-based graph traversal is **not yet verified** (ADR-014 open). Whether shared facet tags (e.g. `client/acme`) create graph edges is unknown. Treat tag-based filtering as a distinct, experimental path — do not assume it works like graph traversal.

For tag-scoped queries, try:
```bash
graphify query "client/acme" --budget 2000
```
…and verify the results are actually tag-filtered before trusting them.

## Episodic questions → memsearch

For questions about sessions, events, or time-ordered history, use memsearch directly with natural language — do not use graphify for episodic retrieval.

## Writing to vault

Use `memory-write` when knowledge generalizes beyond the current repo. Routing heuristic: "Would this be useful outside this repo, next year?" If yes → vault via `memory-write`. If no → project-graph only (no persistent write needed). See `~/.claude/CLAUDE.md` for the full routing rule.