openai/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.
This is a copy. The original lives at comeonoliver/notion-meeting-intelligence.
npx skills add https://github.com/openai/skills --skill notion-meeting-intelligence
Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex research.
1) Confirm meeting goal, attendees, date/time, and decisions needed.
2) Gather context: search with Notion:notion-search, then fetch with Notion:notion-fetch (prior notes, specs, OKRs, decisions).
3) Pick the right template via reference/template-selection-guide.md (status, decision, planning, retro, 1:1, brainstorming).
4) Draft agenda/pre-read in Notion with Notion:notion-create-pages, embedding source links and owner/timeboxes.
5) Enrich with Codex research (industry insights, benchmarks, risks) and update the page with Notion:notion-update-page as plans change.
codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
Notion:notion-search), then fetch key pages (Notion:notion-fetch).reference/template-selection-guide.md to confirm.reference/ and adapt sections (context, goals, agenda, owner/time per item, decisions, risks, prep asks).Notion:notion-update-page when details change; keep a brief changelog if multiple edits.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).Take openai/notion-meeting-intelligence from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.