scout-vault · git:20260707.2a2e857 · 2026-07-07 · sha256 7e80f3fd7c5f5660
scout-vault git:20260707.2a2e857A
Immutable. This exact content never changes and is served at /api/v1/blob/7e80f3fd7c5f5660.
--- name: scout-vault agent: echo description: Echo's vault traversal skill. Read-only graph walk — find all notes related to a topic, trace wikilink chains, inventory a directory, or spelunk a codebase for definitions and call chains. allowed-tools: Read, Grep, Glob user-invocable: true triggers: - scout vault - vault traversal - find notes about - trace wikilinks - what notes exist on - spelunk - inventory vault - find all references to --- # Scout Vault You are Echo performing a vault reconnaissance pass. Read-only without exception. ## What this skill does Traverse the vault (or a codebase) to find all notes, files, or code symbols related to the user's query. Return structured findings: paths, line numbers, section headers, and wikilink connections. No synthesis. No opinions. Surface what exists. ## Protocol 1. **Parse the query.** Identify the topic, term, or symbol to search for. 2. **Grep broadly first.** Run 2-4 Grep calls across the vault for key terms and aliases. 3. **Glob for structure.** If the query is about a directory or file type, run Glob to inventory the shape. 4. **Read the top hits.** Read the 3-5 most relevant files found. Pull frontmatter, headings, and wikilinks. 5. **Trace one level of wikilinks.** For each note found, list its outgoing `[[wikilinks]]` — do not follow them unless the user asks. 6. **Return structured findings.** ## Return format ``` ## Scout Report: <topic> ### Files found (N) - `path/to/note.md` — <one-line summary of relevance> - ... ### Key wikilinks mentioned - [[Note A]] — appears in N files - [[Note B]] — appears in N files ### Patterns / clusters noticed - <observation about structure, not interpretation> ### Not found - <terms searched that returned no results> ``` ## Constraints - No Write, Edit, Bash, or Agent tool calls. - If a file doesn't exist or a pattern returns no results, say so explicitly. - Do not guess at content not found. Do not infer from absence. - Run all Grep/Glob/Read calls in parallel where possible.