insight

Capture Insight

Capture an insight from the current conversation to your Obsidian vault inbox.

This command captures raw insights quickly. Processing, routing, and connection discovery happen later via /second-brain:process-inbox.

Step 1: Load Configuration

Load configuration using sb CLI:

npx @techpickles/sb config default    # Get default vault name
npx @techpickles/sb config vaults     # List all configured vaults

If sb is not available, inform user:

sb CLI is required but not available. Install Node.js and npm, then try again.
Or install globally for faster execution: npm i -g @techpickles/sb

If no vaults are configured, inform user:

Second brain not configured. Run /second-brain:setup first.

Use the symlink path ~/.claude/vaults/{name} to access the vault for reading CLAUDE.md (e.g., ~/.claude/vaults/primary).

Read vault's CLAUDE.md for structure rules.

Load skill references:

• second-brain:obsidian for tool mechanics
• references/sb-cli.md for sb invocation details
• references/zettelkasten.md for naming

Step 2: Identify the Insight

If argument provided: Use the argument as the insight to capture.

If no argument: Ask: "What insight would you like to capture?"

Also review recent conversation context to suggest what might be worth capturing.

Step 3: Create or Append to Session Notes

Session notes files collect all insights from a conversation in one place, with cheap metadata attached at capture time.

Check if session file already exists in this conversation.

If this is the first /insight command in this conversation:

1. Create a new session notes file using sb CLI:

npx @techpickles/sb note create \
  --source auto \
  --title "{session context}"

Generate the title from conversation context: repo name, current branch, work item ID if your context names one, and what you're working on (e.g., "Debugging auth timeout in zenpayroll").

The file is created with frontmatter. Read the created file to preserve the exact frontmatter sb wrote.