granola-core-workflow-a — Claude Code skill: features and setup
granola-core-workflow-a configures meeting templates, chat recipes, and pre-call context inside Granola. Helps structure agendas and summaries for standups and customer calls.
MIT 1 installs ★ 2,935 updated 2026-11-01
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a claude-codeWhat granola-core-workflow-a does
This skill guides the coding assistant through configuring meeting structures in Granola. The app provides 29 default templates for scenarios like 1-on-1s and sprint planning. The guide helps write custom Markdown templates with bracketed formatting hints and sets auto-trigger rules based on calendar keywords or attendee domains.
It also sets up saved chat prompts called recipes. Invoking commands like /follow-up or /bant via slash prompts generates post-meeting emails or BANT qualification summaries directly from the recording. For shared workspaces, default templates map directly to folders such as #engineering or #sales-calls.
The setup requires an authenticated Granola client and a synced calendar. You also need at least one previously captured meeting. Typing agenda notes into an external editor breaks the process: context must stay in Granola's native notepad so Enhance Notes can merge it with the audio.
What it helps with
- structure meeting notes with custom Markdown templates
- set up pre-call goals and context in the notepad
- create slash recipes like /follow-up for Granola Chat
- assign folder templates based on calendar keywords
Example prompts for the agent
- Help me create a custom Granola template for customer feedback calls
- Suggest Granola Chat recipes to extract action items and blockers after a standup
- How do I configure automatic template selection based on calendar invite domains?
How to install granola-core-workflow-a
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a claude-code2Manually: put the files in place
~/.claude/skills/granola-core-workflow-a/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/granola-core-workflow-a/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a codex2Manually: put the files in place
.agents/skills/granola-core-workflow-a/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a cursor2Manually: put the files in place
.cursor/skills/granola-core-workflow-a/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/granola-core-workflow-a2Manually: put the files in place
.github/skills/granola-core-workflow-a/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/granola-core-workflow-aManually: put the files in place
.devin/skills/granola-core-workflow-a/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -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-core-workflow-a
How to install granola-core-workflow-a in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill granola-core-workflow-a -a claude-code in your terminal.
What does granola-core-workflow-a do?
It gives your assistant instructions for designing note templates, reusable chat recipes, and pre-call preparation flows in Granola.
What is required before using these workflows?
You need an authenticated Granola desktop app, an active calendar sync, and at least one recorded call. Pre-meeting notes must be typed directly inside Granola's notepad for Enhance Notes to incorporate them.
Source text
SKILL.md · MIT
--- name: granola-core-workflow-a description: "Meeting preparation and template setup in Granola \u2014 templates,\ \ recipes, and pre-meeting workflows.\nUse when configuring note templates for 1:1s,\ \ standups, discovery calls, or sprint planning,\ncreating custom recipes, or preparing\ \ agenda notes before important meetings.\nTrigger: \"granola template\", \"granola\ \ meeting prep\", \"granola recipe\", \"granola agenda\".\n" allowed-tools: Read, Write, Edit version: 1.13.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - granola - workflow - templates compatibility: Designed for Claude Code --- # Granola Core Workflow A: Meeting Preparation & Templates ## Overview Configure Granola templates (which structure the enhanced output) and recipes (repeatable Chat prompts) for consistent, high-quality meeting notes. Granola ships with 29 built-in templates and supports custom templates per workspace. ## Prerequisites - Granola installed and authenticated - Calendar synced with upcoming meetings - At least one meeting captured (to understand the enhancement flow) ## Instructions ### Step 1 — Choose a Built-in Template Click the **Change template** icon at the bottom of your notes before or during a meeting: | Template | Best For | Sections Generated | |----------|----------|-------------------| | **1-on-1** | Manager/report check-ins | Check-in, Updates, Discussion, Action Items | | **Stand-up** | Daily sync | Progress, Blockers, Priorities | | **Discovery Call** | Sales prospecting | Budget, Authority, Need, Timeline (BANT) | | **Sprint Planning** | Agile ceremonies | Sprint Goals, Velocity, Backlog, Risks | | **Weekly Team** | Status meetings | Updates, Decisions, Action Items | | **Interview Debrief** | Hiring loops | Candidate Assessment, Strengths, Concerns | | **Project Kick-Off** | New initiatives | Goals, Scope, Timeline, RACI | | **Pipeline Review** | Sales forecast | Deal Status, Next Steps, Risks | | **Design Crit** | Creative review | Feedback, Changes Requested, Approvals | Templates tell the AI how to structure the enhanced output — a sales call produces different sections than a standup. ### Step 2 — Create a Custom Template 1. Open Granola Settings > **Templates** 2. Click **Create New Template** 3. Define the structure using section headers: ```markdown ## Customer Feedback Session ### Context [Brief on the customer and their product usage] ### Key Feedback Themes [Grouped by category: UX, Performance, Features, Support] ### Verbatim Quotes [Direct customer quotes with timestamps] ### Severity Assessment [Critical / High / Medium / Low for each issue] ### Action Items [Owner, task, due date] ### Follow-Up Commitment [What we promised the customer and by when] ``` 1. Name it and optionally set auto-trigger conditions: - Calendar event title contains specific keywords (e.g., "feedback", "customer") - Attendee email domains (e.g., `@customer.com`) ### Step 3 — Create Recipes for Granola Chat Recipes are saved prompts invoked with `/` in Granola Chat: | Recipe | Prompt | Use Case | |--------|--------|----------| | `/follow-up` | "Draft a professional follow-up email summarizing decisions and next steps" | Post-meeting email | | `/standup` | "Extract blockers, progress updates, and priorities per person" | Standup summary | | `/bant` | "Analyze this call using BANT framework (Budget, Authority, Need, Timeline)" | Sales qualification | | `/prd` | "Write a PRD based on the product requirements discussed in this meeting" | Product spec | | `/coaching` | "Based on this 1:1, suggest coaching points and development areas" | Manager prep | | `/decision-log` | "List all decisions made, who made them, and the reasoning" | Governance | Create custom recipes at Settings > **Recipes** or directly in Chat. ### Step 4 — Pre-Meeting Preparation Before important meetings, type context into the Granola notepad **before** the call starts: ```markdown ## Pre-Meeting Context - Last meeting: discussed Series A timeline, concerns about runway - Open items: term sheet review, board seat allocation - My goals today: confirm valuation range, discuss liquidation preference - Questions to ask: timeline for closing, co-investor status ``` When you click **Enhance Notes** after the meeting, Granola combines: 1. Your pre-meeting context 2. Your live notes during the meeting 3. The full audio transcript This produces output that is aware of your goals and prior context. ### Step 5 — Set Template Defaults per Workspace For team deployments, set default templates per shared folder: | Folder | Default Template | Auto-Apply | |--------|-----------------|------------| | `#sales-calls` | Discovery Call | Events with external attendees | | `#engineering` | Sprint Planning | Events titled "sprint" or "planning" | | `#leadership` | Weekly Team | Events with >5 attendees | | `#interviews` | Interview Debrief | Events titled "interview" | ## Output - Templates configured for each meeting type - Custom recipes created for post-meeting workflows - Pre-meeting context workflow established - Consistent structured output across team meetings ## Error Handling | Issue | Cause | Fix | |-------|-------|-----| | Wrong template applied | Auto-trigger matched incorrectly | Narrow trigger conditions (more specific keywords) | | Template sections empty | Meeting lacked relevant discussion | Remove irrelevant sections from template | | Recipe not appearing | Not saved to workspace | Save recipe in Settings > Recipes | | Pre-meeting notes lost | Typed in wrong app | Ensure you type in the Granola notepad, not a separate editor | ## Template Design Best Practices 1. **Use clear section headers** — Granola's AI parses headers to organize content 2. **Include bracketed hints** — `[Owner, task, due date]` guides the AI output format 3. **Keep templates under 10 sections** — too many sections dilute content 4. **Add a "Verbatim Quotes" section** for customer-facing meetings — captures exact language 5. **End with "Action Items" and "Next Steps"** — the AI reliably fills these ## Examples For a fictional meeting fixture, record `fixture=meeting-basic-v2; capture=accepted; output=redacted-summary; consent=test-only; retention=none; cleanup=complete` rather than storing notes or transcript text. ## Resources - [Customize Notes with Templates](https://docs.granola.ai/help-center/taking-notes/customise-notes-with-templates) - [Introducing Recipes](https://www.granola.ai/blog/say-hello-to-recipes) - [Get the Best from Granola](https://www.granola.ai/blog/get-the-best-from-granola) ## Next Steps Proceed to `granola-core-workflow-b` for post-meeting processing and sharing workflows.
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace