Source profileQuality 60/100

openai/skills/skills/.curated/notion-meeting-intelligence/SKILL.md

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.

Source repository stars
24,265
Declared platforms
1
Static risk flags
0
Last source update
2026-07-14
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex research.

Best for

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexDeclaredSource recordInstall path and trigger
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/openai/skills --skill "skills/.curated/notion-meeting-intelligence"
Safe inspection promptEditorial

Inspect the Agent Skill "notion-meeting-intelligence" from https://github.com/openai/skills/blob/49f948faa9258a0c61caceaf225e179651397431/skills/.curated/notion-meeting-intelligence/SKILL.md at commit 49f948faa9258a0c61caceaf225e179651397431. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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, deci…

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

    Workflow

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

    Add the Notion MCP:codex mcp add notion --url https://mcp.notion.com/mcpEnable remote MCP client:
  3. 03

    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].rmcpclient = true in config.toml or run codex --enable rmcpclient 3. Log in with OAuth: - codex mcp login notion

    Add the Notion MCP:codex mcp add notion --url https://mcp.notion.com/mcpEnable remote MCP client:
  4. 04

    1) Gather inputs

    Ask for objective, desired outcomes/decisions, attendees, duration, date/time, and prior materials.

    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.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score60/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars24,265SourceRepository attention, not individual Skill quality
Compatibility1 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
openai/skills
Skill path
skills/.curated/notion-meeting-intelligence/SKILL.md
Commit
49f948faa9258a0c61caceaf225e179651397431
License
Not declared
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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

Alternatives

Compare before choosing

Computed 8882,073

nexu-io/open-design

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero cl

2026-07-281 platforms
Computed 85234,327

affaan-m/ECC

dmux-workflows

Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

2026-07-272 platforms
Computed 83234,327

affaan-m/ECC

dmux-workflows

Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

2026-07-272 platforms
Computed 8324,265

openai/skills

render-deploy

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

2026-07-143 platforms