notelisted

Create an Obsidian-formatted markdown note documenting the current session topic. Use when the user says /note, 'save this to Obsidian', 'write a note about X', or asks to document a troubleshooting session, system concept, coding pattern, or workflow. Writes to ~/notes/<slug>.md and syncs to the configured Obsidian inbox. If an argument is provided after /note, use it as the topic; otherwise review the conversation.
escoffier-labs/brigade · ★ 72 · AI & Automation · score 80

Install: claude install-skill escoffier-labs/brigade

# /note - Create Obsidian-Formatted Notes Create an Obsidian-formatted markdown note and place it in `~/notes/`. Tell the user the exact file path and confirm the sync. If the user provided a topic argument after `/note`, use it as the topic. Otherwise, review the conversation to identify the topic. ## When to use Two distinct modes. Pick the right one before you start writing. | Mode | When | |------|------| | **Verbatim fix capture** | Troubleshooting sessions, root-causing bugs, recovering from incidents. The fix needs to be reproducible step-by-step. Future-you will paste the exact commands. | | **Summarize / concept** | Learning something new, capturing a workflow, documenting a system. The reader needs to understand *why*, not just *how*. | Common triggers: - Troubleshooting sessions - issues, errors, and the fix that worked - System concepts - how things work on Linux, networking, services, frameworks - Coding knowledge - languages, libraries, patterns, gotchas - Development workflows - tools, commands, configurations - Architecture decisions - what was chosen and why ## Process 1. Decide which mode applies. If unclear, ask: "Should I write this verbatim (reproducible) or summarize the concept?" 2. Review the conversation to identify the topic and pull the relevant commands, errors, paths. 3. Write the `.md` file to `~/notes/<topic-slug>.md`. 4. Sync to the configured Obsidian inbox (see "Sync target" below). 5. Tell the user the exact file path and confirm th