ObsidianOS: Work

An Obsidian vault wired with AI agent skills — an Agentic Operating System for Thinkers.

Sneak Peek

Slash commands that run inside your vault, powered by any AI agent:

/meeting                  → Create notes from Google Calendar
/cache-notes              → Embed AI meeting transcripts
/fill-participants        → Resolve names to [[@Person]] wikilinks
/followup-todos           → Extract action items as plain markdown bullets (no Tasks checkboxes)
/note-status              → Verify notes are fully processed
/recap                    → Weekly summary from email, Slack, Jira & vault
/commit                   → Stage & commit with inferred intent
/sync-upstream-obsidianos → Pull updates from upstream ObsidianOS

Agent-agnostic — works with Cursor, Claude Code, OpenCode, or any MCP-compatible client. Clone it, fill in USER.md, and go.

Compatible agents

Skills

Each skill supports multiple sub-commands and arguments — see AGENTS.md for the full reference. Skill proxies: .cursor/skills, .claude/skills, .opencode/skills, and repo-root skills/ are symlinks to .agents/skills/ so Cursor, Claude Code, OpenCode, and OpenClaw share one canonical tree.

Prerequisites

• Cursor IDE or CLI (or any agent that supports MCP — see Compatible agents)
• Node.js v20+
• Obsidian (see Obsidian plugins below)
• Google Workspace CLI (gws) — optional; required for /meeting (Calendar), /cache-notes / /fill-participants (Docs/Drive), and /recap (Gmail/Calendar). Install per § 3 in Setup below.

Setup

1. Clone and install

git clone https://github.com/youruser/obsos_work.git
cd obsos_work
npm install

2. Fill in your identity

Edit USER.md with your name, email, timezone, and aliases. This is the single source of truth that all skills reference — no other file needs your personal info.

3. Google Workspace CLI (optional)

Required for /meeting (list today’s Calendar events), /cache-notes / /fill-participants (read Gemini Google Docs), and /recap (Gmail + Calendar). All of these workflows are read-only; use OAuth scopes limited to what you need (e.g. Drive/Docs/Calendar/Gmail readonly).

1. Install gws — pick one:
   • GitHub Releases (pre-built binary)
   • brew install googleworkspace-cli
   • npm install -g @googleworkspace/cli
2. Authenticate (browser flow):

gws auth login

Use a scope preset or --scopes that includes readonly access for the APIs you use. Credentials are stored under ~/.config/gws/ by default. Optional env vars: see .env.example and the upstream README.

3. Command examples for agents are in .agents/skills/_shared/google-workspace-cli.md.

[!NOTE] Google Workspace is not exposed via MCP in this vault — agents run gws in the terminal. Cursor still loads QMD from .cursor/mcp.json only.

4. QMD vault search (optional)

Required for /recap and vault-wide search. QMD indexes your markdown files for keyword and semantic search.

npx qmd collection add . --name my_vault
npx qmd embed

The npx qmd mcp server (configured in .cursor/mcp.json) will serve searches from this index. Re-run npx qmd embed after adding significant new content.

5. Vault structure

The vault ships with these directories already in place:

Meetings/          Meeting notes (create subfolders per team/project as needed)
Teams/People/      Person files: @Name.md (one per colleague)
Teams/             Team files: +TeamName.md
Templates/         Obsidian templates

A default Teams/People/@Me.md is included as the vault owner's person file. Add subfolders under Meetings/ to organise notes by team or project (e.g. Meetings/Eng/, Meetings/TBs/).

6. Open in Obsidian + Cursor

Open the vault folder in both Obsidian (for viewing/editing notes) and Cursor (for running agent skills). Cursor will auto-load MCP servers from .cursor/mcp.json (this repo ships QMD only) and the rules from .cursor/rules/. Install and log in to gws separately for Google Workspace features.

In Obsidian, hide non-vault folders from the file explorer: go to Settings → Files & Links → Excluded files and add node_modules.

Obsidian plugins

The vault works with vanilla Obsidian, but these community plugins power specific features. Install whichever you need from Settings → Community plugins → Browse.

Required

Recommended

Optional (cosmetic / workflow)

These are not required by any skill but improve the day-to-day experience:

Optional (agent skills: Obsidian CLI stack)

These line up with the bundled kepano/obsidian-skills agent skills (obsidian-cli, json-canvas, obsidian-bases, obsidian-markdown). None are extra Community plugins unless noted — turn on the features you use, and keep Obsidian running when an agent drives the vault via the [Obsidian CLI](htt