vault-os / Granola
AGENTS.md2 starsChanged 6 months agoMITView on GitHub
This folder is owned by the obsidian-granola-sync plugin. Files here are written and updated by the plugin from the Granola API. Treat them as the raw layer of the LLM Wiki pattern — immutable from the agent's perspective. Notes (type: note): Body sections: Transcripts (type: transcript) live in a sibling folder per plugin config. The ingest-meeting skill reads these files and produces:
In this repository20 other files it gives its agents.
- 1-Projects/AGENTS.mdAGENTS.md
- 2-Areas/AGENTS.mdAGENTS.md
- 3-Resources/AGENTS.mdAGENTS.md
- 4-Archive/AGENTS.mdAGENTS.md
- _admin/AGENTS.mdAGENTS.md
- _agent/AGENTS.mdAGENTS.md
- Books/AGENTS.mdAGENTS.md
- Content/AGENTS.mdAGENTS.md
- Dashboard/AGENTS.mdAGENTS.md
- Goals/AGENTS.mdAGENTS.md
- Inbox/AGENTS.mdAGENTS.md
- Journal/AGENTS.mdAGENTS.md
- People/AGENTS.mdAGENTS.md
- Recipes/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-moduleSkill
- close-daySkill
- daily-recapSkill
- ingest-meetingSkill
- todaySkill
The file
Files
Granola — Agent Rules
This folder is owned by the obsidian-granola-sync plugin. Files here are written and updated by the plugin from the Granola API. Treat them as the raw layer of the LLM Wiki pattern — immutable from the agent's perspective.
Rules
- Never modify files in this folder. The plugin will overwrite them on the next sync. If you need to add commentary, do it in
_agent/wiki/meetings/<slug>.md. - Never delete files in this folder. The plugin tracks state via
granola_id; deleting confuses it. - Read freely. This is your source of truth for meeting notes, transcripts, and attendees.
File schema (from the plugin)
Notes (type: note):
granola_id: <stable id, primary key for dedup>
title: <meeting title>
type: note
created: <ISO timestamp>
updated: <ISO timestamp>
attendees: [Name1, Name2]
transcript: "[[Transcripts/...md]]" # optional
folders: [granola folder paths] # optionalBody sections:
## Private Notes— your typed notes during the meeting## Enhanced Notes— Granola's processed output (decisions, key points, action items)- Optional inline transcript
Transcripts (type: transcript) live in a sibling folder per plugin config.
Where things go after ingestion
The ingest-meeting skill reads these files and produces:
- Wiki summary →
_agent/wiki/meetings/<YYYY-MM-DD>-<slug>.md - Attendee CRM updates →
People/<Name>.md - Topic / project page updates →
_agent/wiki/<topic>/or1-Projects/<project>/ - Action items → Obsidian Tasks (
- [ ] … 📅 date) appended to relevant project notes or today's daily note - Index update →
_agent/wiki/index.md - Log entry →
_agent/log.mdwith thegranola_idso re-runs skip already-ingested files
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.

