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.
Savant verdict: Review advised
Security analysis or source-hub review identified patterns requiring attention.
Live evaluation
26overall
29quality
15compliance
23grounding
25actionability
44efficiency
Why this score may understate the skillThe live evaluation is a chat-only run: the model follows the skill's instructions but can't execute its scripts, call tools or reach the network.
- Expects tools, MCP servers, installs or network access that a chat-only run doesn't have.
- 5 reference files were too large to include in the run's context.
0 pass · 0 investigate · 3 fail across 3 cases. Independent evaluation accepted 3 of 24 model-drafted cases. Drafted and run by nvidia/nemotron-3-super-120b-a12b, validated and scored by jev-latest.
- Prepare for tomorrow's sprint planning meeting with the engineering team. We need to review last sprint's velocity, discuss carryover items, and select backlog items for Sprint 25. Attendees: Alex (PM), Sam (Eng Lead), Taylor, Jordan, Casey (Engineers). Duration: 90 minutes. Date/time: Tomorrow at 2:00 PM.positive case · fail
- Create a new project plan in Notion for the website redesign initiative, including milestones, resource allocation, and risk register.negative case · fail
- Draft a team-wide announcement about the new remote work policy and publish it in the company Notion wiki.negative case · fail
Security assessment
Risk score
38/100
Recommendation
CAUTION
Severity
MEDIUM
Savant decision
Review advised
The assessment recommends caution with a risk score of 20/100 or more; review its findings before use. Static security analysis completed.
4 patterns found
- Memory Poisoning: Clear statehigh · reference/brainstorming-template.md:16 · Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
- Memory Poisoning: Clear statehigh · reference/decision-meeting-template.md:29 · Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
- Memory Poisoning: Clear statehigh · reference/sprint-planning-template.md:15 · Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
- Excessive Agency: NOT LIMITED TOlow · LICENSE.txt:7 · Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
SKILL.md
--- name: notion-meeting-intelligence description: Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees. metadata: short-description: Prep meetings with Notion context and tailored agendas --- # Meeting Intelligence Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex research. ## Quick start 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. ## Workflow ### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up: 1. Add the Notion MCP: - `codex mcp add notion --url https://mcp.notion.com/mcp` 2. Enable remote MCP client: - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client` 3. 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. ### 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-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`).