notion-meeting-intelligence
by openainotion-meeting-intelligence helps turn Notion context into meeting-ready agendas and pre-reads, with Codex research for decisions, status, planning, retros, and 1:1 prep. Best for the notion-meeting-intelligence for Meeting Prep workflow when you need grounded materials, clear timeboxes, and attendee-specific outputs.
This skill scores 84/100, which means it is a solid directory listing for users who need Notion-backed meeting prep. The repository gives enough workflow detail to install with confidence: it clearly explains when to use the skill, how to gather context, and how to produce agendas and pre-reads with Notion plus Codex research.
- Explicit trigger and purpose: prep meetings using Notion context and tailored agendas/pre-reads.
- Operational workflow is concrete: search, fetch, select a template, create/update pages, and enrich with Codex research.
- Good install-decision evidence: examples, reference templates, and evaluation scenarios show real meeting-prep use cases.
- Depends on a connected Notion MCP server, so it is not self-contained.
- The skill is specialized to meeting intelligence; it is less useful if the user does not manage meeting materials in Notion.
Overview of notion-meeting-intelligence skill
notion-meeting-intelligence helps you turn scattered Notion context into meeting-ready prep: a clear agenda, a useful pre-read, and supporting research where needed. It is best for people who already keep project, customer, or decision notes in Notion and need the notion-meeting-intelligence skill to assemble them into something attendees can actually use.
Use it when the real job is meeting preparation, not generic summarization. The skill is strongest for the notion-meeting-intelligence for Meeting Prep workflow: finding prior notes, pulling relevant pages, shaping the meeting around decisions or status, and tailoring the output to the audience. It is less useful if you do not have Notion content to ground the work.
What the skill is best for
The notion-meeting-intelligence skill is designed for meetings where context matters more than a blank agenda:
- decision meetings with background tradeoffs
- status meetings that need current project facts
- customer or stakeholder meetings that need tailoring
- planning sessions, retros, and 1:1s with existing notes
What makes it different
Unlike a one-shot prompt, this skill expects a workflow: search Notion, fetch relevant pages, choose the right meeting template, then write the meeting asset with sources and timeboxes. That structure reduces guesswork and helps the output stay tied to real workspace context.
When it is a poor fit
If you want a generic meeting agenda with no workspace context, a normal prompt is enough. If your notes live outside Notion, the skill will feel constrained until you move or mirror the source material into Notion first.
How to Use notion-meeting-intelligence skill
Install and connect Notion MCP
Install the notion-meeting-intelligence install path with the OpenAI skills command shown in the repo, then make sure the Notion MCP connection is available before asking for prep. The skill depends on the Notion MCP tool, so missing authentication is the most common blocker.
If the connection fails, the repo’s workflow says to set up the Notion MCP, enable the remote MCP client, and log in with OAuth before retrying. That matters because the skill is built around live Notion search, fetch, create, and update actions.
Start from the meeting outcome
A strong notion-meeting-intelligence usage request should name the meeting outcome, not just the topic. Include:
- meeting type: decision, status, planning, retro, 1:1, brainstorming
- date/time and audience
- what must be decided, reviewed, or approved
- any Notion spaces, projects, or note names to search
Example request shape: “Prepare a decision meeting for the database migration. Find prior Notion context, draft an internal pre-read, and create an external agenda with decisions needed and open questions.”
Read the right files first
For practical install decisions, start with SKILL.md, then check reference/template-selection-guide.md and the relevant template under reference/. Use the examples in examples/ to see how the skill expresses internal pre-reads versus external agendas.
Good first reads:
SKILL.mdreference/template-selection-guide.mdreference/decision-meeting-template.mdreference/status-update-template.mdexamples/project-decision.md
Workflow that improves output
The most effective notion-meeting-intelligence guide pattern is:
- search Notion for the topic and related decisions
- fetch 2–3 relevant pages, not just the top result
- identify the meeting objective and missing decision points
- draft the agenda or pre-read using the matching template
- enrich only where Codex research adds value, such as benchmarks, risk framing, or best practices
- update the page if the plan changes
notion-meeting-intelligence skill FAQ
Does this replace a custom prompt?
No. A custom prompt can draft a meeting agenda, but notion-meeting-intelligence adds a repeatable retrieval workflow: it finds source pages, uses the right template, and keeps the output anchored to Notion context instead of invented background.
Do I need to be an expert in Notion MCP?
Not really. Beginner users can succeed if they provide a clear meeting goal and let the skill do the search/fetch work. The main requirement is that Notion MCP is connected and the relevant content actually exists in the workspace.
When should I not use it?
Skip it if:
- the meeting has no meaningful Notion history
- the answer should come from external documents or a CRM instead
- you only need a short checklist, not a pre-read or agenda
- you cannot connect the Notion MCP tool
Is it only for internal meetings?
No. It works for customer and stakeholder prep too, but the output should be adapted to the audience. Internal pre-reads can include deeper analysis; external agendas should be cleaner and avoid exposing internal-only reasoning.
How to Improve notion-meeting-intelligence skill
Give the skill sharper inputs
The biggest quality lever is specificity. A weak request is “prep my meeting.” A stronger one is: “Prepare a decision meeting for the database migration next Tuesday. Pull prior specs, compare the two options already discussed, and create an internal pre-read plus a 30-minute external agenda.”
Include the names of projects, pages, or terms your workspace already uses. That makes notion-meeting-intelligence usage faster and reduces false matches in search.
Separate facts from analysis
The repo’s workflow supports both Notion facts and Codex research. Keep them distinct in your prompt and in the resulting page: use Notion for what your team already knows, and use research for frameworks, risks, benchmarks, or decision criteria. This prevents the skill from blending workspace evidence with outside advice.
Optimize for the meeting type
Use the matching template so the output matches the meeting’s purpose:
- status: progress, blockers, next steps
- decision: options, tradeoffs, recommendation
- planning: scope, dependencies, timing
- retro: what worked, what didn’t, actions
- 1:1: priorities, feedback, follow-ups
If the first draft feels generic, ask for a rewrite with a tighter audience, shorter agenda, or more explicit decisions needed.