---
title: "Day 3 of 30: Granola + Claude Skills for Interactive Meetings"
url: https://stacklist.com/card/ce492979-a3b5-4026-a634-88ca2fa8e708
source_url: "https://mattpaige68.substack.com/p/day-3-of-30-granola-claude-skills?r=1qh21a&utm_medium=ios&triedRedirect=true"
stack: https://stacklist.com/stack/f3725201-e51d-4977-b61a-61e523b68980
summary: "Meeting OS is a Claude Skill that transforms Granola meeting transcripts into interactive, type-specific dashboards tailored to brainstorms, sales calls, planning sessions, and other meeting types. The integration surfaces key decisions, action items, open questions, and important quotes in a scannable, structured format rather than traditional text summaries."
tags: "meeting-os, claude-skills, granola, interactive-dashboard, meeting-transcripts, ai-automation"
key_entities: "Claude (technology), Granola (technology), Meeting OS (technology), Matt Paige (person), Claude Skills (concept), 30 Days of Claude Skills (event)"
classification: "tutorial"
content_hash: "sha256:5c7303808a05c4a9a036996266624c973ebd11987bc0d520ee5cc8915354dc99"
acp_version: "0.2"
token_counts_approximate: 4364
visibility: public
agent_accessible: true
status: "final"
---

# Day 3 of 30: Granola + Claude Skills for Interactive Meetings

Day 3 of 30: Granola + Claude Skills Is a Cheat Code for Making Your Meetings Interactive. Here’s How. 30 Days of Claude Skills You’ll Actually Use. Day 3 is Meeting OS, the skill that turns every Granola meeting into an interactive dashboard built for that specific meeting type. Matt Paige May 28, 2026 5 Share Granola plus Claude Skills is a literal cheat code for making your meetings interactive. Why an interactive dashboard you ask? Because who wants to read a transcript… Every meeting I have, I drop into Meeting OS and a few seconds later I’m looking at an interactive dashboard built for that specific meeting type. A brainstorm becomes an idea board. A planning session becomes a timeline. A sales call becomes a visual one-pager I can send to anyone who missed it. Every decision, every action item, every open question, every quote that actually mattered, laid out visually and ready to use. This is Day 3 of 30 Days of Claude Skills You’ll Actually Use. Day 3 is Meeting OS. Let’s build it. By the way, if you missed the first two days , the skills are at the bottom of this article. Day 1 does your email for you, and Day 2 gives everything you build Taste. (PS. Make sure to subscribe so you don’t miss any! Some will be free and some for paid subscribers only.) This Substack is reader-supported. To receive new posts like this Claude Skill series, consider becoming a free or paid subscriber. Subscribe What Meeting OS actually does Most meeting tools stop at the summary. Bullet points and action items in a text doc you read once and forget. Meeting OS goes further. It reads your Granola transcript, figures out what kind of meeting you just had (brainstorm, sales call, planning session, decision meeting, 1:1, status meeting, anything else), and builds an interactive dashboard tailored to that meeting type. You stop reading a wall of text and start clicking through a structured view of what happened. Underneath the type-specific layout, every dashboard surfaces the universals: every decision, every action item, every open question, every quote that actually mattered. The format makes it scannable. The universals make sure nothing falls through the cracks. Why Granola + Claude is a cheat code Two things have to be true for this to work. The transcript + summary has to be good. And the AI on top of it has to do something more than summarize. Granola handles the first part. It runs in the background of every meeting and captures the whole conversation. No bot joining the call, no awkward “recording has started.” It just works. The transcripts come out clean, with a beautifully crafted transcript and summary. Claude Skills handles the second part. A skill is just a markdown file you drop into Claude that tells it exactly how to handle a specific task. Drop in the Meeting OS skill and Claude knows to pull from Granola , figure out the meeting type, and build the right view. Most meeting tools give you notes. Granola plus Claude Skills gives you a workspace per meeting. How to set it up (two steps) Step 1: Connect Granola to Claude If you don’t already have Granola , get it. Granola is the AI notepad that sits in the background of every meeting and captures the whole conversation. No bot joining the call, no awkward “recording has started.” It just works. To connect Granola to Claude, open Claude and go to Customize → Connectors . Find Granola in the list and click Connect. Grant the permissions it asks for (read access to your meetings is what Meeting OS needs). About thirty seconds, no API key, no setup wizard. Once connected, Claude can pull your Granola meeting transcripts on demand. That’s the substrate Meeting OS sits on top of. Step 2: Drop the Meeting OS skill into Claude In Claude, create a new skill called meeting-os and paste the text below. Save it. That’s it. Claude will use it whenever you ask for a meeting dashboard. --- name: granola-meeting-os description: Builds an interactive visual dashboard from a Granola meeting — pulls the transcript, classifies the meeting type (brainstorm, planning, sales call, 1:1, retro, customer interview, decision, kickoff, status), and renders a tailored dashboard. Brainstorms become idea boards, planning sessions become timelines, sales calls become visual one-pagers you can send to anyone who missed the meeting. Every dashboard surfaces decisions, action items, open questions, and the quotes that actually mattered. Use this skill whenever the user references a Granola meeting and wants it visualized, recapped, dashboarded, or one-pagered — including casual phrasings like "visualize my last call", "what happened in my Granola today", "recap the standup", or "build a board from my brainstorm". Reach for it even when the user doesn't say "dashboard" — if there's a Granola meeting and they want it rendered visually, this is the skill. --- # Granola Meeting OS Turn a Granola meeting into a visual dashboard — one polished enough to send to someone who missed it and have them walk away knowing what happened. The skill has three jobs: 1. Get the right meeting out of Granola 2. Figure out what kind of meeting it was 3. Render a dashboard shaped around that kind Step 1 and 2 are easy. Step 3 is where the work is — the dashboard needs to be distinctive, scannable, honest, and shareable. ## Workflow ### Step 1 — Pick the meeting Default to most recent unless the user specifies otherwise. - **Default / "my last meeting" / "the call I just had"**: `Granola:list_meetings` sorted desc, take the first. - **By topic** ("the call with Marcus", "the GenDD review"): `Granola:query_granola_meetings` with the user's phrasing. - **By date** ("yesterday's standup", "Monday's planning session"): `Granola:list_meetings` filtered to the time window. If the reference is ambiguous (e.g., "the sales call" when there have been several recently), list 2-3 candidates with title + date and ask which one. Don't guess. If Granola isn't reachable or returns nothing, offer to work from a pasted transcript or a Granola meeting URL instead. The rest of the workflow stays the same once the transcript is in hand. ### Step 2 — Pull the content - `Granola:get_meeting_transcript` for the raw transcript with speaker turns. - `Granola:get_meetings` for Granola's auto-generated notes. Use both. The notes are a cleaner starting point for structured fields (action items Granola already pulled out). The transcript is essential for quotes — those have to be actual lines people said, not paraphrases. ### Step 3 — Classify the meeting type Read `references/meeting-types.md` before deciding. It has signal patterns for every supported type plus the per-type extraction spec. The supported types and their dashboards: | Type | Dashboard shape | |---|---| | Brainstorm / ideation | Idea board — clustered cards grouped by theme | | Planning session | Timeline — milestones, owners, dependencies | | Sales call / pitch | Visual one-pager — prospect header, pains, proposal, next steps | | 1:1 | Scorecard — wins, blockers, asks, follow-ups | | Retro | Three-column board — went well / didn't / try next | | Customer interview / discovery | Insight cards — jobs, pains, current solutions, opportunities | | Decision meeting | Decision log — options weighed, rationale, owners | | Kickoff | Project canvas — goals, scope, team, timeline, risks | | Status update / standup | Status grid — by person or workstream, RAG indicators | | Unknown / mixed | Universal recap — decisions, actions, questions, quotes | If a meeting is genuinely hybrid (half status / half decision, or a brainstorm that turned into planning), pick the dominant mode and note the secondary character in the dashboard's intro line. Don't force a square peg. ### Step 4 — Extract the payload Every dashboard surfaces these four, regardless of type: - **Decisions** — what was actually decided, with one-line rationale. Skip "we'll think about it" non-decisions. - **Action items** — owner, action, due date if mentioned. Skip vague "we should look into..." with no owner. - **Open questions** — things genuinely left hanging. Not rhetorical questions. - **Key quotes** — 3-6 real lines from the transcript that crystallize a moment: an insight, a commitment, an objection, a breakthrough. Attributed to the speaker. Lightly cleaned for filler ("um", "you know") but otherwise verbatim. If you can't quote, don't — a paraphrase pretending to be a quote is worse than no quote. Each meeting type also has its own type-specific fields. See `references/meeting-types.md` for the per-type extraction spec and visual layout sketch. ### Step 5 — Render the dashboard Read `references/dashboard-design.md` before writing HTML. It's the design system — color palettes per meeting type, typography, layout patterns, the patterns that signal "AI dashboard" and the ones that signal "hand-crafted." Build a single self-contained HTML file at `/mnt/user-data/outputs/<meeting-slug>-dashboard.html`: - Inline `<style>` only — no Tailwind CDN, no external stylesheets - Inline `<script>` for any interactivity (collapse/expand sections, filter actions by owner, etc.) - No images requiring network access - Has to open and render correctly when downloaded and double-clicked Then call `present_files` with the path. ## Quality bar A good dashboard: - Looks hand-crafted, not AI-templated - Reads in 30 seconds for the top-line, 2 minutes for the full picture - Has one dominant color, chosen for the meeting's mood (see design reference) - Treats quotes as first-class — pulled into callouts with attribution, not buried in paragraphs - Omits empty sections rather than showing "No decisions" - Sits well on one desktop screen for the main view, with detail below the fold if needed - Has no "AI" or "Claude" signature anywhere — feels like Matt built it A bad dashboard: - Generic gradients, stock icon sets - Equal-weight everything (no typographic hierarchy) - Paraphrased "quotes" no human said that way - Emojis stuffed into section headers (acceptable only for playful types — retro, brainstorm) - "Action items" that are actually rephrased status updates - A footer that says "Generated by AI" ## When the transcript is too thin If the transcript is under ~150 words, fragmentary, or just status pings ("Looks good." "Sounds good." "Done."), don't manufacture content. Say so plainly and offer one of: 1. Use Granola's generated notes instead (sometimes meatier than the transcript) 2. Bundle multiple related meetings into a thread-level dashboard 3. Skip the dashboard and write a short prose recap Three real items beats ten padded ones. ## Output End the turn with `present_files` pointing at the HTML file and a single line — "Here's the dashboard." Don't narrate what's in it; the dashboard speaks for itself. If Matt wants changes, he'll say so. That’s the skill. Two minutes to paste, then it’s ready. What it looks like in use Ask Claude to “Meeting OS my 10am sales call” or “build the dashboard for yesterday’s planning meeting” and it pulls the transcript, detects the type, and builds the right view: Brainstorm → Idea Board. Every idea clustered into themes, each card tagged with who said it, top three highlighted. Useful for going back later and remembering which idea actually had traction. Planning session → Timeline. Phases, milestones, owners, dependencies. Useful for sharing after a planning meeting so nobody asks “what did we decide on the launch date again.” Sales call → Visual One-Pager. The customer’s pain in their own words, the solution discussed, next steps, decision-makers. Share-ready. Send to anyone on the team who needs to know what happened on the call. Customer call → Insight Card. Customer situation, asks, themes pulled from their language. Useful for customer success and product teams catching up. Decision meeting → Decision Map. The question, the options, the choice, the reasoning, the open risks. Useful for going back six months later when somebody asks why you picked that. Standup → Status Grid. Each person’s section, blockers highlighted. Useful for asynchronous teammates who missed the live meeting. 1:1 → Conversation Recap. Themes covered, personal or career items, action items for both parties. Check out this example Interactive Claude Artifact created by the Claude Skill: (Give it a click to see it in action) Every dashboard, regardless of format, ends with the universal extraction: decisions, action items, open questions, quotes. The format makes it scannable. The universals make sure nothing important slips. Pro tip : the meeting types above are the defaults Meeting OS comes with. Add your own. If you run weekly retros, customer onboarding calls, design crits, partner check-ins, whatever you have a regular cadence for, edit the skill text in Step 2 to define a new meeting type and the dashboard layout you want for it. The skill scales with however many meeting types you want it to handle. How to tailor it for your meetings The skill above is my version. Yours probably needs different meeting type detection or different layouts for the specific kinds of meetings you run. Use this meta-prompt to have Claude interview you and produce a customized version. I'm about to save the Meeting OS skill. Before I do, interview me about my meetings and produce a customized version. Topics to cover: 1. What kinds of meetings I run most often (brainstorms, sales calls, 1:1s, others I have that aren't in the default list) 2. What dashboard layout I want for each of those types 3. Specific things I always want surfaced (commitments I made, anything mentioning a specific client or project, mentions of risk) 4. Anything to skip (sections I don't want) 5. How I want shareable outputs formatted (for clients, for team, for executives) After I answer, produce a customized version of the Meeting OS skill with my specifics. Summarize what changed before showing me the final version. The base skill is: [PASTE THE SKILL FROM STEP 2 HERE] Spend ten minutes answering. The output is a skill tailored to how you actually run your meetings. Other ways to use Meeting OS A few extensions worth knowing: Share the dashboard with your team. The dashboard for a sales call or planning session is share-ready out of the box. Once Claude builds the artifact, click the drop down next to copy, and click Publish Artifact . Claude turns it into a hosted shareable URL you can drop into Slack, an email, or anywhere else. People who open it get the full interactive dashboard in their browser, no Claude account needed. Multi-meeting dashboards. Point Meeting OS at multiple meetings (a sales cycle, a project phase) and ask for a cross-meeting dashboard. Useful for pulling threads across a series of conversations. Hand the dashboard to other agents. The structured output (decisions, action items, owners) is perfect input for downstream agents. If you’ve already built Email Autopilot from Day 1 or any other agent that needs meeting context, Meeting OS hands it the cleanest version of that context. Go deeper on Granola + Claude. I wrote a separate guide on connecting Granola to Claude Code for non-dashboard use cases: turning meetings into prompts that produce finished work (apps, drafts, follow-ups). That guide is here if you want to push Granola + Claude beyond Meeting OS. I also wrote a guide on how to use Recipes in Granola, plus my 20 favorites you can steal. If you don’t know what a Granola Recipe is, I highly recommend you check this out . What to do this week Get Granola if you don’t have it. Connect Granola in Claude. Customize → Connectors → Granola → Connect. About thirty seconds. Save Meeting OS as a skill in Claude (the text in Step 2). Run it on your next meeting. Ask Claude to “Meeting OS my [date/title] meeting” and watch what comes out. Click Publish on the artifact and send the shareable URL to anyone who needs to see what happened. Tailor it with the meta-prompt above if the default layouts don’t match how you run meetings. By the end of the week, every meeting you have ends with a dashboard you can actually use and share. If you missed Day 1 and Day 2 in the series… The earlier skills in this series, all ready to paste into Claude like Meeting OS: Day 1: Email Autopilot . The skill that triages your inbox into Needs Response / FYI / Noise, ranks the response bucket P1 / P2 / P3, and drafts replies in your voice. Also introduces the my-voice shared-base-skill pattern that future drafting skills in the series build on top of. Day 2: Taste Skill . A free open-source skill that makes anything you build with AI stop looking like AI. Comes with style variants for minimalist, brutalist, and high-end visual design. Build the trio (Email Autopilot, Taste Skill, Meeting OS) and you’ve got an AI that triages your inbox, designs your apps with taste, and turns your meetings into dashboards. Solid stack from three short articles. Day 3 down. 27 more to go. If you want each skill as it drops, stay subscribed. I got some good ones coming up 😎. This Substack is reader-supported. To receive new posts like this Claude Skills series, consider becoming a free or paid subscriber. Subscribe 5 Share