// Use when asked to import, sync, or add Granola meeting notes into the Obsidian vault. Triggers on "meeting notes", "Granola", "import meetings", "add notes from this week", or any request to move meeting content into Obsidian.
Use when evaluating, designing, or pressure-testing the business model of an AI agent product. Triggers on "agent business model", "agent economics", "agent canvas", "evaluate agent product", "agent pricing", "agent unit economics", "agentic business", "AI agent company", "agent cost structure".
Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.
Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.
Use when a pipeline DOT file has passed structural validation but may still have flow inefficiencies, spec fidelity gaps, or information loss in prompts. Use after dotfile-audit or dotfile-from-spec when you want to deeply verify a pipeline captures everything from the original spec. Use when prompts might be missing critical domain rules, data models, or invariants.
| name | granola-to-obsidian |
| description | Use when asked to import, sync, or add Granola meeting notes into the Obsidian vault. Triggers on "meeting notes", "Granola", "import meetings", "add notes from this week", or any request to move meeting content into Obsidian. |
Import Granola meeting notes into the 2389 Obsidian vault with correct formatting.
NEVER guess the format. Before creating any meeting note, read 2-3 existing files in Meeting Notes/ to confirm current conventions. Formats evolve.
custom_end should be the day AFTER the last date (exclusive upper bound)mcp__granola__list_meetings
time_range: "custom"
custom_start: "YYYY-MM-DD"
custom_end: "YYYY-MM-DD" # day after last date
mcp__granola__get_meetings
meeting_ids: ["id1", "id2", ...] # max 10 per call
Glob: Meeting Notes/*.md
Read: 2-3 recent files to confirm frontmatter and body format
Search by meeting title in existing filenames:
Glob: Meeting Notes/*{partial-title}*
If a file with a matching title exists, ask the user before overwriting.
Filename: Date prefix with hyphen-separated title: YYYY-MM-DD-Title.md
Meeting Notes/2026-01-30-Camp Sessions.md (correct)Meeting Notes/Camp Sessions.md (WRONG โ older files use this, but new notes get the date prefix)Content structure:
---
Created by: Harper Reed
Created time: YYYY-MM-DDTHH:MM:SS
Event time: YYYY-MM-DD
Type: <see type list>
Attendees:
- Name One
- Name Two
---
# Meeting Title
Day, DD Mon YY ยท location-or-participant-emails
### Section Heading
- Bullet point content
- Nested detail
- Another point
### Another Section
- Content follows Granola's summary structure directly
| Field | Value | Source |
|---|---|---|
Created by | Harper Reed | Always (note creator) |
Created time | ISO 8601 timestamp | From Granola meeting datetime |
Event time | ISO 8601 date only | From Granola meeting date |
Type | See below | Classify from content |
Attendees | YAML list of names | From Granola participants |
Do NOT add: notion-id, base, Last edited by, Last edited time (those are legacy Notion migration artifacts on older files).
| Type | When to Use |
|---|---|
Investors | VC meetings, fundraising discussions |
Tactical | Internal team planning, standups |
Training | Research, experiments, learning sessions |
Camp | External events, camp sessions |
Brainstorm | Ideation, product exploration |
Strategy | Company direction, GTM, partnerships |
Product Demo | Product demonstrations, demos |
Meetup | Community events, group gatherings |
1:1 | One-on-one conversations |
If unsure, omit the Type field rather than guessing wrong.
Use: Day, DD Mon YY ยท context
Examples:
Wed, 28 Jan 26 ยท BetaworksThu, 29 Jan 26 ยท dylan@2389.ai, harper@2389.aiFri, 30 Jan 26The context after ยท is optional. Use location if known, participant emails if it's a small meeting, or omit.
###) headings- [ ] task checkboxes unless the source has themIf Granola returns private_notes, do NOT include them in the Obsidian file by default. Ask the user if they want private notes included.
| Mistake | Fix |
|---|---|
| Using the wrong year | Always check today's date for current year |
| Missing date prefix in filename | New notes use YYYY-MM-DD-Title.md format (older files without prefix are legacy) |
| Inventing frontmatter fields | Use only: Created by, Created time, Event time, Type, Attendees |
| Adding Notion legacy fields | notion-id and base are only on migrated files |
| Checkbox action items | Don't add - [ ] unless source has them |
| Guessing format without reading | Always read 2-3 existing notes first |
| Bold labels in body | Don't use **Date:** patterns, use the date line format |
| Overwriting existing notes | Always check for duplicates by title first |