granola
Skill1 starsChanged 7 months agoMITView on GitHub
Fetch meeting notes from Granola and save them as structured Markdown files to your Obsidian vault, categorized by meeting type (interviews, work, discovery)
9 other projects use a version of this.
Adopted by
Most recently taken up by
- obra/muse-skillstheir own version, first seen Oct 13, 2026
- joelhooks/joelclawtheir own version, first seen Oct 8, 2026
- t0ddharris/compound-marketingtheir own version, first seen Oct 8, 2026
- jacobwell/muse-skillstheir own version, first seen Sep 25, 2026
- ArtemXTech/personal-os-skillstheir own version, first seen Sep 22, 2026
- glebis/claude-skillstheir own version, first seen Jul 1, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- ArtemXTech/personal-os-skills★ 545same name
- glebis/claude-skills★ 410same name
- ArtemXTech/claude-code-obsidian-starter★ 225same name
- joelhooks/joelclaw★ 65same name
- obra/muse-skills★ 20same name
- jacobwell/muse-skills★ 8same name
- t0ddharris/compound-marketing★ 1same name
- JAVICHILEON/claude---Skills★ 0same name
- KISHOR403/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Call list_meetings with appropriate time_range.
- Distinctive: line 128
All files saved. No additional ingest steps.
- Distinctive: line 133
Never fetch transcript unless user explicitly asks — summaries and notes are enough
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<objective>
Fetch meeting notes from Granola and save them as structured Markdown files in your Obsidian vault under Meetings/, categorized by type.
</objective><context>
User input: $ARGUMENTSVault base: $OBSIDIAN_VAULT environment variable (or ./meetings-output if not set)
Meetings base: {VAULT}/Meetings/
Subfolders:
Interviews/— job interviews, candidate interviews, SME interviewsWork/— team syncs, planning, internal meetingsDiscovery/— customer calls, user research, partner meetings
Flags:
all— fetch all recent meetings (default: last 30 days)interviews— only interview-type meetingswork— only internal work meetingsdiscovery— only customer/partner/external meetings<keyword>— fetch meetings matching a title keyword--days N— how many days back to look (default: 30)--no-ingest— save files only, skip wiki ingest step</context>
<process>Step 1: Parse arguments and determine filter
Extract from $ARGUMENTS:
- Filter: all | interviews | work | discovery | keyword (default: all)
- Days: from --days flag (default: 30)
- Ingest: true unless --no-ingest
Step 2: List meetings
Call list_meetings with appropriate time_range.
For keyword filter: fetch all, then filter by title containing the keyword.
Step 3: Categorize meetings
For each meeting, classify into one of:
- Interview — title contains: interview, rozmowa kwalifikacyjna, hiring, rekrutacja, SME interview, [company] + first name only (e.g. "n8n / Łukasz")
- Discovery — external participants from outside your company domain (
$COMPANY_DOMAINenv var, if set), or title contains: demo, customer, client, partner, intro, coffee, onboarding (external) - Work — everything else (internal meetings within your company domain)
Apply the user's filter to decide which categories to process.
Step 4: Fetch meeting details
For meetings passing the filter, call get_meetings (batch up to 10 at a time).
Skip meetings that:
- Have no notes and no summary (empty meetings)
- Are pure daily standups with no meaningful content
- Are already saved (check if file exists at output path)
Step 5: Save to vault
For each meeting, create a markdown file:
File path: {MEETINGS_BASE}/{Category}/YYYY-MM-DD {Sanitized Title}.md
File format:
---
title: "{Meeting Title}"
date: YYYY-MM-DD
type: meeting
category: interview | work | discovery
participants: [Name1, Name2]
source: granola
granola_id: {meeting_id}
---
# {Meeting Title}
**Date:** YYYY-MM-DD
**Participants:** {participant list}
---
## Summary
{AI-generated summary from Granola, or "No summary available"}
## Notes
{Private notes if any, or "No notes recorded"}
## Action Items
{Extract action items from summary/notes, or "None identified"}Sanitize title for filename: remove special chars, truncate to 80 chars.
Step 6: Report saved files
Granola sync complete!
Saved: N meetings
Interviews: N files → Meetings/Interviews/
Work: N files → Meetings/Work/
Discovery: N files → Meetings/Discovery/
Skipped: N (empty or already saved)Step 7: Done
All files saved. No additional ingest steps.
</process><principles>
1. Never fetch transcript unless user explicitly asks — summaries and notes are enough
2. Skip empty meetings (no summary, no notes)
3. Files already saved are not overwritten unless content has changed
</principles>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.

