| name | notion-knowledge-capture |
| description | 用于把对话、决策和笔记沉淀到 Notion。 |
| zh_description | 用于把对话、决策和笔记沉淀到 Notion。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | in-house |
| source_url | |
| tags | ["capture", "knowledge", "notion"] |
| created_at | 2026-03-04 |
| updated_at | 2026-03-20 |
| quality | 3 |
| complexity | intermediate |
| metadata | null |
| short-description | Capture conversations into structured Notion pages |
Knowledge Capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
When to Use
Use this skill when the user wants to:
- turn a chat, meeting note, or rough draft into a durable Notion page
- capture a decision, FAQ, how-to, or learning note in a reusable format
- update an existing wiki page instead of creating duplicate documentation
- connect new knowledge to existing hub pages, databases, or related records
Use a different skill when:
- the task is specifically meeting prep before the meeting starts → use
notion-meeting-intelligence
- the main job is research synthesis across many Notion pages → use
notion-research-documentation
- the main job is breaking a PRD/spec into implementation artifacts → use
notion-spec-to-implementation
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:notion-search → Notion:notion-fetch (existing pages to update/link).
- Draft the page with
Notion:notion-create-pages using 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-page as the source evolves.
Usage
Typical usage pattern:
search existing page/database
-> fetch target schema or page content
-> decide create vs update
-> write structured content
-> link related records
-> verify final page destination
Default output shape:
- short summary at the top
- structured sections instead of raw transcript dump
- source links or discussion references
- explicit owners/tags if the destination database supports them
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 = true in config.toml run