granola-install-auth
Installs the Granola desktop application and guides users through system-level permission configuration.
Install
mkdir -p .claude/skills/granola-install-auth && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6330" && unzip -o skill.zip -d .claude/skills/granola-install-auth && rm skill.zipInstalls to .claude/skills/granola-install-auth
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Install and configure Granola AI meeting notes with calendar and audioKey capabilities
- →Install Granola on macOS via Homebrew or direct download
- →Install Granola on Windows via an executable installer
- →Create an account and authenticate using Google or Microsoft
- →Grant system permissions for microphone and screen recording on macOS
- →Verify microphone permissions on Windows
- →Connect Google Calendar or Microsoft Outlook for meeting detection
How it works
This skill guides the user through the installation and initial configuration of the Granola AI meeting notes app. It covers downloading, account creation, system permissions, and calendar integration.
Inputs & outputs
When to use granola-install-auth
- →Installing Granola via Homebrew
- →Granting microphone access
- →Configuring audio capture permissions
- →Setting up calendar authentication
About this skill
Granola Install & Auth
Overview
Install Granola, the AI notepad that captures meeting audio directly from your device (no bot joins the call), transcribes with GPT-4o/Claude, and produces structured notes with action items. Supports Zoom, Google Meet, Teams, Slack Huddles, and WebEx.
Prerequisites
- macOS 12+ or Windows 10+ (iOS/Android for mobile)
- Google Calendar or Microsoft Outlook account
- Active internet connection for initial auth
Instructions
Step 1 — Download and Install
# macOS via Homebrew
brew install --cask granola
# Or download directly
open "https://www.granola.ai/download"
Windows: download the installer from granola.ai/download and run the .exe.
Step 2 — Create Account and Authenticate
- Launch Granola
- Click Sign up — authenticate with Google or Microsoft
- Granola uses WorkOS for SSO; enterprise users may see their IdP login (Okta, Azure AD)
Step 3 — Grant System Permissions
macOS (critical — both required):
System Settings > Privacy & Security > Microphone
→ Enable Granola
System Settings > Privacy & Security > Screen & System Audio Recording
→ Enable Granola
The Screen Recording permission is required because macOS bundles system audio capture under that category — Granola does not record your screen.
Windows: Microphone permissions are granted automatically. Confirm at:
Settings > Privacy & Security > Microphone → Granola enabled
Step 4 — Connect Calendar
- Granola Settings (avatar bottom-left) > Calendar
- Connect Google Calendar or Microsoft Outlook
- Select which calendars to sync (personal, work, shared)
- Granola detects meetings from synced calendars with video/conference links
Step 5 — Verify Audio Capture
# macOS — confirm Granola is running
pgrep -l Granola
# Check installed version
defaults read /Applications/Granola.app/Contents/Info.plist CFBundleShortVersionString 2>/dev/null || echo "Check Granola > About"
Join or start any meeting (Zoom, Meet, Teams). Granola shows a floating notepad when it detects a calendar event with a conferencing link. Verify the live transcription indicator appears.
Step 6 — Configure Preferences
| Setting | Location | Recommended |
|---|---|---|
| Auto-start with calendar | Preferences > General | On |
| Default template | Preferences > Templates | Match your meeting type |
| AI model | Uses GPT-4o/Claude | No configuration needed |
| Auto-update | Preferences > General | On |
Output
- Granola installed and running on login
- Calendar connected with meeting auto-detection
- System audio + microphone permissions granted
- Live transcription verified on a test call
Error Handling
| Error | Cause | Fix |
|---|---|---|
| No audio captured | Missing Screen & System Audio permission (macOS) | System Settings > Privacy & Security > Screen & System Audio Recording > enable Granola, then restart |
| Calendar not syncing | OAuth token expired or wrong account | Disconnect calendar in Settings, re-authenticate |
| App won't launch | macOS Gatekeeper block | Right-click Granola.app > Open, or xattr -cr /Applications/Granola.app |
| Meeting not detected | Event has no video link | Add a Zoom/Meet/Teams link to the calendar event |
| Bluetooth audio drops | BT device causes transcription stops | Switch to built-in mic or wired headset |
Granola Architecture (How It Works)
Your Device Audio ──→ Granola Desktop App ──→ Granola Cloud (transcription)
│ │
Local notepad GPT-4o / Claude
(your typed notes) (enhance + summarize)
│ │
└────── Merged Output ───┘
│
Structured meeting notes
with action items
- Audio is transcribed server-side; Granola does not store raw audio after processing
- Your typed notes are merged with the transcript for context-aware summaries
- No bot joins your meeting — capture happens via system audio
Resources
Next Steps
After installation, proceed to granola-hello-world for your first meeting capture.
When not to use it
- →When the operating system is not macOS 12+ or Windows 10+
- →When a Google Calendar or Microsoft Outlook account is not available
- →When there is no active internet connection for initial authentication
Prerequisites
Limitations
- →macOS Screen Recording permission is required for system audio capture
- →Bluetooth audio devices may cause transcription stops
- →Meeting detection requires a video/conference link in the calendar event
How it compares
This skill provides step-by-step instructions and commands for Granola setup, simplifying the process compared to manually navigating system settings and application interfaces.
Compared to similar skills
granola-install-auth side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| granola-install-auth (this skill) | 1 | 27d | Review | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
dev-browser
SawyerHood
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools