Skip to main content
skill CX Codex

journal · thoreinstein — Claude Code skill: Obsidian daily note, how to install

journal — a skill for your Obsidian daily note: it reads today's entry, appends quick logs and builds weekly or end-of-day reviews from CLI sessions.

ISC ★ 102 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thoreinstein/gemini-obsidian --skill journal -a claude-code
Open on GitHub

What journal does

The skill handles the daily note inside an Obsidian vault. Call it with nothing and it pulls today's entry, gives you the short version of tasks and events, then asks whether to add anything. Text passed after the call lands in the log under a Notes heading, and you get a confirmation back.

Entries go into fixed sections: Work Log for progress, Notes for observations, Ideas, Meetings with action items. Ask for a weekly review and the skill lists notes from the Daily Notes subfolder, reads them and sums up themes plus anything still open.

/recap is the other workflow: obsidian_harvest_cli_sessions collects the day's CLI sessions, the skill groups them by project and repository and appends the result to the daily note. Supply a template and its headings are kept. Everything runs through the obsidian_* tools, so without the Obsidian vault behind them the calls go nowhere.

What it helps with

  • log a thought into the daily note in one line
  • build a weekly review from notes in Daily Notes
  • file entries under Work Log, Ideas or Meetings
  • turn a day of CLI sessions into a per-project summary
  • check what today's note already contains

Example prompts for the agent

  • What's in my daily note for today?
  • /journal Standup notes: blocked on the auth migration until Tuesday
  • Run /obsidian:recap for today and append the summary to Work Log

How to install journal

1Skills CLI (Vercel)

npx skills add thoreinstein/gemini-obsidian --skill journal -a claude-code

2Manually: put the files in place

~/.claude/skills/journal/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/journal/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about journal

How do I install journal in Claude Code?

Run npx skills add thoreinstein/gemini-obsidian --skill journal -a claude-code. The skill file ends up at ~/.claude/skills/journal/SKILL.md.

What does the journal skill do?

It opens today's note in an Obsidian vault, appends logs to it and assembles reviews, both weekly and for a single day of CLI work.

Which headings does journal write to?

Work Log, Notes, Ideas and Meetings. Quick text without a heading of your own goes to Notes, while /recap output goes to Work Log.

Source text

SKILL.md · ISC
---
name: journal
description: >-
  Use when the user wants to work with their daily note — view today's entry,
  add a log, do a daily review, or capture quick thoughts. Covers all daily
  note workflows.
---

# Daily Journal

Work with today's daily note in the Obsidian vault.

## Default Action (no arguments)

1. Call `obsidian_get_daily_note` to retrieve today's note
2. Summarize key tasks, events, or entries
3. Ask if the user wants to add anything

## Quick Capture (with arguments)

If the user provides text after `/journal`, log it:

1. Call `obsidian_append_daily_log` with heading "Notes" and the user's text
2. Confirm what was logged

## Common Headings

When logging entries, use these standard headings:
- **Work Log** — tasks, progress, accomplishments
- **Notes** — general thoughts and observations
- **Ideas** — creative ideas and inspirations
- **Meetings** — meeting notes and action items

## Weekly Review

If the user asks for a "weekly review":
1. List recent daily notes via `obsidian_list_notes` (subfolder "Daily Notes")
2. Read each day's note
3. Summarize themes, accomplishments, and open items

## Multi-Session Daily Activity Recap (/recap)

Use this workflow when the user wants to summarize today's work across workspaces, consolidate daily activities, or runs `/recap` / `/obsidian:recap`:

1. **Harvest Sessions**:
   Call `obsidian_harvest_cli_sessions` with `date` (defaults to today) and optional `template_path`.

2. **Template-Driven Formatting**:
   - **When a custom template is provided (`templateContent`)**:
     Analyze the template structure and map the harvested activities into the corresponding sections/placeholders (e.g. accomplishments, engineering milestones, reflections, or next steps) while strictly preserving the user's template headings and formatting.
   - **When no template is provided (Default Universal Format)**:
     Synthesize a clean, structured project activity summary:
     - Group activities by project or repository name.
     - For each project, extract:
       - **Accomplishments**: Key problems solved, features implemented, or tasks completed (derived from user prompts and topic transitions).
       - **Engineering Milestones**: Meaningful operations such as Git commits, Pull Requests/reviews, issue keys, or automated tests run.
       - **Topics & Explorations**: Core technical topics, investigations, or architectural decisions discussed.

3. **Vault Ingestion**:
   Append the synthesized summary to today's daily note under the designated heading (defaults to `Work Log` or the heading specified by the user/template) via `obsidian_append_daily_log`.

4. **Response**:
   Present the plain-text summary to the user for immediate review.

© thoreinstein · ISC · thoreinstein/gemini-obsidian

Similar skills

All skills for Notes, tasks and projects →

journal by other authors comes first.

From the same set15

The whole set →
research research is a Claude Code skill that searches an Obsidian vault, reads relevant notes, and follows links to answer questions about stored knowledge. CX Codex +1 ★ 102repo stars moc-update moc-update finds the Maps of Content (MOCs) in an Obsidian vault that should link to a freshly created Engineering/ note. Fires on prompts like “update MOC” or “which MOCs”. CX Codex +1 ★ 102repo stars link-audit link-audit audits Obsidian vaults for broken wikilinks and orphaned notes. Helps repair target paths or generate new links via semantic search. CX Codex +1 ★ 102repo stars knowledge This skill finds ideas repeated across project notes and drafts a shared note in Engineering/. Use it to turn recurring project knowledge into a linked concept. CX Codex +1 ★ 102repo stars obsidian-companion obsidian-companion connects your assistant to an Obsidian vault to edit files, inspect broken wikilinks, and run queries using local RAG. CX Codex +1 ★ 102repo stars cross-linker cross-linker finds mentions of other Obsidian notes that lack wikilinks, then sorts possible links by confidence. Use it to connect notes across a chosen folder or a wider vault scope. CX Codex +1 ★ 102repo stars vault-lint vault-lint audits an Obsidian vault across five checks and returns a prioritised report with fixes you accept one at a time. CX Codex +1 ★ 102repo stars wiki-ingest wiki-ingest distills external files, transcripts, and Readwise exports into structured Obsidian notes with RAG-based deduplication and source tracking. CX Codex +1 ★ 102repo stars

Project sponsors

Companies that keep this analytics open