Advanced Notion Meeting Intelligence

A specialized skill for preparing and documenting meetings using Notion — covering agenda generation from Notion context, pre-read assembly, action item tracking, decision logging, and post-meeting follow-up workflows integrated with Notion databases.

When to Use This Skill

Choose Advanced Notion Meeting Intelligence when you need to:

• Prepare meeting agendas by pulling context from Notion
• Assemble pre-read materials from existing Notion pages
• Track action items and decisions in Notion databases
• Generate follow-up tasks linked to meeting notes
• Build a searchable meeting knowledge base in Notion

Consider alternatives when:

• You need meeting transcription (use a transcription skill)
• You need calendar management (use a calendar skill)
• You need meeting analytics (use a meeting insights skill)

Quick Start

Copy
# Prepare a meeting using Notion context
claude "Prepare for my 1:1 with Sarah (Engineering Manager). Pull her recent project updates from Notion, draft an agenda, and create a meeting notes page."

Copy
# Meeting Prep: 1:1 with Sarah
**Date**: Dec 15, 2024 | **Duration**: 30 min

## Context Pulled from Notion
### Sarah's Active Projects
- Auth Redesign: 75% complete (from Projects DB)
- API Performance: Sprint 24, 3 issues remaining
- Team Hiring: 2 candidates in pipeline

### Recent Updates (Last 7 Days)
- Shipped auth session management (Dec 12)
- Opened 2 new P1 bugs in API perf project
- Requested additional backend engineer headcount

## Suggested Agenda
1. **Auth Redesign Status** (10 min)
   - Sprint 24 delivery confidence?
   - Any blockers from security review?

2. **API Performance P1 Bugs** (10 min)
   - Root cause identified?
   - Need cross-team support?

3. **Hiring Pipeline** (5 min)
   - Candidate status update
   - Interview scheduling

4. **Career Development** (5 min)
   - Q1 goals discussion
   - Any training/conference requests?

## Pre-Read Materials
- [Auth Redesign RFC](notion://page/xxx)
- [API Performance Dashboard](notion://page/yyy)
- [Q4 Team OKRs](notion://page/zzz)

Core Concepts

Meeting Workflow in Notion

Phase	Activities	Notion Integration
Preparation	Pull context, draft agenda	Search + fetch pages
Pre-Read	Assemble relevant documents	Link existing pages
During Meeting	Capture notes, decisions, actions	Meeting notes template
Follow-Up	Create tasks, share notes	Database entries, sharing
Archive	Tag and file for future reference	Database relations, tags

Meeting Notes Template

Copy
# Meeting Notes Template (Notion Page)

## Properties
- Meeting Type: [1:1 / Team / Stakeholder / Interview]
- Date: [date property]
- Attendees: [people property]
- Related Project: [relation to Projects DB]
- Status: [Draft / Final]

## Page Structure

### Agenda
- [ ] Topic 1 (time estimate)
- [ ] Topic 2 (time estimate)

### Notes
[Captured during meeting]

### Decisions Made
| Decision | Rationale | Owner | Date |
|----------|-----------|-------|------|

### Action Items
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|

### Follow-Up
- Next meeting date:
- Open questions for async:

Context Gathering

Copy
## Pulling Meeting Context from Notion

### Search for Relevant Pages
1. Search by attendee name in People properties
2. Search by project name in Project databases
3. Search for recent updates (last 7-14 days)

### Assemble Pre-Read
1. Identify pages related to agenda topics
2. Extract key data points (metrics, status, blockers)
3. Create a pre-read summary linking to full pages

### Historical Context
1. Find notes from previous meetings with same attendees
2. Check action items from last meeting (completed?)
3. Review decisions that need follow-up

Configuration

Parameter	Description	Example
meeting_type	Type of meeting	"one_on_one" / "team"
attendees	Meeting participants	["Sarah", "Bob"]
context_days	Days of history to pull	14
agenda_template	Template for agenda generation	"standard" / "brief"
track_actions	Create action items in database	true

Best Practices

1. Pull context 24 hours before the meeting — Give yourself time to review the assembled context and adjust the agenda. Last-minute preparation produces superficial agendas that waste meeting time on context-setting instead of decision-making.

2. Link meeting notes to project databases — Every meeting note should relate to the relevant project in your Projects database. This creates a searchable history: "Show me all meetings about the Auth Redesign project."

3. Track action item completion across meetings — Before each recurring meeting, check the action items from the last meeting. Open items should be the first agenda topic. This creates accountability and prevents items from being quietly dropped.

4. Archive meeting notes monthly — Active meeting notes in your workspace clutter search results. Move completed meeting notes to an archive section monthly, keeping only the last 30 days of meetings in the active view.

5. Use decision logs as a team reference — Decisions made in meetings get forgotten. A searchable Notion database of decisions (what, why, who, when) becomes the team's institutional memory. Reference it when someone asks "Why did we choose X?"

Common Issues

Meeting prep takes longer than the meeting itself — If assembling context for a 30-minute meeting takes 45 minutes, the process is too heavy. Automate context gathering with Notion API queries and standardize to a 10-minute prep template.

Action items are created but never reviewed — Notion action items that aren't part of a regular review cadence become invisible. Add a "My Actions" view to your daily dashboard that filters across all meeting notes for items assigned to you.

Previous meeting decisions contradict new ones — Without a decision log, teams unknowingly reverse previous decisions. Before making a decision, search the decision database for related entries and reference them: "In October we decided X. Are we reversing this, and if so, why?"