agentleFS
ailessonioailessonio/open-source-skills/skills/openai/notion-meeting-intelligence/SKILL.md

notion-meeting-intelligence

Skill0 starsChanged 2 months agoMITView on GitHub

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

16 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-deep-links, helium-mcp and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • MicrosoftSkill

    deploy-pipeline

    Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

    Also in 3 projects that use this

  • ArogyaReddySkill

    raffle-winner-picker

    Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.

    Also in 5 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add the Notion MCP:

    line 21
  2. Distinctive:

    After successful login, the user will have to restart codex.

    line 28
  3. Distinctive:

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

    line 31
  4. Very specific:

    Search Notion for relevant docs, past notes, specs, and action items (Notion:notion-search), then fetch key pages (Notion:notion-fetch).

    line 32
  5. Very specific:

    Use reference/template-selection-guide.md to confirm.

    line 42
  6. Very specific:

    Start from the chosen template in reference/ and adapt sections (context, goals, agenda, owner/time per item, decisions, risks, prep asks).

    line 45
  7. Distinctive:

    Add concise Codex research where helpful: market/industry facts, benchmarks, risks, best practices.

    line 50
  8. Distinctive:

    Keep claims cited with source links.

    line 51
  9. Distinctive:

    Add next steps and owners for follow-ups.

    line 54
  10. Distinctive:

    If tasks arise, create/link tasks in the relevant Notion database.

    line 55
  11. Very specific:

    Update the page via Notion:notion-update-page when details change.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.