bot-note

name	bot-note
description	Write a note in Obsidian based on the recent conversation
user_invocable	true

Bot Note

Write a note summarizing the recent conversation using obsidian-notes.

On invocation

1. Review the last several messages in the conversation to identify the substantive topic.
2. Pick a short, lowercase, descriptive name (e.g., jj workspace tool). Match the style of existing notes (obsidian-notes bot:list).
3. Write the note by piping content to obsidian-notes bot:create "<name>".

If invoked with an argument, treat it as instructions on what to include in the note (topic, scope, emphasis). The filename should always just be a good short representative title regardless of the argument.

Note format

The filename is the note title. Do not add a leading Markdown heading like # title inside the note body.

The key principle: the note should be very close to verbatim what was said in the conversation. If you gave a good explanation in the chat, copy it nearly verbatim into the note. Do not rewrite, reorganize, or "summarize" something that was already well-written. The conversation is the primary source — the note preserves it, lightly edited at most.

• Use the conversation's Q&A structure directly. The user's questions become blockquotes (>), your answers follow. If the user asked a follow-up question that drove the conversation forward, include it as a blockquote transition between sections — this is more authentic and clearer than invented section headings.
• When quoting, quote. Blockquotes (>) must use the user's actual words. It's fine to paraphrase or summarize the user, but not inside a blockquote — that's a quote.
• Copy your responses nearly verbatim. Light editing for flow is fine (removing "Let me look at..." transitions), but preserve the structure, tone, and level of detail. If the response used prose paragraphs, keep prose paragraphs. Don't break flowing text into bullet points or add headings that weren't there.
• Include concrete details. Links, file paths with line numbers, code snippets, command examples — the kind of thing that's hard to reconstruct later.
• Omit filler. No preamble, no "here's what we discussed," no meta-commentary about the note itself.

Before writing

Run obsidian-notes bot:list to check existing notes and avoid duplicating a topic. If a closely related note already exists, ask whether to append or create a new one. To append, pipe content to obsidian-notes bot:append "<name>". To edit an existing note directly, use obsidian-notes bot:path "<name>" to get the absolute filesystem path, then read/edit the file.

After writing

End with a single line of the form Note created at [<name>](<url>) (or Note updated at ... for appends/edits) where <name> is just the note filename without the Base files/Bot notes/ prefix or .md extension, and <url> is obsidian://open?vault=<vault>&file=<url-encoded-name>. Get the vault name from the basename of obsidian-notes bot:path "<name>" walked up two directories (i.e., the vault directory containing Base files/). The link must be clickable, so URL-encode spaces as %20.