notion-meeting-intelligence

Overview of notion-meeting-intelligence skill

What notion-meeting-intelligence does

The notion-meeting-intelligence skill prepares meetings by pulling context from Notion, adding Claude research where it helps, and generating two distinct docs: an internal pre-read and an external agenda. It is built for the moment when you have a meeting coming up, but the background is scattered across pages, notes, and project docs.

Best-fit use cases

Use this skill when the meeting needs real preparation: decision reviews, customer calls, executive updates, sprint planning, retros, or any meeting where participants need a shared view of context. It is especially useful for notion-meeting-intelligence for Meeting Prep when you want both the facts already in Notion and a synthesized recommendation or discussion structure.

Why it is different

Unlike a generic prompt, this skill is workflow-oriented: it expects you to search Notion, fetch the most relevant pages, and then turn that material into meeting-ready outputs. The main value is not just summary; it is separating internal background from participant-facing agenda so you can control what is shared and what stays private.

How to Use notion-meeting-intelligence skill

Install and find the workflow

Install the skill with npx skills add makenotion/claude-code-notion-plugin --skill notion-meeting-intelligence. Then read skills/notion/meeting-intelligence/SKILL.md first, followed by evaluations/README.md, evaluations/decision-meeting-prep.json, evaluations/status-meeting-prep.json, and the examples in examples/. Those files show the intended output shape and the meeting types the skill handles best.

Give it a complete meeting brief

The skill works better when your request includes the meeting purpose, date, attendees, meeting type, and related project or decision. A weak request is: “Prep for a meeting.” A stronger notion-meeting-intelligence usage request is: “Prep for Friday’s database migration decision meeting with engineering and ops; create an internal pre-read and a 30-minute external agenda; focus on options, risks, and recommendation.”

Follow the expected workflow

The practical flow is: search Notion for relevant context, fetch the best pages, enrich with Claude research only where needed, then create two pages in Notion. The internal pre-read should capture background, current status, tradeoffs, and what you need from the meeting. The external agenda should be concise, time-boxed, and safe to share with all participants.

Read these files first

If you want to adapt the notion-meeting-intelligence guide to your workspace, start with the examples and reference templates: examples/customer-meeting.md, examples/project-decision.md, examples/executive-review.md, and reference/template-selection-guide.md. These show how to choose the right meeting template, which is often the difference between useful output and generic notes.

notion-meeting-intelligence skill FAQ

Is this only for Notion-heavy teams?

Yes, it is most valuable when Notion already holds the source material: project pages, meeting notes, specs, metrics, or customer context. If your meeting context lives elsewhere, the skill can still help, but the install is less compelling because the workflow depends on finding and reading Notion pages first.

Do I need Claude research every time?

No. The skill uses Claude research as enrichment, not as a replacement for your workspace facts. For a routine status meeting, Notion data may be enough. For a decision meeting, notion-meeting-intelligence is stronger when it adds external frameworks, benchmarks, or best practices to help compare options.

Is it beginner-friendly?

Yes, if you can describe the meeting clearly. You do not need to design the workflow yourself; you need to provide enough context for the skill to choose sources and shape the deliverables. The main beginner mistake is under-specifying the meeting goal, which leads to broad or unfocused prep.

When should I not use it?

Do not use it for meetings that need no prep, where there is no useful Notion context, or when the output is meant to be a quick note rather than a structured pre-read and agenda. It is also a poor fit if you want a single polished summary without the added step of creating meeting docs in Notion.

How to Improve notion-meeting-intelligence skill

Start with the decision or outcome

The best notion-meeting-intelligence skill runs begin with a concrete outcome: decide, align, review, plan, or unblock. If you say what the meeting must produce, the skill can prioritize the right pages and avoid overloading the pre-read with background that does not change the decision.

Feed it better source targets

Stronger input names the project, customer, team, initiative, or exact topic, plus any known related pages. For example, “Mobile App Redesign status meeting” is better than “product sync.” That specificity helps the skill search narrower Notion context and reduces the chance of grabbing irrelevant pages.

Use the right split between internal and external

Improve output quality by stating what should stay internal and what can be shared externally. This matters most for customer or executive meetings. The skill is designed to create both docs, so clear boundaries help it avoid exposing internal debate in the agenda or making the pre-read too generic.

Iterate on the first draft

If the first pass is too shallow, ask for a second pass that tightens the recommendation, adds stronger options analysis, or shortens the agenda to a specific time budget. For notion-meeting-intelligence install users, the fastest improvement is usually better source selection plus one sharper follow-up prompt, not a larger prompt.