domains / documents / notion-meeting-prep / notion-meeting-intelligence

notion-meeting-intelligence

Skill card

combined

The openai/skills and composio-community copies are identical and describe a single-document workflow driven by a template-selection guide. The Prat011 copy overlaps on the core Notion search/fetch/create steps but diverges materially: it mandates producing two separate documents (an internal pre-read and an external agenda), provides detailed content structures for each, and includes a document-linking step. Crowning the openai/composio version would hide the two-document alternative, so the copies should be combined.

Repositories

Other copies

Combined skill

---
name: notion-meeting-intelligence
description: Prepare meeting materials with Notion context and research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
metadata:
  short-description: Prep meetings with Notion context and tailored agendas
---

# Meeting Intelligence

Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with research.

## Quick start
1) Confirm meeting goal, attendees, date/time, and decisions needed.
2) Gather context: search with `Notion:notion-search`, then fetch with `Notion:notion-fetch` (prior notes, specs, OKRs, decisions).
3) Pick the right template via `reference/template-selection-guide.md` (status, decision, planning, retro, 1:1, brainstorming).
4) Draft agenda/pre-read in Notion with `Notion:notion-create-pages`, embedding source links and owner/timeboxes.
5) Enrich with research (industry insights, benchmarks, risks) and update the page with `Notion:notion-update-page` as plans change.

## Workflow
### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
1. Add the Notion MCP:
   - `codex mcp add notion --url https://mcp.notion.com/mcp`
2. Enable remote MCP client:
   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
3. Log in with OAuth:
   - `codex mcp login notion`

After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.

### 1) Gather inputs
- Ask for objective, desired outcomes/decisions, attendees, duration, date/time, and prior materials.
- Search Notion for relevant docs, past notes, specs, and action items (`Notion:notion-search`), then fetch key pages (`Notion:notion-fetch`).
- Capture blockers/risks and open questions up front.

### 2) Choose format
- Status/update → status template.
- Decision/approval → decision template.
- Planning (sprint/project) → planning template.
- Retro/feedback → retrospective template.
- 1:1 → one-on-one template.
- Ideation → brainstorming template.
- Use `reference/template-selection-guide.md` to confirm.

### 3) Build the agenda/pre-read
- Start from the chosen template in `reference/` and adapt sections (context, goals, agenda, owner/time per item, decisions, risks, prep asks).
- Include links to pulled Notion pages and any required pre-reading.
- Assign owners for each agenda item; call out timeboxes and expected outputs.
- If the meeting involves external participants, create two documents:
  - **Internal Pre-Read** (for internal attendees): Meeting Overview, Background Context, Current Status, Context & Insights, Key Discussion Points, What We Need from This Meeting.
  - **External Agenda** (for all participants): Meeting Details, Objective, Agenda Items with time allocations, Discussion Topics, Decisions Needed, Action Items, Related Resources.

### 4) Enrich with research
- Add concise research where helpful: market/industry facts, benchmarks, risks, best practices.
- Keep claims cited with source links; separate fact from opinion.
- Use general knowledge only; do not fabricate specific facts.

### 5) Finalize and share
- Add next steps and owners for follow-ups.
- If tasks arise, create/link tasks in the relevant Notion database.
- Update the page via `Notion:notion-update-page` when details change; keep a brief changelog if multiple edits.
- If two documents were created, link the pre-read to the agenda and both to the relevant project page.

## References and examples
- `reference/` — template picker and meeting templates (e.g., `template-selection-guide.md`, `status-update-template.md`, `decision-meeting-template.md`, `sprint-planning-template.md`, `one-on-one-template.md`, `retrospective-template.md`, `brainstorming-template.md`).
- `examples/` — end-to-end meeting preps (e.g., `executive-review.md`, `project-decision.md`, `sprint-planning.md`, `customer-meeting.md`).

## Conflicts
- **Prat011/awesome-llm-skills** requires creating two separate Notion pages (internal pre-read and external agenda) and linking them, while **openai/skills** and **composio-community/awesome-codex-skills** describe a single agenda/pre-read page updated via `Notion:notion-update-page`.
- **openai/skills** and **composio-community/awesome-codex-skills** include a Step 0 for setting up the Notion MCP connection that is absent from **Prat011/awesome-llm-skills**.
- **Prat011/awesome-llm-skills** specifies detailed content structures for internal pre-reads and external agendas, while the other copies rely on templates in a `reference/` directory without specifying those structures.