notion-meeting-intelligence
Prepare meeting materials with Notion context and supplemental research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 37
- Forks
- 1
01 前言 Front Matter
- name
- notion-meeting-intelligence
- metadata
- { "short-description": "Prep meetings with Notion context and tailored agendas" }
- description
- Prepare meeting materials with Notion context and supplemental research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
02 资源文件 18
- 参考文档agents/openai.yaml327 B
- 资产文件assets/notion-small.svg1.5 KB
- 资产文件assets/notion.png8.3 KB
- 参考文档evaluations/decision-meeting-prep.json3.4 KB
- 参考文档evaluations/README.md4.0 KB
- 参考文档evaluations/status-meeting-prep.json3.2 KB
- 参考文档examples/customer-meeting.md3.2 KB
- 参考文档examples/executive-review.md2.4 KB
- 参考文档examples/project-decision.md12.5 KB
- 参考文档examples/sprint-planning.md2.5 KB
- 许可证LICENSE.txt1.0 KB
- 参考文档reference/brainstorming-template.md1.4 KB
- 参考文档reference/decision-meeting-template.md1.8 KB
- 参考文档reference/one-on-one-template.md931 B
- 参考文档reference/retrospective-template.md939 B
- 参考文档reference/sprint-planning-template.md1.3 KB
- 参考文档reference/status-update-template.md1.3 KB
- 参考文档reference/template-selection-guide.md1.9 KB
03 SKILL.md 正文
Meeting Intelligence
Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with supplemental research.
Quick start
- Confirm meeting goal, attendees, date/time, and decisions needed.
- Gather context: search with
Notion:search, then fetch withNotion:fetch(prior notes, specs, OKRs, decisions). - Pick the right template via
reference/template-selection-guide.md(status, decision, planning, retro, 1:1, brainstorming). - Draft agenda/pre-read in Notion with
Notion:notion-create-pages, embedding source links and owner/timeboxes. - Enrich with supplemental research (industry insights, benchmarks, risks) and update the page with
Notion:notion-update-pageas plans change.
Tool-call guardrails
- Notion tool availability can vary by workspace. If a Notion MCP call returns
Tool <name> not found, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; useNotion:searchandNotion:fetchwhere sufficient. - Use one literal search query per
Notion:searchcall and includefilters: {}when no narrower filter is needed. - Only fetch Notion page, database, or data-source URLs/IDs; external connected-source search results are not valid
Notion:fetchinputs. - Create meeting pages with an explicit
parentand apagesarray. - Query databases with
Notion:notion-query-data-sourcesunder a top-leveldataobject, using fetchedcollection://...URLs as table names. - When editing a page, fetch its current content first and use
Notion:notion-update-pagewith supported commands such asupdate_contentorupdate_properties; on the current deployed surface, useproperties: {}forupdate_contentandcontent_updates: []forupdate_properties. Do not invent insertion-only commands.
Workflow
0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:
- Enable the bundled Notion app for this plugin or session.
- Complete the Notion auth flow if prompted.
- Start a new session if the tools still do not appear.
After the app is connected, finish your answer and tell the user to retry so 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:search), then fetch key pages (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.mdto 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 supplemental 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-pagewhen 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).
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建(通过 CLI 或手动方式)、SDK 安装(Python 或 TypeScript)、任务模式(重试、子任务、扇出)、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。
render-web-services
配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署,或排查端口绑定问题时使用。
render-static-sites
在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React/Vue/Hugo/Gatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header,或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。