
Notion Knowledge Capture
Skill把对话与笔记整理成结构化的 Notion 页面:团队 wiki、操作指南、决策记录与 FAQ,并链接相关页面。收录于 OpenAI 官方插件仓库(开发者标注为 Notion),需要连接 Notion MCP。
name: notion-knowledge-capture
description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
metadata:
short-description: Capture conversations into structured Notion pages
Knowledge Capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
Quick start
- Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
- Identify the right database/template in
reference/(team wiki, how-to, FAQ, decision log, learning, documentation). - Pull any prior context from Notion with
Notion:search→Notion:fetch(existing pages to update/link). - Draft the page with
Notion:notion-create-pagesusing the database’s schema; include summary, context, source links, and tags/owners. - Link from hub pages and related records; update status/owners with
Notion:notion-update-pageas the source evolves.
Tool-call guardrails
- Notion tool availability can vary by workspace. If a Notion MCP call returns
Tool <name> not found, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; useNotion:searchandNotion:fetchwhere sufficient. - Use one literal search query per
Notion:searchcall and includefilters: {}when no narrower filter is needed. If several query variants are useful, issue separate searches instead of writingoror+inside one query string. - Only pass Notion page, database, or data-source URLs/IDs to
Notion:fetch. Search can also surface external connected-source URLs; use those as context or citations, but do not feed them intofetch. - Create pages with an explicit
parentand apagesarray. For database-backed pages, fetch the database first and use the returnedcollection://...data source ID. - To edit existing page content, fetch the current page first, then use
Notion:notion-update-pagewithcommand: "update_content",properties: {}, and exactold_str/ full replacementnew_strpairs. For property-only edits, usecommand: "update_properties"withcontent_updates: []. The current deployed schema expects both top-level fields even when one is unused. Do not invent insertion-only commands.
Workflow
0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:
- Enable the bundled Notion app for this plugin or session.
- Complete the Notion auth flow if prompted.
- Start a new session if the tools still do not appear.
After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.
1) Define the capture
- Ask purpose, audience, freshness, and whether this is new or an update.
- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
2) Locate destination
- Pick the correct database using
reference/*-database.mdguides; confirm required properties (title, tags, owner, status, date, relations). - If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
3) Extract and structure
- Extract facts, decisions, actions, and rationale from the conversation.
- For decisions, record alternatives, rationale, and outcomes.
- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
- For FAQs, phrase as Q&A with concise answers and links to deeper docs.
4) Create/update in Notion
- Use
Notion:notion-create-pageswith the correctdata_source_id; set properties (title, tags, owner, status, dates, relations). - Use templates in
reference/to structure content (section headers, checklists). - If updating an existing page, fetch then edit via
Notion:notion-update-page.
5) Link and surface
- Add relations/backlinks to hub pages, related specs/docs, and teams.
- Add a short summary/changelog for future readers.
- If follow-up tasks exist, create tasks in the relevant database and link them.
References and examples
reference/— database schemas and templates (e.g.,team-wiki-database.md,how-to-guide-database.md,faq-database.md,decision-log-database.md,documentation-database.md,learning-database.md,database-best-practices.md).examples/— capture patterns in practice (e.g.,decision-capture.md,how-to-guide.md,conversation-to-faq.md).
相關資源

Notion Research Documentation
Skill在 Notion 工作区里检索多处页面并综合整理,按需求生成速览、研究摘要、方案对比或完整报告,附引用与来源链接后写回 Notion。收录于 OpenAI 官方插件仓库(开发者标注为 Notion),需要连接 Notion MCP。
openai/plugins8k
Notion Meeting Intelligence
Skill结合 Notion 里的历史笔记、需求与决策准备会议:按会议类型选模板,生成议程与预读材料并补充调研。收录于 OpenAI 官方插件仓库(开发者标注为 Notion),需要连接 Notion MCP。
openai/plugins7.9k
Notion
PluginOpenAI 官方 Codex 插件市场收录的 Notion 插件(开发者标注为 Notion):接入 Notion 连接器与托管 MCP,可搜索并更新工作区页面,内含需求转实现计划、调研成文、会议准备与知识沉淀四个技能。仅适用于 Codex,需授权 Notion 账号。
openai/plugins7.9k
Notion MCP Server
MCPNotion 官方的自托管 MCP:用集成令牌搜索、读写页面与数据源,可按 Markdown 读取和编辑页面。官方现主推托管版 Remote Notion MCP,本仓库不再积极维护。
makenotion/notion-mcp-server4.7k
Notion Plugin for Claude Code
PluginNotion 官方 Claude Code 插件:打包 Notion 托管 MCP 与四个 Cookbook 技能(知识沉淀、会议准备、调研成文、需求转实现),提供搜索、建页、查库、建任务等斜杠命令,OAuth 登录。
makenotion/claude-code-notion-plugin510
Enterprise Search
PluginAnthropic 官方知识工作插件:一次提问同时检索已接入的聊天、邮件、云盘文档、Wiki 与项目管理工具,汇总成带出处的答案,并能生成每日或每周动态摘要。预置 Slack、Notion、Atlassian、Asana 等 MCP 连接,需逐个授权。
anthropics/knowledge-work-plugins36.2k