agentsclimarketplace

Notion meeting intelligence

Skill ulpi-io/plugin-marketplace/plugins/openai/skills/notion-meeting-intelligence

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install
npx -y skills add ulpi-io/plugin-marketplace --skill notion-meeting-intelligence

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

3.3 KB, 755 tokens by cl100k_base, as published. Nobody here has run it

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

Gives 0 of the 12 instructions most note taking skills give in 755 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 35 of 686, across 11 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 files
  • read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
  • keep 0.5 inch minimum marginsin 30 of 686, across 7 files
  • use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
  • re-verify affected slides after every fixin 27 of 686, across 5 files
  • run content QA checks before declaring successin 26 of 686, across 3 files
  • Use Markdown links for external URLs onlyin 26 of 686, across 10 files
  • pick a bold topic specific color palettein 24 of 686, across 2 files
  • read editing guide before editing existing presentationsin 23 of 686, across 1 file
  • use one dominant color across all slidesin 23 of 686, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.