notion-meeting-intelligence
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).
More from firecrawl/skills
firecrawl-build-scrape
Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.
19.2Kfirecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
19.1Kfirecrawl-build-interact
Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
19.1Kfirecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
19.1Kfirecrawl-build-map
Integrate Firecrawl `/map` into product code for URL discovery on a known site. Use when a feature needs to find pages before scraping or crawling, especially on large docs sites, blogs, or help centers where the exact target URLs are not known yet.
554firecrawl-build-crawl
Integrate Firecrawl `/crawl` into product code for bulk extraction across a site or site section. Use when a feature needs many related pages, such as documentation sets, help centers, or blogs, and page-by-page `/scrape` would be too manual.
554