Stats
Actions
Tags
From alive
Searches decisions, people, files, references, insights, and logs across all walnuts in priority order from frontmatter, insights, tasks, files, manifests, and context sources. Useful for locating captured information by location.
How this skill is triggered — by the user, by Claude, or both
Slash command
/alive:search-worldThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search across the world. One verb for all retrieval.
Search across the world. One verb for all retrieval.
Priority order — fastest and highest signal first:
Scan _kernel/key.md across all walnuts. Matches on: type, goal, people names, tags, links, reference descriptions.
Scan _kernel/insights.md across relevant walnuts. Domain knowledge that persists — "Nova Station test windows are Tue-Thu only."
Search _kernel/log.md entries. Signed decisions, session summaries, what happened when. Frontmatter first (last-entry, summary), then entry bodies.
Use tasks.py list to query tasks across walnuts. Find tasks by status, age, attribution.
Scan */ across walnuts (bundles are flat in walnut root). Find drafts by name, version, age, squirrel attribution.
Search */context.manifest.yaml files across walnuts (bundles are flat in walnut root). Match on frontmatter: type, date, source, participants, subject.
Load actual raw files. Only on explicit request — "read me that email from Jax."
If steps 1-7 return nothing and the user believes it exists, automatically fan out to configured context sources before reporting "not found." Check .alive/preferences.yaml context_sources: for what's available — any configured MCP server, sync script, or API connection is a valid search target.
One-hop inference applies: if the user says "the setup guide I sent Sarah" and an email integration is configured, that's enough to trigger a search without being asked. The system should resolve across its full context surface — local files are not the only source of truth.
╭─ 🐿️ not found in local files
│ Checking configured context sources...
│ → Found in email: sent to Sarah, Mar 15, "Setup Guide v2"
│
│ ▸ What now?
│ 1. Read it
│ 2. Capture it to a walnut
│ 3. Skip
╰─
Never say "not found" if context sources haven't been checked.
Find searches across ALL walnuts by default. Results show which walnut each match came from.
╭─ 🐿️ found 3 matches for "radiation shielding"
│
│ 1. nova-station / insights.md
│ "Ceramic composites outperform aluminum at 3x the cost"
│
│ 2. nova-station / _kernel/log.md — 2026-02-23
│ Decision: go with hybrid shielding approach
│
│ 3. nova-station / bundles/research/
│ 2026-02-23-radiation-shielding-options.md
│
│ number to load, or refine search.
╰─
When a match is found, surface connected walnuts:
╭─ 🐿️ [[ryn-okata]] is mentioned in this entry.
│ She also appears in: nova-station, glass-cathedral
│ Load her context?
╰─
"What happened last week" → filter log entries by date range, show across all active walnuts.
"What changed since Tuesday" → scan _kernel/now.json updated timestamps + recent log entries.
"History of nova-station" → show _kernel/log.md frontmatter (entry count, summary) + offer to load recent entries.
npx claudepluginhub alivecontext/alive --plugin aliveSearches sayou workspace for past decisions, research, notes via structured path/frontmatter, content grep, and semantic search. Useful for recalling prior workspace knowledge.
Searches Claude's memory tiers (working memory, registers, daily logs, archive) for relevant information using grep/ripgrep keyword matching. Groups results by source with confidence, dates, and timestamps.
Searches an Obsidian vault for past decisions, troubleshooting history, and project knowledge when the user asks about previous work or how something was done. Supports keyword, type-aware, and catalog search.