ObsidianOS: Work
An Obsidian vault with skills for work meetings: Gmail transcripts, participants, follow-up tasks and weekly recaps.
- 165 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The `/mail-transcripts` skill reads Gmail, writes notes and marks emails as read, so it needs modify access.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/obsidianos-workDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The `/mail-transcripts` skill reads Gmail, writes notes and marks emails as read, so it needs modify access.
This is third-party code. Review the repository files before installing.
What it does
An Obsidian vault template whose slash commands carry meeting notes through a pipeline. `/mail-transcripts` collects Gemini transcript emails from Gmail, `/organize-meetings` sorts drafts into folders, `/cache-notes` embeds transcripts, `/fill-participants` turns names into `[[@Person]]` links and `/followup-todos` extracts action items. `/meeting wrap pending` runs the whole chain and `/commit` records the result in one commit. Other skills build a weekly `/recap` from email, Slack, Jira and notes, audit links and orphans in `/vault-health`, and maintain people notes and one-on-one tracking. Work goes through the Obsidian CLI, the Google Workspace CLI `gws` and QMD search. The agent can be Cursor, Claude Code, OpenCode or OpenClaw.
Who it is for. Team leads and engineers who keep work notes in Obsidian and drown in meeting transcripts and follow-up emails.
Good fit when
- After a dozen meetings in a week, transcripts sit in Gmail and must be sorted into notes.
- Participant names in notes must be replaced with links to people notes.
- A weekly recap from email, Slack, Jira and vault notes is due.
- The vault has grown and broken links and orphan notes need to be found.
Not a fit when
- Meeting transcripts do not come from Gemini or Otter.
- Company policy forbids connecting Google mail and calendar to an agent.
- Notes are kept in another editor unrelated to Obsidian.
Example request
Process all pending meetings with /meeting wrap pending and show the proposed follow-ups before writing.Limitations
The meeting pipeline targets Gemini transcripts and a manual Otter format, and folder paths are hardcoded in `.scripts/gmail_ai_transcripts_to_meetings.py`, which you will have to edit. It needs Obsidian with Bases enabled, the Obsidian CLI, Node.js 24 and `gws`. The Gmail label must be named `🤖-ai-transcripts`, or the emails will not be found. The latest commit in the repository dates from June 2026, and activity is low.
How to disable. Delete the vault folder or the `.agents/skills` directory, revoke `gws` access to the Google account and remove the Gmail label.
FAQ
What do I fill in first?
The `USER.md` file: name, email, timezone and aliases. All skills take personal data only from there.
Is MCP required?
Only for QMD search in Cursor, loaded from `.cursor/mcp.json`. Google Workspace goes through `gws` in the terminal, not MCP.
What does /meeting wrap pending do?
It runs the chain: transcript emails, folder sorting, transcript embedding, participants, follow-ups and a shared commit. Follow-ups are proposed and the user confirms.
Which agents are supported?
Cursor, Cursor CLI, Claude Code, OpenCode and OpenClaw work in full. Other MCP clients get only QMD search without auto-loaded instructions.
What does `/mail-transcripts` change in the mailbox?
The script marks processed emails as read, which needs Gmail modify scope. Calendar and documents are read-only.
Discussion
No questions or reviews yet.
Related
SkillsAn Obsidian vault template for Claude Code: /daily, /weekly, /monthly and /project commands link three-year goals to today's tasks
An Obsidian vault template with hooks, commands and skills that gives Claude Code, Codex and Gemini CLI persistent memory across sessions
Compass is an Obsidian vault template that takes journal questions and habits from one configuration file for its dashboards.
A self-hosted Telegram AI assistant with Markdown memory: voice, photos, tasks and Google Workspace on your own server.
Obsidian skills
Obsidian Skills
Skills for agents working with Obsidian: Markdown with wikilinks, Bases, JSON Canvas, Obsidian CLI, Defuddle and Knap
A skill set that lets an agent run a personal Obsidian wiki: it compiles knowledge from documents and past sessions and answers with citations
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| ObsidianOS: Work (this card) | no | 165 | |
| Obsidian Mind | no | 5,502 | gives hooks and commands persistent memory between sessions; ObsidianOS: Work runs meetings from a transcript email to tasks |
| Claude Code Obsidian Starter | no | 225 | a starter vault for projects, tasks and clients; this one is a meeting pipeline with Gmail, Otter and weekly recaps |
README in short
The README lists over twenty skills, tiers of dependencies and an end-to-end meeting pipeline. Skills live in `.agents/skills`, and the other agent folders link to them.