Notion Meeting Intelligence

Skills productivity 53 Scanned by NVIDIA SkillSpector

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

Install Command

npx claude-code-templates@latest --skill productivity/notion-meeting-intelligence

View on GitHub

claude-code — notion-meeting-intelligence

Scanned by NVIDIA SkillSpector

Automated static analysis (no LLM) · v2.12.0 · 2026-10-17

Partial analysis: some checks could not run on this component.

0 observations

scanner score 0/100

SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.

No observations.

Learn more about NVIDIA SkillSpector.

Content

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:notion-search, then fetch with Notion:notion-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-page as plans change.

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

Add the Notion MCP:
- codex mcp add notion --url https://mcp.notion.com/mcp
Enable remote MCP client:
- Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
Log in with OAuth:
- codex mcp login notion

After 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.

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:notion-search), then fetch key pages (Notion: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.md to 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.

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-page when 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).