AutoGineer
Generated banner for Notion Meeting Intelligence
Generated logo for Notion Meeting Intelligence

Notion Meeting Intelligence

JetBrainsOfficialCreated by OpenAIDistributed by JetBrains

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
— the description by OpenAI

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow for preparing effective meeting materials. It guides users through gathering context from Notion, selecting appropriate meeting templates, and enriching agendas with external research to ensure meetings are productive and well-informed.

What it does

  • Searches and fetches relevant project context, notes, and specs from Notion.
  • Provides a selection guide to choose the optimal meeting format.
  • Drafts agendas and pre-reads using standardized templates.
  • Enriches meeting materials with external industry insights and benchmarks.
  • Creates and updates meeting pages directly within Notion.
  • Links action items and follow-ups to existing Notion databases.

When to use it

  • When preparing for recurring status updates or project planning sessions.
  • When you need to gather historical context for decision-making meetings.
  • When drafting pre-read materials for stakeholders.
  • When you want to ensure meetings have clear goals, timeboxes, and assigned owners.

Advantages

  • Reduces preparation time by centralizing information from Notion.
  • Ensures consistency across different meeting types via templates.
  • Improves meeting quality by incorporating external research and clear objectives.
  • Facilitates better follow-up by linking tasks directly to Notion.

Usage examples

“Prepare a project decision meeting agenda for next Tuesday regarding the new API integration.”
The agent will search Notion for relevant API specs, select a decision-meeting template, draft an agenda with timeboxes, and add relevant industry research on API security.
“Create a pre-read document for our upcoming sprint planning meeting.”
The agent will pull the latest OKRs and backlog items from Notion, format them into a sprint planning template, and create a new page in Notion for the team to review.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/jetbrains/notion-meeting-intelligence/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip notion-meeting-intelligence.zip -d .agents/skills

Documentation by OpenAI

Meeting Intelligence

Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex 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 Codex 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.

4) Enrich with research

  • Add concise Codex research where helpful: market/industry facts, benchmarks, risks, best practices.

  • Keep claims cited with source links; separate fact from opinion.

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.

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

Files

examples/sprint-planning.md

Example: Sprint Planning Meeting Prep

User Request: "Prepare for tomorrow's sprint planning meeting"

Workflow

1. Search for Context
Notion:notion-search
query: "sprint planning" + "product backlog"
teamspace_id: "engineering-team"

Found:

  • Last sprint retrospective

  • Product backlog (prioritized)

  • Current sprint progress

  • Team capacity notes

2. Fetch Details
Notion:notion-fetch (4 pages)

Key context:

  • Last Sprint: Completed 32/35 story points (91%)

  • Velocity: Consistent 30-35 points over last 3 sprints

  • Team: 5 engineers, 1 on vacation next sprint (80% capacity)

  • Top Backlog Items: User auth improvements, API performance, mobile responsive fixes

3. Query Current Sprint Tasks
Notion:notion-query-data-sources
query: "SELECT * FROM tasks WHERE Sprint = 'Sprint 24' AND Status != 'Done'"

3 tasks carrying over (technical debt items)

4. Create Pre-Read (Internal)
Notion:notion-create-pages
title: "Sprint 25 Planning - Pre-Read (Internal)"

Pre-read included:

  • Sprint 24 summary (velocity, what carried over)

  • Team capacity for Sprint 25

  • Top backlog candidates with story points

  • Technical dependencies

  • Risk items (auth changes need QA time)

5. Create Agenda
Notion:notion-create-pages  
title: "Sprint 25 Planning - Agenda"

Agenda:

  • Review Sprint 24 completion (5 min)

  • Discuss carryover items (5 min)

  • Review capacity (28 points available)

  • Select backlog items (30 min)

  • Identify dependencies & risks (10 min)

  • Confirm commitments (10 min)

6. Link Documents

Cross-linked pre-read and agenda, referenced last retro and backlog.

Output Summary

Internal Pre-Read: Team context, capacity, blockers External Agenda: Meeting structure, discussion topics Both saved to Notion and linked to project pages

Key Success Factors

  • Gathered sprint history for velocity trends

  • Calculated realistic capacity (account for PTO)

  • Identified carryover items upfront

  • Pre-read gave team context before meeting

  • Agenda kept meeting focused and timeboxed

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
OpenAI
Publisher
JetBrains (Official)
Distributed by
JetBrains
Source
JetBrains/skills · notion-meeting-intelligence · commit 3f53782
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by OpenAI or JetBrains.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download notion-meeting-intelligence.zip