granola · glebis — Claude Code skill: meeting exports and setup
Use this skill to retrieve Granola notes and transcripts, then save meeting notes to Obsidian. It suits workflows that need searchable records or follow-up analysis.
MIT 234 installs ★ 414 updated 2026-10-23
npx skills add glebis/claude-skills --skill granola -a claude-codeWhat granola does
The skill queries Granola’s Personal API to list notes and retrieve meeting details. You can filter the list by date, request JSON, or ask show to include a transcript. Run its commands through python3 ~/.claude/skills/granola/scripts/granola.py.
The export command writes a note to Obsidian using a format shared with Fathom exports. Choose a vault or provide a custom output path. Access requires a Granola Business or Enterprise plan and an API key stored as GRANOLA_API_KEY in ~/Brains/brain/.env.granola. Meetings appear through the API only after Granola has generated a summary, so in-progress calls cannot be retrieved. Individual speaker names may also be missing from transcript utterances.
What it helps with
- list Granola notes created after a chosen date
- inspect a meeting summary and its attendees by note ID
- retrieve the transcript for a completed meeting
- export a Granola note to Obsidian in Fathom format
Example prompts for the agent
- List Granola notes after
2026-05-01and return the results as JSON. - Show the transcript for meeting
not_5FkswTp4Omkpm5. - Export note
not_5FkswTp4Omkpm5to my Obsidian vault.
How to install granola
1Skills CLI (Vercel)
npx skills add glebis/claude-skills --skill granola -a claude-code2Manually: put the files in place
~/.claude/skills/granola/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/granola/
1Skills CLI (Vercel)
npx skills add glebis/claude-skills --skill granola -a codex2Manually: put the files in place
.agents/skills/granola/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add glebis/claude-skills --skill granola -a cursor2Manually: put the files in place
.cursor/skills/granola/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install glebis/claude-skills granola2Manually: put the files in place
.github/skills/granola/SKILL.md1Skills CLI (Vercel)
npx skills add glebis/claude-skills --skill granola -a gemini-cli2Platform CLI
gemini skills install https://github.com/glebis/claude-skills --path granolaManually: put the files in place
.devin/skills/granola/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add glebis/claude-skills --skill granola -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about granola
How do I install granola in Claude Code?
Run npx skills add glebis/claude-skills --skill granola -a claude-code. The skill file is at ~/.claude/skills/granola/SKILL.md.
What does granola do?
It retrieves Granola meeting notes and transcripts, displays meeting details, and exports notes to Obsidian.
What does granola need to access meetings?
You need a Granola Business or Enterprise plan and a Personal API key saved as GRANOLA_API_KEY in ~/Brains/brain/.env.granola. The API returns notes once Granola has generated their summaries.
Source text
SKILL.md · MIT
---
name: granola
description: This skill should be used when importing, listing, or exporting Granola meeting recordings and transcripts. Queries Granola's Personal API to list meetings, extract transcripts, and export to Obsidian notes in Fathom-compatible format.
---
# Granola Meeting Importer
Query Granola via Personal API to list notes, view transcripts, and export to Obsidian vault in the same format as the Fathom skill.
## Prerequisites
- Granola Business or Enterprise plan (Personal API required)
- API key in sops-encrypted `~/Brains/brain/.env.granola` as `GRANOLA_API_KEY=grn_...`
- No additional dependencies (uses stdlib only)
## Usage
```bash
python3 ~/.claude/skills/granola/scripts/granola.py <command> [options]
```
### Commands
| Command | Description |
|---------|-------------|
| `list` | List notes from Personal API |
| `show <note_id>` | Show note details (summary, attendees, optionally transcript) |
| `export <note_id>` | Export note to Obsidian markdown (Fathom-compatible format) |
### Options
| Option | Applies to | Description |
|--------|-----------|-------------|
| `--format text\|json` | list, show | Output format (default: text) |
| `--after <ISO date>` | list | Filter notes created after date |
| `--all` | list | Paginate through all results |
| `--transcript` | show | Include transcript in output |
| `--vault <path>` | export | Obsidian vault path (default: ~/Brains/brain) |
| `--output <path>` | export | Custom output file path |
## Examples
### List recent meetings
```bash
python3 ~/.claude/skills/granola/scripts/granola.py list
python3 ~/.claude/skills/granola/scripts/granola.py list --format json
python3 ~/.claude/skills/granola/scripts/granola.py list --after 2026-05-01
```
### Show note with transcript
```bash
python3 ~/.claude/skills/granola/scripts/granola.py show not_5FkswTp4Omkpm5
python3 ~/.claude/skills/granola/scripts/granola.py show not_5FkswTp4Omkpm5 --transcript --format json
```
### Export to Obsidian
```bash
python3 ~/.claude/skills/granola/scripts/granola.py export not_5FkswTp4Omkpm5
python3 ~/.claude/skills/granola/scripts/granola.py export not_5FkswTp4Omkpm5 --vault ~/Brains/brain
```
## Output Format
Exported notes match Fathom skill format for consistency:
```markdown
---
granola_id: not_xxxx
title: "Meeting Title"
date: YYYY-MM-DD
participants: ['Name 1', 'Name 2']
duration: HH:MM
source: granola
---
# Meeting Title
## Summary
{AI-generated summary}
## Transcript
**Speaker Name**: What they said...
```
Files saved as: `Sessions/YYYYMMDD-meeting-title-slug.md`
## API Details
- **Base URL**: `https://public-api.granola.ai/v1`
- **Auth**: Bearer token (Personal API key, never expires)
- **Rate limits**: 25 req burst / 5 req/sec sustained
- **Important**: API only returns notes with generated summaries — in-progress meetings won't appear
## Known Limitations
- **No live/in-progress access** — notes appear only after Granola generates the AI summary
- **No per-utterance speaker names** — Granola provides `source` (microphone vs speaker) and optional `diarization_label`. Export assigns meeting owner to microphone utterances
- **Note IDs required** — use `list` first to get `not_xxxx` IDs, then `show`/`export`
## Integration
- **transcript-analyzer**: After export, run transcript-analyzer on the output file for deeper analysis
- **Fathom skill**: Granola exports use the same frontmatter and transcript format as Fathom exports, so downstream tools work with both
© glebis · MIT · glebis/claude-skills
Similar skills
All skills for Notes, tasks and projects →granola by other authors comes first.