scout-vault — Claude Code skill: what it does, how to install
The scout-vault Claude Code skill finds related vault notes, links, and code definitions. It runs for note discovery, vault inventory, or call-chain searches.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill scout-vault -a claude-codeWhat scout-vault does
scout-vault searches a vault or codebase for notes, files, and code symbols related to a query. It returns paths, line numbers, section headings, and wikilink connections in a structured report.
The skill searches terms and aliases first. For directory or file-type queries, it can inventory the structure, then read the most relevant files and list their outgoing [[wikilinks]]. It follows those links only when asked. Its tools are limited to Read, Grep, and Glob; it does not modify files.
What it helps with
- find notes matching a topic and its aliases
- inventory files by directory or file type
- trace outgoing wikilinks from relevant notes
- locate code symbols and call chains
Example prompts for the agent
- Find notes about release planning and trace their wikilinks.
- List the Markdown files in this vault.
- Find every reference to
UserServiceand show its call chains.
How to install scout-vault
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill scout-vault -a claude-code2Manually: put the files in place
~/.claude/skills/scout-vault/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/scout-vault/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill scout-vault -a codex2Manually: put the files in place
.agents/skills/scout-vault/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill scout-vault -a cursor2Manually: put the files in place
.cursor/skills/scout-vault/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/scout-vault2Manually: put the files in place
.github/skills/scout-vault/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill scout-vault -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/scout-vaultManually: put the files in place
.devin/skills/scout-vault/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill scout-vault -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about scout-vault
How do I install scout-vault in Claude Code?
Run npx skills add wrg32786/aigent-os --skill scout-vault -a claude-code. The skill file is at ~/.claude/skills/scout-vault/SKILL.md.
What does scout-vault do?
It searches for related notes, files, and code symbols, then reports paths, lines, headings, and wikilink connections.
Does scout-vault modify files?
No. It only uses Read, Grep, and Glob, and operates in read-only mode.
Source text
SKILL.md · MIT
--- name: scout-vault agent: echo description: "Trace vault wikilinks, inventory notes, or explore code definitions and call chains. Use when finding related notes, references, or scouting a vault. Read-only." 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.
© wrg32786 · MIT · wrg32786/aigent-os