granola-setup
Skill509 starsChanged 3 months agoMITView on GitHub
Connect Granola via its official API for automatic meeting sync and transcripts. Use when the user says 'connect Granola', 'my meetings aren't syncing', 'set up meeting notes'. Not for Zoom recordings; use `zoom-setup`. Not for processing meetings already synced; use `process-meetings`.
- Reads credentials
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .claude/plugins/compound-engineering/CLAUDE.mdCLAUDE.md
- .cursor/rules/search-routing.mdcCursor rule
- anthropic-algorithmic-artSkill
- anthropic-brand-guidelinesSkill
- anthropic-doc-coauthoringSkill
- anthropic-docxSkill
- anthropic-frontend-designSkill
- anthropic-internal-commsSkill
- anthropic-mcp-builderSkill
- anthropic-pptxSkill
- anthropic-slack-gif-creatorSkill
- anthropic-theme-factorySkill
- anthropic-webapp-testingSkill
- anthropic-web-artifacts-builderSkill
- anthropic-xlsxSkill
- atlassian-setupSkill
- backup-nowSkill
- backup-restoreSkill
- backup-setupSkill
- calendar-setupSkill
- commitmentsSkill
- create-mcpSkill
- daily-planSkill
- daily-reviewSkill
- decision-logSkill
- delegate-checkSkill
- dex-backlogSkill
- dex-doctorSkill
- dex-improveSkill
- dex-obsidian-setupSkill
- dex-rollbackSkill
- dex-updateSkill
- dex-whats-newSkill
- diff-profileSkill
- enable-semantic-searchSkill
- getting-startedSkill
- goal-backlogSkill
- google-workspace-setupSkill
- identity-snapshotSkill
- industry-truthsSkill
- initiative-kickoffSkill
- integrate-mcpSkill
- journalSkill
- manage-capabilitiesSkill
- meeting-closeoutSkill
- meeting-prepSkill
- ms-teams-setupSkill
- pipedrive-setupSkill
- pipeline-syncSkill
- process-meetingsSkill
- product-briefSkill
- project-healthSkill
- prompt-improverSkill
- relationship-radarSkill
- reviewSkill
- save-insightSkill
- scrapeSkill
- skill-scoreSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 10 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 75
Read System/integrations/config.yaml for a granola section.
- Very specific: line 76
Check whether GRANOLA_API_KEY is already configured:
- Very specific: line 78
If absent, load the vault root .env file (at VAULT_ROOT) and parse a GRANOLA_API_KEY=...
- Distinctive: line 79
If a key is found, run the verification request from Step 5 silently.
- Distinctive: line 80
If it succeeds, tell the user they're already connected and skip to Step 7 (Reconfiguration / what's enabled).
- Distinctive: line 81
If it returns 401, the key is stale — continue to Step 2 to replace it.
- Distinctive: line 82
If no key is found, continue to Step 2.
- Distinctive: line 128
Wait for the user to paste the key.
- Very specific: line 130
Do a light sanity check: it should look like grn_....
- Distinctive: line 131
Never: ask the user to put the key in a file themselves — they only paste it into the chat.
- Very specific: line 138
Write or update the line GRANOLA_API_KEY=<pasted key> in that file.
- Very specific: line 139
If a GRANOLA_API_KEY= line already exists, replace it.
- Distinctive: line 174
On HTTP 429 (rate limited): wait a short moment and retry the verification request once.
- Very specific: line 180
Write to System/integrations/config.yaml — update (or add) the granola section.
- Very specific: line 195
Never write the API key value itself into config.yaml or any committed file — only the env var name.
- Very specific: line 227
Official API is the only data source: Do not read local cache files or use spoofed client headers or unofficial crypto helpers.
- Distinctive: line 240
Rate limits: not documented. Be gentle — sequential detail fetches, and retry once on HTTP 429 with a short backoff.
- Very specific: line 273
If the user runs /granola-setup when already configured:
- Distinctive: line 275
Verify the current key with the Step 5 test request.
- Distinctive: line 284
If the user wants to disconnect:
- Very specific: line 291
Remove (or comment out) the GRANOLA_API_KEY=...
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
<!-- Generated from `.claude/skills/granola-setup/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->Granola Setup
Connect your Granola account to Dex so your meetings sync automatically. Dex uses Granola's official API to read your notes, summaries, attendees, and transcripts — then files them into 00-Inbox/Meetings/ ready for /process-meetings.
This integration needs a Granola Business (or Enterprise) plan, because API keys can only be created on those plans. Granola Basic / free accounts can't create an API key, so this setup won't work on them.
What This Enables
Once connected, Dex can:
Read (via the official Granola API):
- List your Granola notes (title, owner, created/updated dates)
- Fetch each note's summary, attendees, folder membership, and web link
- Fetch full speaker-labelled transcripts per note
Skill Enhancements:
- Process Meetings (
/process-meetings) uses Granola as the primary meeting source — notes sync into00-Inbox/Meetings/, then get turned into structured meeting notes (decisions, actions, key points) - Meeting Prep (
/meeting-prep) surfaces your last Granola note and summary with each attendee - Week Review (
/week-review) includes meeting counts and topics from Granola
New Capabilities:
- Automatic Meeting Sync: new Granola notes are pulled into
00-Inbox/Meetings/ - Transcript Access: full transcripts are available when processing a meeting
Privacy
Dex reads your Granola data through Granola's official API using a key you create. The API key is stored locally in a .env file at your vault root — it is gitignored and never committed. Only YOUR Granola account is accessible (the key is scoped to your login). Nothing is sent anywhere except Granola's own API.
When to Run
- User types
/granola-setup - User asks about connecting Granola
- User wants automatic meeting sync or transcripts
- During
/integrate-mcpif Granola is mentioned - During onboarding if the user mentions Granola
Setup Flow
Throughout this flow, Dex performs every file action for the user. Never ask the user to open, create, or hand-edit
.envor any other file. They only ever paste their key into the chat — Dex does the rest.
Step 1: Check if Already Connected
- Read
System/integrations/config.yamlfor agranolasection. - Check whether
GRANOLA_API_KEYis already configured:- First check
process.env.GRANOLA_API_KEY. - If absent, load the vault root
.envfile (atVAULT_ROOT) and parse aGRANOLA_API_KEY=...line from it.
- First check
- If a key is found, run the verification request from Step 5 silently.
- If it succeeds, tell the user they're already connected and skip to Step 7 (Reconfiguration / what's enabled).
- If it returns 401, the key is stale — continue to Step 2 to replace it.
- If no key is found, continue to Step 2.
Step 2: Explain the New API-Based Sync
Set expectations conversationally:
Granola sync now uses Granola's official API.
That means Dex reads your meetings the supported way — your notes, summaries,
attendees, and transcripts — straight from Granola.
One thing to know up front: creating an API key requires a **Granola Business
(or Enterprise) plan**. The Basic / free plan can't create API keys, so if
you're on Basic this won't work yet.
Are you on a Granola Business or Enterprise plan? [Yes / Not sure / I'm on Basic]- If "I'm on Basic": let them know kindly that they'd need to upgrade to a Granola Business plan to create an API key, and that they can run
/granola-setupagain once they do. Stop here. - If "Not sure": reassure them — the next step will tell them quickly (if there's no API option in Settings, they're not on a plan that supports it). Continue.
- If "Yes": continue.
Step 3: Walk Them Through Creating an API Key
Guide them, step by step, in plain language:
Let's create your Granola API key:
1. Open **Granola** and go to **Settings**.
2. Find the **API** section (the Granola API settings page).
3. Click **Create API key** (or "New API key").
4. Copy the key — it starts with `grn_`.
If there's no API section in Settings, your plan doesn't support API keys yet
(that's the Business-plan requirement). Otherwise, grab that `grn_...` key.Step 4: Ask Them to Paste the Key
Paste your Granola API key here and I'll save it for you securely.
(It starts with grn_ — I'll store it locally and never commit it.)Wait for the user to paste the key.
- Do a light sanity check: it should look like
grn_.... If it clearly doesn't (e.g. they pasted something else), ask them to re-copy it from Granola's API settings. - Never ask the user to put the key in a file themselves — they only paste it into the chat.
Step 5: Store and Verify the Key
Store it (Dex does this — not the user):
- Locate the vault root
.envfile (VAULT_ROOT/.env). Create it if it doesn't exist. - Write or update the line
GRANOLA_API_KEY=<pasted key>in that file.- If a
GRANOLA_API_KEY=line already exists, replace it; otherwise append it.
- If a
- Make the file owner-only:
chmod 600 "$VAULT_ROOT/.env". Run this every time — it also tightens a pre-existing.envthat was left readable by other users of the machine. - Confirm
.envis gitignored (it is by convention — never commit it).
Verify it with a real request:
Make a single test call against the official API:
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $GRANOLA_API_KEY" \
"https://public-api.granola.ai/v1/notes?page_size=1"(Equivalently: GET https://public-api.granola.ai/v1/notes?page_size=1 with header Authorization: Bearer <key>.)
- On success (HTTP 200):
Continue to Step 6.Connected — I can see your Granola notes. - On 401 Unauthorized:
Offer to retry (back to Step 4). Retry up to 2 times, then offer to come back later.That key was rejected by Granola. Two common reasons: - the key was copied incompletely or has been revoked/expired, or - the account isn't on a Granola Business plan (only Business/Enterprise can create working API keys). Want to paste it again, or create a fresh key in Granola → Settings → API? - On HTTP 429 (rate limited): wait a short moment and retry the verification request once. The API has no documented limits, so stay gentle (one request at a time, single retry).
- On other errors (network/5xx): report briefly and offer to retry.
Step 6: Save Configuration
Write to System/integrations/config.yaml — update (or add) the granola section. Preserve all other integration configs.
granola:
enabled: true
configured_at: YYYY-MM-DD
auth_type: api_key
api_base_url: https://public-api.granola.ai
key_env_var: GRANOLA_API_KEY # value lives in VAULT_ROOT/.env, never here
account: user@example.com # from the owner.email in the test response
features:
meeting_sync: true
transcripts: trueNever write the API key value itself into config.yaml or any committed file — only the env var name. The key lives solely in the gitignored .env.
Step 7: Confirm with Capability Cascade
Granola is connected!
Here's what just got enabled:
- **Automatic meeting sync** — your Granola notes flow into 00-Inbox/Meetings/,
ready to be turned into structured notes.
- **Transcripts** — full speaker-labelled transcripts are available per meeting.
- **Meeting Prep** (/meeting-prep) — surfaces your last Granola note and summary
with each attendee.
- **Week Review** (/week-review) — includes meeting counts and topics from Granola.
Next step: run **/process-meetings** to pull in and organise your recent meetings.
You can re-run /granola-setup anytime to rotate your key or disconnect.Shared Conventions (data source rules)
These rules apply wherever Dex reads Granola data. The skill agent must follow them exactly so every Granola-aware workflow behaves consistently.
- API key env var:
GRANOLA_API_KEY. Readprocess.env.GRANOLA_API_KEYfirst; if absent, loadVAULT_ROOT/.envand parseGRANOLA_API_KEY=...from it. - No key configured → no error. Log this friendly one-liner and exit cleanly (exit 0 / return empty):
Granola not connected — run /granola-setup to add your Granola API key (requires a Granola Business plan). - Official API is the only data source. Do not read local cache files or use spoofed client headers or unofficial crypto helpers. Use only the documented endpoints below with the
Authorization: Bearerheader.
API reference (for Granola-aware skills)
- Base URL:
https://public-api.granola.ai - Auth header:
Authorization: Bearer <GRANOLA_API_KEY> - List:
GET /v1/notes- Query params:
created_after,created_before,updated_after(ISO date/datetime),folder_id,cursor(string),page_size(int 1..30, default 10). - Response:
{ "notes": [ { "id", "object", "title": string|null, "owner": {name,email}, "created_at", "updated_at" } ], "hasMore": boolean, "cursor": string|null }. - List items contain no summary, attendees, or transcript — fetch detail per note.
- Paginate by passing the returned
cursoruntilhasMoreisfalse.
- Query params:
- Detail:
GET /v1/notes/{note_id}?include=transcript- Response includes
web_url,calendar_event,attendees,folder_membership,summary_text,summary_markdown, andtranscript(array of{speaker, text, start_time, end_time}ornull).
- Response includes
- Rate limits: not documented. Be gentle — sequential detail fetches, and retry once on HTTP 429 with a short backoff.
Troubleshooting
401 Unauthorized
The key was rejected. Either:
- the key is wrong, incomplete, revoked, or expired — create a fresh one in Granola → Settings → API and paste it again, or
- the account isn't on a Granola Business / Enterprise plan — only those plans can create working API keys. Basic / free can't.
Re-run /granola-setup to paste a new key.
No Notes Returned (empty list, 200 OK)
The key works but Dex sees no notes. Check:
- you're querying the right Granola workspace/account (the key is scoped to the account that created it), and
- that account actually has recorded notes, and
- the plan still supports API access.
"Granola not connected" keeps appearing
That means no GRANOLA_API_KEY is configured. Run /granola-setup to add one. (Dex never errors out when the key is missing — it just nudges you to set it up.)
Rate Limiting (429)
Granola doesn't publish rate limits, so Dex fetches gently. If you hit a 429, Dex waits briefly and retries once. Persistent 429s are rare — wait a minute and try again.
Reconfiguration
If the user runs /granola-setup when already configured:
- Verify the current key with the Step 5 test request.
- Show the current config from
System/integrations/config.yaml. - Offer options:
- Rotate the key — paste a new
grn_...key; Dex updatesVAULT_ROOT/.env. - Re-test the connection.
- Disconnect Granola.
- Rotate the key — paste a new
Disconnect Flow
If the user wants to disconnect:
- Update
System/integrations/config.yaml:granola: enabled: false - Remove (or comment out) the
GRANOLA_API_KEY=...line inVAULT_ROOT/.envfor them. - Confirm: "Granola is disconnected. Meeting sync and transcripts will pause. Run
/granola-setupanytime to reconnect."
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.

