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://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

evaluations/status-meeting-prep.json

{
  "name": "Status Update Meeting Preparation",
  "skills": ["meeting-intelligence", "task-manager"],
  "query": "Prep for Friday's project status meeting on the Mobile App Redesign project. Create both an internal pre-read and an external agenda.",
  "expected_behavior": [
    "Step 1: Uses Notion:notion-search to find Mobile App Redesign project page",
    "Step 2: Fetches project page using Notion:notion-fetch to get current status and context",
    "Step 3: Uses Notion:notion-search to find tasks database",
    "Step 4: Queries task database using Notion:notion-query-data-sources for project tasks (WHERE Project = 'Mobile App Redesign')",
    "Step 5: Analyzes task data: calculates completion %, identifies completed work, in-progress items, and blockers",
    "Step 6: Enriches with Codex research - adds project management insights (velocity trends, risk patterns, common project pitfalls), suggests discussion frameworks if risks identified, provides context on timeline implications",
    "Step 7: Creates INTERNAL PRE-READ using Notion:notion-create-pages with title 'INTERNAL: Mobile App Redesign Status - Pre-Read - [Date]'",
    "Step 7a: Internal pre-read includes: Project overview, current status with metrics (from Notion/tasks), progress summary with specifics, context & insights (Codex research on project health patterns), honest assessment of challenges/risks, what we need from meeting",
    "Step 7b: Internal pre-read contains detailed metrics, blockers, and strategic considerations",
    "Step 8: Creates EXTERNAL AGENDA using Notion:notion-create-pages with title 'Meeting Agenda: Mobile App Redesign Status Update - [Date]'",
    "Step 8a: External agenda uses Status Update structure: Meeting Details → Objective → Agenda Items (timed) → Discussion Topics → Action Items",
    "Step 8b: External agenda is concise, professional, focuses on meeting flow (summary-level metrics only)",
    "Step 9: Links both documents together",
    "Both documents link to project page and task database using <mention-page> and <mention-database>"
  ],
  "success_criteria": [
    "TWO documents are created (internal pre-read + external agenda)",
    "Internal pre-read contains: Detailed metrics from task query, honest assessment of blockers/risks, Codex insights on project health patterns, strategic considerations",
    "Internal pre-read is marked 'INTERNAL' or 'For team only'",
    "External agenda is professional status update format with: Overall status, progress summary (high-level), upcoming work, discussion topics, action items section",
    "External agenda does NOT contain detailed risk analysis or internal strategic discussion (that's in pre-read)",
    "Progress metrics are accurate based on Notion:notion-query-data-sources results (e.g., X complete, Y in progress, Z blocked)",
    "Blockers identified from task query are included in internal pre-read with full context",
    "Codex enrichment adds value (project management insights, risk patterns, velocity analysis)",
    "Links to project page and task database using mention tags",
    "Documents are cross-linked for easy navigation",
    "Uses correct tool names (Notion:notion-search, Notion:notion-fetch, Notion:notion-query-data-sources, Notion:notion-create-pages for BOTH documents)"
  ]
}

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