Notion Knowledge Capture

davila7/claude-code-templates/cli-tool/components/skills/productivity/notion-knowledge-capture

作者 davila78da17d671b6f無授權條款32K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

AI 產生的概覽

把對話與筆記整理成結構化、可互相連結的 Notion 頁面,例如 wiki 條目、操作指南、決策記錄與常見問題。

功能
引導代理把一段對話或筆記沉澱到 Notion:先釐清用途與讀者,選擇合適的資料庫或範本,再擷取事實、決策與步驟,並依對應的 schema 與屬性草擬頁面。它也涵蓋把新頁面連結到中心頁與相關記錄,以及在來源變動時更新狀態或負責人。整個流程依賴 Notion MCP 工具完成搜尋、取得、建立與更新操作。
適用情境
當一段聊天、會議或筆記需要變成可重複使用的 Notion 頁面時使用,例如決策記錄、操作指南、常見問題、wiki 條目或文件頁面。也適合在來源素材變動後更新或關聯既有的 Notion 頁面。
執行需求
需要已連線的 Notion MCP 伺服器(notion-search、notion-fetch、notion-create-pages、notion-update-page)以及 OAuth 登入;設定說明涵蓋新增 MCP、啟用遠端 MCP 用戶端與登入。需要網路存取。不附帶指令碼,僅為說明文件。

Knowledge Capture

Convert conversations and notes into structured, linkable Notion pages for easy reuse.

Quick start

  1. Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
  2. Identify the right database/template in reference/ (team wiki, how-to, FAQ, decision log, learning, documentation).
  3. Pull any prior context from Notion with Notion:notion-search → Notion:notion-fetch (existing pages to update/link).
  4. Draft the page with Notion:notion-create-pages using the database's schema; include summary, context, source links, and tags/owners.
  5. Link from hub pages and related records; update status/owners with Notion:notion-update-page as the source evolves.

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) 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.md guides; 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-pages with the correct data_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).

來源與署名

來源:davila7/claude-code-templates位於cli-tool/components/skills/productivity/notion-knowledge-capture提交8da17d6

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架