AnthropicWorkflows

· Power user

Illustration: an empty file folder beside a small desk tent calendar, in black and white.
Illustration

Reported, not yet confirmed.

Build an Obsidian morning brief with Claude Code skills

James Wilkins's scheduled Claude Code routine maintains an Obsidian task vault and writes the daily note he runs his day from.

James Wilkins (Apr 8, 2026; checked Oct 14, 2026) described, as of April, a Claude Code morning briefing that keeps an Obsidian task vault tidy and writes the daily note he runs his day from. Two custom skills sit under it: obsidian-cli for vault reads and writes through Obsidian's own CLI, and todo-vault for the note types and routines. The claim is self-reported. We have not run it.

What it replaces#

Before: syncing yesterday's checkboxes back into task notes, archiving finished items, updating habit streaks, compacting old daily notes, and building today's list by hand. After: a scheduled eleven-step routine does that maintenance, then writes one daily note with today's tasks, habits, a seven-day forward view, and a weather summary.

Wilkins's goal is to "offload as much of that maintenance overhead to Claude as possible" so the vault structure stays useful without becoming a second job.

How it works#

  1. Install or write an obsidian-cli skill so Claude Code talks to the vault through Obsidian's CLI instead of raw file edits. Wilkins says direct filesystem writes often break links because Obsidian never sees them.
  2. Add a todo-vault skill that defines the note types (tasks, reminders, repeated tasks, habits, events, notes) and where archives go.
  3. Keep two context files in the vault: context.md (your goals, constraints, in-progress work) that you maintain, and agent-notes.md (behavioral observations) that the agent maintains and compacts.
  4. Schedule the morning briefing. Wilkins's routine syncs yesterday's checkbox states into note metadata, archives completed items, updates habit streaks, compacts old daily notes into year/month folders, scans the next seven days, fetches weather, reads the context files, carries unfinished items forward at higher priority, and writes the daily note.
  5. Edit the daily note by hand when needed. Wilkins says Claude assembles the draft, and because the notes are plain text, tweaks stay easy.

Starter shape (not a drop-in of the author's private skills; shaped from the article):

Prompt
Help me build a Claude Code morning briefing for my Obsidian task vault.
Use the Obsidian CLI (not raw file edits) for every read and write.
Each morning: sync yesterday's daily-note checkboxes back to task metadata,
archive completed items, update habit streaks, compact daily notes older
than seven days, scan the next seven days, fetch weather, read context.md
and agent-notes.md, carry unfinished tasks forward with higher priority,
and write today's daily note with tasks, habits, a seven-day forward view,
and weather. Never delete notes outside the archive rules. Stop and list
exceptions if a link or folder is ambiguous.

What you need connected#

Claude Code with a morning schedule, a local Obsidian vault, the Obsidian CLI wired into an obsidian-cli skill, and the todo-vault (or equivalent) skill that defines note types. Wilkins keeps the knowledge layer in a separate vault and only automates the task layer in this post.

Good to know#

  • This is a power-user setup. Wilkins says the specific architecture is "just the setup that works for me," and that figuring out your own structure takes trial and error.
  • Prefer the Obsidian CLI path. The article argues raw file operations are slower, cost more tokens, and can leave the vault's internal state out of sync.
  • Capture still needs a human front door. Wilkins uses speech-to-text into an inbox note, then Claude Code ingests that dump into the right note types.
  • No hours-saved number was published. The result is the maintenance steps removed and one daily note to run from.
  • Article dated Apr 8, 2026. We re-checked the live page on Oct 14, 2026. We did not reproduce the skills on this box.

Same idea in Grok Bot#

Grok Bot can own a morning scheduled routine that reads and writes Markdown on a computer where your Obsidian vault lives, with the method saved as a skill. There is no first-party Obsidian plugin to claim here, so keep edits behind approval until you trust the archive rules. Calendar and weather can come from Google Calendar or a public forecast fetch if you connect them. Do not claim HubSpot-style CRM connectors for this job; it is a local vault brief.

Sources#

Sources

  1. jdhwilkins.com

Something wrong? Tell the bot