Menu
Process accumulated inbox notes through the full pipeline (ingest, enrich, route, connect, link). User-facing orchestrator.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when investigating an agent-harness CLI's internals (Claude Code, codex, opencode, or similar): extracting the system prompt or tool descriptions, finding what code path produces a specific UI message, decoding minified function names or Rust symbols, understanding undocumented config keys, or otherwise spelunking a shipped binary (or its pinned source) to figure out how the tool actually behaves.
Use when about to lock in a non-trivial or hard-to-reverse decision, fire AskUserQuestion to offload a call, proceed on your own preferred option, or assert something is done / found / tested / fixed / "that's how it works" — especially when the basis is memory, the handoff, the first framing, or an unchecked assumption rather than something verified this session. Also invoked as /gut-check. Use even when you feel confident; confidence is the symptom, not the all-clear.
Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.
Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that's distinct from", "versus"), bolded terms followed by colons, or an embedded "X, Y, and Z" series. Composes with prose-clarity skills (concision) and voice skills (personality) rather than replacing them. Skip for source code and for casual one-line replies where formatting reads as overkill.
| name | process-inbox |
| description | Process accumulated inbox notes through the full pipeline (ingest, enrich, route, connect, link). User-facing orchestrator. |
| allowed-tools | ["Read(~/.claude/vaults/**/CLAUDE.md)","Read(~/.claude/vaults/**/.obsidian/*.json)","Read(~/.claude/vaults/**/*.md)","Read(~/.claude/vaults/**/.routing-memory.md)","Write(~/.claude/vaults/**/*.md)","Write(~/.claude/vaults/**/.routing-memory.md)","Edit(~/.claude/vaults/**/*.md)","Edit(~/.claude/vaults/**/.routing-memory.md)","Bash(npx @techpickles/sb:*)","Bash(which:qmd)","Bash(qmd:query *)","Bash(qmd:collection list)","Bash(qmd:get *)","Bash(qmd:status)"] |
Process accumulated inbox notes through the full pipeline: ingest, enrich, route, connect, link to daily note.
See references/pipeline.md for stage definitions and status flow.
npx @techpickles/sb config default
npx @techpickles/sb config vaults
If no vault configured:
Second brain not configured. Run /second-brain:setup first.
Load skill references:
second-brain:obsidian for tool mechanicsreferences/pipeline.md for stage definitionsreferences/routing-memory.md for learning loopreferences/routing.md for scoring algorithmreferences/connecting.md for connection discoveryreferences/daily-linking.md for daily note linkingreferences/sb-cli.md for sb command referencenpx @techpickles/sb inbox list --detail
Parse the JSON response. Group notes by status field (notes without status are raw).
Check for stale notes (captured more than 14 days ago based on captured frontmatter field).
Present summary:
Inbox: {total} notes
{n} raw (session notes awaiting ingestion)
{n} ingested (insights awaiting enrichment)
{n} enriched (notes awaiting routing)
{n} pending-review (need your input)
{n} routed (awaiting connection)
{n} connected (awaiting daily linking)
{If stale notes exist:}
Heads up: {n} notes have been in the inbox for over 2 weeks.
If inbox is empty:
Inbox is empty. Nothing to process.
Work through notes in pipeline order. Each stage picks up notes at its expected input status.
For each note with status: raw and type: session-notes:
ingest skill to split into individual insight notesIngested: {session filename} -> {n} insightsFor each note with status: ingested and type: insight:
enrich skill to create proper zettelkasten notesEnriched: {filename}For each note with status: enriched:
route skillRouted: {filename} -> {destination}references/routing-memory.mdAlso process any pre-existing pending-review notes from previous runs.
For each note with status: routed:
connect skillSkipped connections: qmd not available (once, not per note)For each note with status: connected:
link-daily skillsb daily append call when possibleLinked {n} notes to daily notePipeline complete:
{n} session notes ingested -> {m} insights extracted
{n} insights enriched
{n} notes routed ({auto} auto, {manual} manual)
{n} notes connected ({links} links added)
{n} notes linked to daily note
{n} notes still pending review