obsidian-operator

Operator

An AI-native personal operating system built on Obsidian + Claude Code.

Operator is an opinionated system of 19 Claude Code skills that turn an Obsidian vault into a structured execution engine — daily briefings, arXiv paper scanning, weekly reviews, strategic planning, meeting processing, deadline tracking, deep research, and a content engine for publishing, all orchestrated by AI agents.

Quick Start

1. Install the plugin

Claude Code (recommended — includes auto-updates):

# Add the marketplace and install (auto-updates enabled)
/plugin marketplace add https://github.com/yuhanwang14/obsidian-operator
/plugin install obsidian-operator

Codex CLI:

# 1. Add the marketplace (from your shell)
codex plugin marketplace add yuhanwang14/obsidian-operator

# 2. Launch Codex and enable the plugin via the TUI
codex
> /plugin           # opens the plugin manager — toggle obsidian-operator on

Upgrading from v1.9.x manual install? Remove the stale symlink first: rm ~/.agents/skills/obsidian-operator. See docs/README.codex.md for full upgrade steps.

2. Initialize the vault

Open your (empty or existing) Obsidian vault directory and run:

cd /path/to/your/vault
claude       # or: codex

/vault-init

/vault-init creates the six core folders, installs CLAUDE.md, walks you through the Customization table (vault owner, calendar names, meeting paths), and optionally sets up ~/.secrets + the transcription script for /meeting. It's idempotent — safe to rerun.

3. Start using

# Your first day:
/project-init MyProject
/daily-init 6

git clone https://github.com/yuhanwang14/obsidian-operator.git
cp -r obsidian-operator/plugins/obsidian-operator/skills/vault-init/assets/vault-template/* /path/to/your/vault/
cp    obsidian-operator/plugins/obsidian-operator/skills/vault-init/assets/CLAUDE.md         /path/to/your/vault/
# then edit the Customization table in CLAUDE.md by hand

Prerequisites

Configuration

/vault-init handles the common settings interactively: the Customization table in CLAUDE.md (vault owner, calendar names, meeting paths) and, optionally, ~/.secrets + the /meeting transcription script. Rerun it any time to update values.

Two integrations live outside Claude Code and need a one-time setup of their own:

Gmail MCP (optional — for /daily-init)

Claude Code: Connect your Google account under Claude Code settings → MCP integrations and grant Gmail read access.

Codex CLI: Configure a Gmail MCP server in ~/.codex/config.toml. Three compatible options (Google Workspace MCP, Composio Gmail, Nylas) — see docs/README.codex.md for setup snippets and tool-name differences.

If not configured (either platform), /daily-init silently skips the email section and /content-extract skips the newsletter step.

Apple Calendar & Reminders (macOS only — for /deadline-plan, /quarterly-plan, /add-events)

No OS setup needed beyond macOS. Configure the calendar and list names via /vault-init, or edit them directly in the Customization table of CLAUDE.md.

Vault Structure

00_Strategy/            — annual vision, quarterly plans, monthly pulses
01_Execution/           — daily notes, weekly todos, blockers, reviews
02_Projects/            — per-project folders with meeting plans, transcripts, deadlines
03_Thinking/            — reflections, ideas, mental models
04_Knowledge/           — research, meeting knowledge, deep research, digests
05_Content/             — content backlog, drafts, published, archived, voice guide

See CLAUDE.md for full conventions, frontmatter spec, checkbox states, and AI agent instructions.

Skills Reference

Setup