NO

notion-meeting-intelligence

Automate meeting preparation by fetching Notion documentation and generating agendas and pre-reads enriched with research.

Install

mkdir -p .claude/skills/notion-meeting-intelligence && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/602" && unzip -o skill.zip -d .claude/skills/notion-meeting-intelligence && rm skill.zip

Installs to .claude/skills/notion-meeting-intelligence

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
159 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Synthesize Notion OKRs and specs into meeting notes
  • Draft structured agendas based on meeting types
  • Enrich meeting context with Codex research
  • Link action items directly to Notion pages

How it works

Queries Notion via MCP for historical project context and populates standardized templates using researched benchmarks.

Inputs & outputs

You give it
Meeting goal, attendees, and duration
You get back
Structured Notion page with agenda and research context

When to use notion-meeting-intelligence

  • Drafting pre-read documents
  • Creating meeting agendas
  • Synthesizing OKRs and past decisions
  • Preparing 1:1 talking points

About this skill

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

When not to use it

  • Informal syncs without project goals
  • Meetings lacking supporting documentation in Notion

Prerequisites

Notion MCP serverCodex access

Limitations

  • Dependent on Notion MCP uptime
  • Requires existing documentation to provide value
  • Template selection relies on user input accuracy

How it compares

It automates the discovery of existing organizational context instead of prompting the user for manual input.

Compared to similar skills

notion-meeting-intelligence side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
notion-meeting-intelligence (this skill)66moNo flagsIntermediate
gtd06moNo flagsIntermediate
end-session05moReviewBeginner
standup01moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

skill-installer

openai

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

29141

figma-implement-design

openai

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

2460

figma

openai

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

2266

gh-fix-ci

openai

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

1234

transcribe

openai

Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

1148

gh-address-comments

openai

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

1059

Search skills

Search the agent skills registry