joplin-capturing-notes

Capturing notes in Joplin

See the using-joplin skill for the connection check and shared conventions (resolve names to IDs, truncated, delete caution).

Steps

1. Find the target notebook. Call list_notebooks and match the user's intended notebook by title (use the nested tree to disambiguate notebooks with the same name under different parents). If it doesn't exist and the user wants it created, call create_notebook with the title and an optional parent_id to nest it.
2. Choose the format. Default to markdown. Use html only when the content is genuinely HTML (e.g. clipped rich content). The body you pass is stored as-is in that format.
3. Create the note. Call create_note with title, body, format, and notebook_id. Capture the returned note id.
4. Apply tags (separate step). create_note does not take tags. For each desired tag: ensure it exists via list_tags (create it with create_tag if missing), then attach it with tag_note (note id + tag id).
5. Report the created note's id and where it landed.

Diagrams and math

Joplin renders Mermaid (```mermaid fences) and KaTeX ($...$ inline, $$...$$ display) in Markdown notes. Follow "Diagrams and math" in the using-joplin skill. In short:

• Add a diagram or formula only when it genuinely helps (a process, architecture, sequence, or maths), never as decoration.
• If the mermaid or katex skill is available, use it to write the block, then embed it in the body. If not, write a plain fence or $/$$ math yourself; the capture still works.
• Keep the note format as markdown (step 2); neither renders in html notes.
• Verbatim captures (slides, documents, anything the user wants copied exactly): only include diagrams or formulas present in the source. Never invent or embellish one.
• You may offer to install a missing companion skill, but only run the install after an explicit yes, and don't ask again this session if they decline.