vault-journal
Vault Journal
Log structured research entries to today's daily note. Automatically discovers related vault projects and wikilinks them.
Workflow
-
Get the user's entry content — what they learned, worked on, or want to capture. Accept freeform text.
-
Read today's daily note:
obsidian daily:readNote whether it exists and what sections are already present.
-
If the daily note is empty or missing, create an initial structure first:
obsidian create path="YYYY-MM-DD.md" content="---\ndescription: Daily research log\ndate: YYYY-MM-DD\n---\n\n# YYYY-MM-DD\n\n## Research Log\n" silentUse today's actual date in YYYY-MM-DD format.
-
Search for related vault projects using keywords extracted from the user's entry:
obsidian search query="<keywords>" limit=10Run 1-2 searches with different keyword combinations. Extract matching folder names from results.
-
Compose the journal entry:
### HH:MM — Topic Title User's content here (cleaned up, concise). **Related:** [[folder_name/README]], [[another_folder/gemini3_summary]]- Use current time for HH:MM
- Keep the entry focused — 1-4 sentences max
- Only include related links if you found genuinely relevant folders (don't force it)
- If a source URL was mentioned, add
**Source:** <url>
-
Append the entry:
obsidian daily:append content="### HH:MM — Topic Title\nContent here.\n**Related:** [[folder/README]]\n" -
Confirm by reading back the daily note or reporting what was appended.
Tips
- Extract 2-4 specific keywords from the user's entry for search (e.g., "agent teams parallel" not just "agents")
- Link to
gemini3_summary.txtfor content-summary folders,README.mdfor code project folders - If the user says "log this conversation" or similar, summarize the current conversation's key insight as the entry
- Multiple entries in one session are fine — each gets its own
### HH:MMblock
More from az9713/claude-code-obsidian
vault-moc
Generate a Map of Content (MOC) note that categorizes and wikilinks vault project folders by theme. Can create a full vault index or a focused MOC for a specific category (e.g., "skills", "agents", "browser automation"). Use when wanting to create a navigational index of vault content.
2vault-save
Capture insights, solutions, or learnings from the current Claude Code conversation into a formatted Obsidian note with wikilinks. Use when the user wants to save something discovered during a conversation — a technique, a solution, a workflow decision, or a key insight.
2defuddle
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
1json-canvas
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
1obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
1obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
1