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.zipInstalls 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.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
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
- Confirm meeting goal, attendees, date/time, and decisions needed.
- Gather context: search with
Notion:notion-search, then fetch withNotion: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-pageas 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 = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- 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.mdto 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-pagewhen 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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| notion-meeting-intelligence (this skill) | 6 | 6mo | No flags | Intermediate |
| gtd | 0 | 6mo | No flags | Intermediate |
| end-session | 0 | 5mo | Review | Beginner |
| standup | 0 | 1mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by openai
View all by openai →You might also like
gtd
Gerstep
Autonomous task execution from GTD.md items. Use when processing GTD tasks, call prep, outreach, or podcast preparation.
end-session
connorkitchings
Close a development session properly. Create session log, run health checks, update schedule, prepare handoff documentation.
standup
thrawn01
Reconstruct what you actually did over a time window from Claude session logs, GitHub, Linear, and daily notes; group it by Linear ticket; write a standup-ready markdown report to ~/Notes; and copy a Range.co-ready version to the clipboard. Use when the user says 'standup', '/standup', 'what did I d
team-collaboration-standup-notes
sickn33
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.