Agent skill · operations · jeremylongshore
granola-incident-runbook
Incident response procedures for Granola meeting capture failures and
Why this skill is useful
Provides specific incident response procedures and scripts for handling Granola service outages that the AI wouldn't reliably generate on its own.
What it needs
Requires granola account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Granola Incident Runbook Overview Standard operating procedures for Granola incidents — from individual recording failures to organization-wide outages. Covers triage, remediation, communication, escalation, and post-incident review. Designed for IT admins, team leads, and individual users. Prerequisites Granola admin access (for org-level incidents) Bookmark status.granola.ai for service status Internal communication channel identified (#granola-support or similar) Instructions Step 1 — Triage: Assess Severity Severity Description Response Time Example ---------- ------------- --------------- --------- P1 Critical Org-wide outage, data loss risk Immediate Granola service down, no one can record P2 High Multiple users affected < 1 hour Recording fails for a team, sync broken P3 Medium Single user issue < 4 hours One person's transcription stopped P4 Low Minor issue, workaround exists < 24 hours UI glitch, slow processing Scope assessment questions: 1. Is it just you, or are others affected too? → Ask in #granola-support 2. Is status.granola.ai showing an incident? → P1/P2 if yes 3. Was it working earlier today? → Recent change (OS update, permissions) likely 4. Which platform? (Zoom/Meet/Teams) → Platform-specific audio routing Step 2 — Remediation by Incident Type --- Incident: "Meeting Not Recording" Severity: P3 (single user) or P2 (team-wide) Immediate actions: 1. Click Granola menu bar icon > Start Recording (manual override) 2. If manual start fails: Check that the meeting has audio playing Verify Granola is running: pgrep -l Granola Restart: right-click menu bar icon > Restart Granola Root cause investigation: [ ] Calendar event has a video conferencing link (Zoom/Meet/Teams) [ ] Calendar is connected in Settings > Calendar [ ] Microphone permission granted [ ] Screen & System Audio Recording permission granted (macOS) [ ] Not running conflicting audio software (Loopback, BlackHole) Backup: Take manual notes. After fixing, re-record the next meeting. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/granola-incident-runbook