Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From learning-loop
Captures insights mid-conversation to 0-inbox/ with zero friction. Infers note content from context or accepts title/body arguments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/learning-loop:quick-noteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Captures a single insight to `0-inbox/` mid-conversation. No preview, no approval, no multi-agent pipeline. One subagent, one note, one confirmation line.
Captures a single insight to 0-inbox/ mid-conversation. No preview, no approval, no multi-agent pipeline. One subagent, one note, one confirmation line.
/learning-loop:quick-note: infer the insight from conversation context/learning-loop:quick-note "insight as title": user provides the title/learning-loop:quick-note "title" "body": user provides everythingIf no args: Read the recent conversation. Identify the most capture-worthy insight: a decision made, pattern discovered, or connection drawn. If nothing stands out, tell the user and stop.
If title only: Use it as the insight title. Derive body from conversation context.
If title + body: Use both as provided.
Spawn a single note-writer subagent (subagent_type: learning-loop:note-writer) with this prompt:
Write a quick inbox note for the Obsidian vault.
Insight: <title>
Context: <body or conversation context summary, 2-3 sentences max>
Source project: <current project name or "conversation">
Date: <today YYYY-MM-DD>
Destination: 0-inbox/
Before writing, run this command to find related vault notes:
node PLUGIN/scripts/vault-search.mjs search "<key terms from insight>" --rerank
Use the top 1-3 relevant results as wiki-links in the note.
Write the note directly to {{VAULT}}/0-inbox/<filename>.md using the Write tool.
Return the filename and title when done.
The note-writer is a subagent. Its Write call bypassed PostToolUse, so backlinks and edge inference didn't run. Replay them on the returned path:
printf '%s\n' "$NOTE_PATH" \
| node "${CLAUDE_PLUGIN_ROOT}/scripts/sweep-hook-replay.mjs" --stdin
Where $NOTE_PATH is constructed from the agent's response (e.g. {{VAULT}}/0-inbox/<filename>, where <filename> is the kebab-case filename note-writer returned). See skills/_shared/hook-replay.md for context.
Show one line:
Captured: "Note Title" → 0-inbox/filename.md
Nothing else. No summary. No follow-up suggestions. Back to what we were doing.
/deepen exists for a reason.npx claudepluginhub robinslange/learning-loop --plugin learning-loopCaptures lightweight short-form notes (observations, insights, strategy snippets) to `meta/notes/` with optional tags and artifact linkage. Use when you want to quickly jot something down.
Processes Obsidian Inbox items into a knowledge base: reads source, discusses key ideas, then files synthesized notes. Also saves conversation answers as permanent wiki pages.
Files conversation insights into an Obsidian wiki vault as structured notes. Detects note type, generates frontmatter, and updates index/log/hot cache.