AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 3.3w
Forks
3.9k

01 前言 Front Matter

name
notion-meeting-intelligence
metadata
{ "short-description": "Prep meetings with Notion context and tailored agendas" }
description
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

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

04 同仓库更多 Skills

davila7
davila7/claude-code-templates

wealthville-pool-scoring

Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

technical-debt-auditor

Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

readonly-sql-guard

Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.

数据分析师后端与接口Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

前端开发
★ 3.3w
davila7
davila7/claude-code-templates

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

测试与质量前端开发
★ 3.3w
davila7
davila7/claude-code-templates

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

内容创作者写作与文案Skill与智能体开发
★ 3.3w