granola-core-workflow-b

Granola Core Workflow B: Post-Meeting Processing

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "granola-core-workflow-b" with this command: npx skills add jeremylongshore/claude-code-plugins-plus-skills/jeremylongshore-claude-code-plugins-plus-skills-granola-core-workflow-b

Granola Core Workflow B: Post-Meeting Processing

Overview

Process, enhance, and share Granola meeting notes for maximum team productivity.

Prerequisites

  • Completed meeting with Granola capture

  • Notes generated (typically 1-2 minutes after meeting)

  • Team sharing preferences configured

Instructions

Step 1: Review AI-Generated Notes

Immediately after meeting ends:

  • Open Granola

  • Find meeting in recent list

  • Review generated content:

  • Summary accuracy

  • Action items captured

  • Key points highlighted

  • Participant attribution

Step 2: Enhance Notes

Edit and improve AI output:

Review Checklist

  • Correct any transcription errors
  • Add context AI might have missed
  • Clarify ambiguous action items
  • Add links to referenced documents
  • Tag relevant team members
  • Mark confidential sections

Step 3: Extract and Assign Action Items

Process action items for tracking:

Action Item Processing

From Meeting: Sprint Planning 2025-01-06

ActionOwnerDueStatus
Update API documentation@mikeJan 8Pending
Review design mockups@sarahJan 7Pending
Schedule client demo@alexJan 10Pending

Export Format (for ticket systems):

  • [HIGH] Update API documentation (@mike, due: 2025-01-08)
  • [MED] Review design mockups (@sarah, due: 2025-01-07)
  • [MED] Schedule client demo (@alex, due: 2025-01-10)

Step 4: Share with Stakeholders

Share via Granola

  • Click "Share" button

  • Select recipients or copy link

  • Set permissions (view/edit)

  • Send with optional message

Share via Integrations

Slack: Channel: #team-meeting-notes Format: Summary + Action Items

Notion: Database: Meeting Archive Page: Full notes with transcript

Email: Recipients: Meeting attendees Content: Summary + Action Items Attachment: PDF export

Step 5: Archive and Categorize

Organize for future reference:

Filing System

Folder Structure: /meetings /2025 # 2025 year /q1 /project-alpha 2025-01-06-sprint-planning.md 2025-01-08-client-sync.md /team-1-1s 2025-01-06-sarah-1-1.md

Tags:

  • #decision - Contains key decisions
  • #action-items - Has pending tasks
  • #client - External stakeholder present
  • #confidential - Sensitive content

Post-Meeting Checklist

Within 5 Minutes

  • Review AI summary for accuracy
  • Correct obvious transcription errors
  • Confirm action items are captured

Within 1 Hour

  • Share notes with attendees
  • Create tickets for action items
  • Send follow-up email if needed

Within 24 Hours

  • Archive in project folder
  • Update relevant documentation
  • Schedule follow-up meetings if needed

Output

  • Reviewed and enhanced meeting notes

  • Action items extracted and assigned

  • Notes shared with stakeholders

  • Meeting properly archived

Sharing Best Practices

  • Share promptly - Within 1 hour while fresh

  • Highlight decisions - Make outcomes clear

  • Assign owners - Every action needs an owner

  • Set due dates - Create accountability

  • Link to source - Reference full notes

Error Handling

Issue Cause Solution

Notes not appearing Still processing Wait 2-5 minutes

Sharing failed Permission issue Check recipient access

Action items missing Not stated clearly Add manually

Wrong attendees Calendar mismatch Edit attendee list

Resources

  • Granola Sharing Options

  • Follow-up Best Practices

Next Steps

Proceed to granola-common-errors for troubleshooting common issues.

Examples

Basic usage: Apply granola core workflow b to a standard project setup with default configuration options.

Advanced scenario: Customize granola core workflow b for production environments with multiple constraints and team-specific requirements.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

backtesting-trading-strategies

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

svg-icon-generator

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

performance-lighthouse-runner

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

mindmap-generator

No summary provided by upstream source.

Repository SourceNeeds Review