notion-meeting-intelligence
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
- License 许可
- MIT
- 最近更新
- 2026-07-25
- Stars
- ★ 0
- Forks
- 0
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 Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
02 资源文件 18
- 参考文档agents/openai.yaml327 B
- 资产文件assets/notion-small.svg15.4 KB
- 资产文件assets/notion.png8.3 KB
- 参考文档evaluations/decision-meeting-prep.json3.3 KB
- 参考文档evaluations/README.md3.9 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 Codex 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 Codex 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 Codex prompts for it.
- Restart Codex or the current 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 Codex 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
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
skill-audit
Pre-install security scanner for AI agent skills. 7.5% of 14,706 skills are malicious. Audit before you trust.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
bumblebee
Run Bumblebee supply-chain inventory and exposure scans on macOS/Linux to detect compromised packages, extensions, and MCP host configs.