ReddRadar
Agent skill
granola-core-workflow-b
Post-meeting note processing and sharing workflow with Granola. Use when reviewing meeting notes, sharing with team members, or processing action items after meetings. Trigger with phrases like "granola post meeting", "share granola notes", "granola follow up", "process meeting notes", "granola action items".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/granola-core-workflow-b
SKILL.md
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
| Action | Owner | Due | Status |
|--------|-------|-----|--------|
| Update API documentation | @mike | Jan 8 | Pending |
| Review design mockups | @sarah | Jan 7 | Pending |
| Schedule client demo | @alex | Jan 10 | Pending |
### 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
/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
Next Steps
Proceed to granola-common-errors for troubleshooting common issues.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?