This Skill focuses on preparation before a meeting. Supply its purpose, participants, duration and required decisions. It finds relevant notes, specifications and outstanding work in Notion, then organizes a status meeting, decision session, planning meeting or retrospective around the outcome you need.
Install and prepare
This guide covers the standalone Skill retained in openai/skills. That repository is deprecated and current examples have moved to openai/plugins; the instructions here describe the linked standalone version, not the latest plugin.
Enter this line in the Codex conversation, not a terminal. If the installed Skill does not appear, restart Codex.
$skill-installer notion-meeting-intelligence
- Local Codex with an available Notion MCP connection
- A Notion workspace authorized through OAuth
- Access and editing permission for the destination page or database
If no connection exists, add the following to ~/.codex/config.toml, then run codex mcp login notion in the terminal and complete OAuth. Current Notion documentation does not require the old Skill’s rmcp_client flag. Reuse an existing working connection instead of configuring it twice. [4]
[mcp_servers.notion]
url = "https://mcp.notion.com/mcp"
Try a first task
Replace the destination Notion links, then start with:
$notion-meeting-intelligence
Prepare Thursday’s 30-minute payment-redesign decision meeting for the product, backend and support leads. We need to choose which refund entry point to launch first. Context: [paste page URL]. Read the previous notes and open actions. Draft a pre-read, timed agenda and decision questions. Do not invent participants’ opinions. Preview the material here first.
Work through the task
-
Define the decision. Provide the time, participant roles, required outcome and topics outside this meeting’s scope.
-
Recover the context. Read previous notes, requirements and unfinished tasks. Separate recorded facts, opinions and gaps; link any external research separately.
-
Build the agenda. Choose a suitable format, assign time to each item and identify its owner or missing owner. Confirm the destination before writing the Notion page.
Spend meeting time on decisions, not reciting background
Include the meeting type, duration, participant roles and the decision that must be made, plus a link to previous notes or the project hub. For example: “Prepare next week’s release decision meeting. We must decide whether to ship on schedule. Read the last two minutes and open high-priority issues first, then prepare a 30-minute agenda and pre-read.” That lets the agent separate established facts, unresolved risks and questions requiring a live decision instead of filling a generic agenda template.
Each agenda item should have a purpose, timebox and expected outcome. If a named owner must supply data, mark that as pending rather than committing on their behalf. When Notion search returns similarly named projects, compare team and date before using the page. A resolved issue from an older project is not automatically resolved here.
Do a final pre-meeting check
Open the generated page and confirm that pre-read links work, the agenda fits the duration, and the decision questions can be answered from available material. Unsupported judgments should remain questions. The Skill prepares materials; it does not create a calendar invite, notify participants or secure their agreement to a decision.
Another case: an incident retrospective
An incident retrospective needs a different agenda from a release decision meeting. Ask: “Prepare a 45-minute retro from the previous incident notes and open actions. Separate the confirmed timeline and impact from questions we must decide about monitoring, on-call coverage and rollback. Do not turn an unverified root cause into fact or assign owners before the meeting.” Check that the agenda allows time for fact clarification, pre-read links point to original events and actions, and there is room to record decisions and owners afterward. If incident material is missing, make it a pre-meeting gap instead of fabricating a complete timeline.
Check the result
Expect a short background, pre-reading links, an agenda that fits the allotted time and explicit decision questions. Compare it with the attendee list: each role should have a reason to participate. Unsupported market claims should not blend into project facts.
Common blockers
The topic is too broad. Reduce it to a decision the meeting can finish. Move background reading or unrelated questions outside the agenda.
Old notes conflict. Preserve dates and competing conclusions, then ask the meeting to clarify what changed.
No destination was provided. Start with a conversation draft and choose the Notion location before creating pages.
Separate the internal pre-read from the external agenda
If a meeting has internal context and external guests, prepare two outputs. Keep open risks, internal debate, and owners in a team-only pre-read; put objectives, timing, discussion questions, and shareable material in the external agenda. Review each document against its audience and permissions before sending it.