notion-meeting-intelligence
by makenotionnotion-meeting-intelligence prepares meetings by gathering context from Notion, adding Claude research, and creating an internal pre-read plus an external agenda. It is useful for decision meetings, status reviews, customer calls, and other Notion-heavy workflows where you need a practical notion-meeting-intelligence guide.
This skill scores 84/100, which means it is a solid listing candidate for users who need a repeatable Notion-backed meeting-prep workflow. The repository gives enough structure, examples, and evaluation cases for directory users to understand how to trigger it and what they will get: internal pre-reads plus external agendas. It is not fully polished because there is no install command and no supporting scripts/resources, but the workflow value is real and the install decision is clear.
- Strong workflow specificity: the SKILL.md gives a step-by-step meeting-prep process using Notion search, fetch, research enrichment, and page creation.
- Good triggerability and reuse: examples and evaluation files cover multiple meeting types, including decision meetings, status updates, sprint planning, customer meetings, and executive reviews.
- Operationally helpful output shape: it explicitly aims to produce both an internal pre-read and an external agenda, with guidance to distinguish Notion facts from Claude insights.
- No install command and no support files/scripts, so adopters must infer setup and tool availability from the prose and examples.
- Some placeholder markers appear in the repository, which suggests parts of the documentation may be incomplete even though the core workflow is substantive.
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-based research, and generating two outputs: an internal pre-read and an external agenda. It is best for people who need to turn scattered notes, project pages, and prior discussions into a meeting package that is actually usable.
Who it fits best
This skill is most useful for project leads, operators, PMs, founders, and anyone running decision meetings, status reviews, customer calls, sprint planning, or executive reviews in Notion-heavy workflows. If your main job is to show up with the right background, options, and asks already organized, notion-meeting-intelligence is a strong fit.
Why it is different
Unlike a generic prompt that only drafts an agenda, notion-meeting-intelligence is built around a full prep workflow: search Notion, fetch relevant pages, synthesize the facts, add research context, then publish separate docs for internal and external audiences. That separation matters when you need candid notes for the team but a clean agenda for participants.
How to Use notion-meeting-intelligence skill
Install and enable it
Use the skill manager command shown in the repo, then enable meeting-intelligence in your Claude workspace or agent setup. The practical notion-meeting-intelligence install step is not just loading text; it is making sure the agent can call the Notion tools used by the workflow.
Start with the right meeting brief
Give the skill a concise brief with the meeting title, purpose, attendees, related project, and what decision or outcome is expected. Strong inputs look like: “Prep tomorrow’s database migration decision meeting for engineering and product; need an internal pre-read with options and a customer-safe agenda.” Weak inputs like “help with a meeting” force guesswork and reduce the quality of Notion search.
Read these files first
For notion-meeting-intelligence usage, the highest-value files are SKILL.md, evaluations/decision-meeting-prep.json, evaluations/status-meeting-prep.json, and the examples in examples/. The reference/*.md templates are especially useful when you want to see how the skill changes format by meeting type instead of reinventing structure from scratch.
Use the intended workflow
A good notion-meeting-intelligence guide follows the repo’s sequence: search Notion for context, fetch the most relevant pages, identify the meeting goal, enrich with Claude research only where it adds decision quality, then create an internal pre-read and an external agenda. If the meeting involves tracked work, add task or database queries early so the prep includes current status, blockers, and real progress instead of stale page text.
notion-meeting-intelligence skill FAQ
Is this only for Notion-native teams?
Yes, it is most valuable when the team already keeps project context, notes, or task data in Notion. If your source of truth lives elsewhere, you can still use the skill, but the Notion search-and-fetch loop becomes less useful and you may need a different workflow.
What does it do better than a normal prompt?
A normal prompt can draft an agenda, but notion-meeting-intelligence is designed to assemble evidence first. That means the output is usually better for high-stakes meetings because it is grounded in current pages, linked sources, and the distinction between fetched facts and added research.
Is it beginner-friendly?
Yes, as long as you can describe the meeting in plain language and point the skill at the right Notion workspace. The main beginner mistake is skipping context: if you do not say what kind of meeting it is, who it is for, and what must be decided, the output will be broad instead of useful.
When should I not use it?
Do not use notion-meeting-intelligence when you only need a quick standalone agenda, when there is no useful Notion context to search, or when the meeting is so lightweight that a full pre-read would be overhead. It is optimized for preparation quality, not for replacing every meeting note task.
How to Improve notion-meeting-intelligence skill
Give it source material, not a vague topic
The biggest quality jump comes from better input selection. Tell the skill which project page, decision thread, or task database matters, and specify the meeting type; for example, “status review for Mobile App Redesign” is far more actionable than “project update.” This helps notion-meeting-intelligence find the right pages and avoid broad, noisy synthesis.
Separate facts, research, and asks
When you use notion-meeting-intelligence, aim for a pre-read that clearly labels what came from Notion, what came from Claude research, and what you need from the meeting. That separation improves trust and reduces confusion, especially in decision meetings where people need to see evidence, tradeoffs, and the recommendation side by side.
Tune the output for the meeting type
Use the meeting type to shape the artifact. For decision meetings, ask for options and pros/cons; for status meetings, ask for progress, blockers, and timeline risk; for customer meetings, ask for account context and likely objections. This is the fastest way to improve notion-meeting-intelligence usage without changing the skill itself.
Iterate after the first draft
If the first output is too general, feed back what is missing: “Add the latest blockers from the tasks database,” “remove internal-only language from the external agenda,” or “tighten the recommendation to one option with rationale.” The best notion-meeting-intelligence guide is iterative: refine the source list, then refine the meeting ask, then refine the audience split.