obsidianos_work
AGENTS.md166 starsChanged 5 months agoMITView on GitHub
This is an Obsidian vault with AI agent skills. See USER.md for the vault owner's identity. Agents working in this repo should be aware of the following structure and conventions. Custom skills live in .agents/skills/. Each has a SKILL.md with usage, workflow, and conventions.
- Reads credentials
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository29 other files it gives its agents.
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- vault-healthSkill
- workspace-modeSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 117
If you forked or cloned this repo into a private vault, you can pull structural updates (skills, rules, shared conventions) without …
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agents
This is an Obsidian vault with AI agent skills. See USER.md for the vault owner's identity. Agents working in this repo should be aware of the following structure and conventions.
Skills
Custom skills live in .agents/skills/. Each has a SKILL.md with usage, workflow, and conventions.
| Skill | What it does | Arguments |
| meeting | Create a meeting note | |
├ /meeting | Pick from today's Google Calendar events | |
├ /meeting {title} | Manual creation with today's date | folder={subfolder} |
├ /meeting wrap <path> | Wrap up: mail-transcripts → cache → participants → todos → commit | |
└ /meeting wrap pending [dates] | Find & wrap all pending meetings | today, yesterday, last week, 2026-01-01..2026-02-03 |
| cache-notes | Fetch & embed AI transcripts as Obsidian callouts | |
├ /cache-notes <path> | Cache a specific meeting file (prompts for URLs if empty) | |
├ /cache-notes all | Batch-cache all uncached meetings | |
└ /cache-notes refresh <path> | Re-fetch and overwrite existing cache | |
| fill-participants | Resolve and fill Participants: frontmatter | |
├ /fill-participants <path> | Fill for a specific meeting note | |
└ /fill-participants all | Scan and fill all meetings missing participants | |
| followup-todos | Extract action items as plain markdown bullets | |
├ /followup-todos <path> | Extract from a specific meeting note | |
└ /followup-todos | /note-status pending --step=todos | |
| recap | Produce a recap from emails, Slack, Jira, and vault notes | |
├ /recap | Recap current week (Monday through today) | |
└ /recap [dates] | Recap a specific date range | today, yesterday, last week, 2026-01-01..2026-02-03 |
| sync-upstream-obsidianos | Pull structural updates from upstream ObsidianOS | |
├ /sync-upstream-obsidianos | Preview and merge upstream updates | |
└ /sync-upstream-obsidianos preview | Show what's new without merging | |
| note-status | Verify meeting notes are fully processed | |
├ /note-status <path> | Check a specific note | |
├ /note-status [dates] | Check notes in a date range | today, yesterday, last week, 2026-01-01..2026-02-03 |
├ /note-status all | Check every meeting note | |
└ /note-status pending [dates] | Filter to pending, prompt selection | --step=notes|cache|participants|todos |
| commit | Stage and commit with flexible intent parsing | |
├ /commit | Staged files, or infer related changes | |
├ /commit <file or folder> | Scope commit to a specific path | |
├ /commit <description> | Infer scope from free-text intent | |
├ /commit amend [scope/description] | Amend last commit (with optional scope or new message) | |
| └ (sequence mode) | Deferred — sub-skills skip, caller commits once at the end | |
| defuddle | Extract clean markdown from web pages with Defuddle CLI (prefer over raw fetch for articles & docs) | |
| json-canvas | Create and edit Obsidian JSON Canvas (.canvas) files | |
| obsidian-bases | Create and edit Obsidian Bases (.base) — views, filters, formulas | |
| obsidian-cli | Drive a running Obsidian app via the obsidian CLI (read/write/search, dev helpers) | |
| obsidian-markdown | Obsidian Flavored Markdown — wikilinks, embeds, callouts, properties | |
| mail-transcripts | Drain Gmail AI-transcript notifications into meeting Notes: (gws) | |
| organize-meetings | Triage Meetings/_inbox/ into the right subfolder via qmd + memory | <path>, --auto |
| otter-fetch | Otter.ai transcript sub-skill (invoked by cache-notes / fill-participants) | |
| people-stubs | Batch-create Teams/People/@Name.md stubs from unresolved [[@*]] links | --auto |
| onboard-person | Create/enrich a @Name.md from external sources (ATS / profile) | <Name>, --candidate |
| last-1on1 | Flag overdue 1:1s by recency (Meetings.base OneOnOnes view) | <weeks>, @Name |
| vault-health | Audit unresolved links, orphans, deadends, sync conflicts | unresolved, orphans, deadends, sync, --fix-people |
| migrate-tags | Migrate body #hashtags to frontmatter tags: lists | <path>, --dry-run, --strip-body |
| workspace-mode | Switch named Obsidian Workspace layouts | <name>, save <name> |
| sprint-retro | Synthesize a Sprint Retro draft from vault sources | <N>, <dates> |
Skill proxies (symlinks to .agents/skills/)
The canonical skill tree is .agents/skills/. These paths are symlinks to the same directory so each agent discovers the same skills:
| Path | Used by |
.cursor/skills | Cursor |
.claude/skills | Claude Code |
.opencode/skills | OpenCode |
skills/ | OpenClaw (workspace skills) |
OpenCode also discovers .agents/skills/ directly; the .opencode/skills link matches the Cursor / Claude layout.
Rules
Shared rules live in .agents/rules/ and are the single source of truth. Agent-specific wrappers point to them.
| Rule | Purpose |
| qmd-search | Prefer QMD over grep for vault search (always apply) |
| skill-conventions | Skill structure, shared conventions, project context |
| skill-registry | Keep skill tables in sync when skills change |
Agent wrappers
| Agent | Instruction files | How rules are loaded |
| Cursor | .cursor/rules/*.mdc | Auto-injected by glob; each .mdc points to .agents/rules/ |
| Claude Code | CLAUDE.md, .agents/skills/CLAUDE.md | Read on startup; point to .agents/rules/ |
| OpenCode / Crush | OpenCode.md | Read on startup; points to .agents/rules/ |
| OpenClaw | AGENTS.md (and your gateway config) | Rules live in .agents/rules/; skills via repo skills/ → .agents/skills/ |
Vault Layout
Meetings/ Meeting notes by subfolder (Engineering/, One-on-ones/, Interviews/, etc.)
Templates/ Obsidian templates
Teams/People/ Person files: @Name.md
Teams/ Team files: +TeamName.md
ToDo's.md Aggregated Tasks plugin view
Tracker.md Project trackerConventions
- User: See USER.md for identity, timezone, aliases, and agent behavior rules.
- Frontmatter: YAML between
---fences.modified:is managed by Obsidian — never set manually. - Participants:
[[@Name]]wikilinks (people) or[[+Team]](teams). - AI Transcripts: Cached under
## 🤖 AI Noteswith provider subheadings and collapsible callouts ([!gemini_notes]-,[!gemini_todos]-,[!gemini_transcript]-). - Tasks priorities: 🔺 highest, ⏫ high, 🔼 medium, 🔽 low.
MCP & external tools
- QMD — Configured in .cursor/mcp.json for vault search (MCP server
npx qmd mcp). - Google Workspace — Use the
gwsCLI (Google Workspace CLI) for Docs, Drive, Calendar, and Gmail in read-only workflows. See README.md § Google Workspace CLI and .agents/skills/_shared/google-workspace-cli.md.
Syncing from Upstream
If you forked or cloned this repo into a private vault, you can pull structural updates (skills, rules, shared conventions) without overwriting your personal data.
./.scripts/sync-upstream.sh # fetch + merge
./.scripts/sync-upstream.sh --preview # see what's new without mergingFirst-time setup:
git remote add upstream <url-to-this-repo>
./.scripts/sync-upstream.sh # auto-configures merge driver on first runProtected paths (always keep local version during merge): USER.md, Tracker.md, .env, .cursor/mcp.json, Meetings/, Teams/, Templates/, Recaps/. Edit .gitattributes to add or remove paths.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

