granola-core-workflow-a

Meeting preparation and template setup in Granola — templates, recipes, and pre-meeting workflows. Use when configuring note templates for 1:1s, standups, discovery calls, or sprint planning, creating custom recipes, or preparing agenda notes before important meetings. Trigger: "granola template", "granola meeting prep", "granola recipe", "granola agenda".

1,868 stars

Best use case

granola-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Meeting preparation and template setup in Granola — templates, recipes, and pre-meeting workflows. Use when configuring note templates for 1:1s, standups, discovery calls, or sprint planning, creating custom recipes, or preparing agenda notes before important meetings. Trigger: "granola template", "granola meeting prep", "granola recipe", "granola agenda".

Teams using granola-core-workflow-a should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/granola-core-workflow-a/SKILL.md --create-dirs "https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/main/plugins/saas-packs/granola-pack/skills/granola-core-workflow-a/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/granola-core-workflow-a/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How granola-core-workflow-a Compares

Feature / Agentgranola-core-workflow-aStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Meeting preparation and template setup in Granola — templates, recipes, and pre-meeting workflows. Use when configuring note templates for 1:1s, standups, discovery calls, or sprint planning, creating custom recipes, or preparing agenda notes before important meetings. Trigger: "granola template", "granola meeting prep", "granola recipe", "granola agenda".

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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]
```

4. 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

## 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.

Related Skills

calendar-to-workflow

1868
from jeremylongshore/claude-code-plugins-plus-skills

Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".

workhuman-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".

workhuman-core-workflow-a

1868
from jeremylongshore/claude-code-plugins-plus-skills

Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".

wispr-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".

wispr-core-workflow-a

1868
from jeremylongshore/claude-code-plugins-plus-skills

Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".

windsurf-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".

windsurf-core-workflow-a

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".

webflow-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".

webflow-core-workflow-a

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".

veeva-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".

veeva-core-workflow-a

1868
from jeremylongshore/claude-code-plugins-plus-skills

Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".

vastai-core-workflow-b

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".