Integrations

notion-knowledge-capture

Try it

Convert chats and notes into linked, structured Notion knowledge pages.

What it does

Turn conversations and notes into structured Notion pages for decisions, how-tos, FAQs, wiki entries, learnings, and documentation. It finds the appropriate database and existing context, applies the referenced schema or template, creates or updates the page, and adds summaries, metadata, source links, relations, and follow-up tasks where needed.

When to use it

  • Turning a project discussion into a decision log
  • Converting notes into a reusable how-to
  • Building an FAQ from recurring questions
  • Updating wiki documentation with new context

The skill document

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

Questions people ask

Can it update an existing Notion page instead of creating a new one?
Yes. It searches for prior context, fetches the existing page, and updates it while preserving the destination database’s schema.
What information does it capture for a decision or how-to?
Decision pages can include alternatives, rationale, and outcomes. How-tos and documentation can include steps, prerequisites, asset or code links, and edge cases.
How does it choose where the content belongs in Notion?
It uses the database guides in `reference/` to match the content type and confirm required properties. If several databases are suitable, it asks the user which one to use; otherwise, it uses the primary wiki or documentation database.

Related skills

Create and validate Slack-ready animated GIFs with PIL-based drawing, motion helpers, and size optimization.

by Anthropic180.3k stars

Create or update Codex skills with concise instructions, reusable resources, metadata, and validation.

by OpenAI28.0k stars

yeet

Official

Stage, commit, check, push, and open or update a GitHub PR in one explicit flow.

by OpenAI28.0k stars

Migrate selected Claude Code instructions, skills, hooks, agents, MCP servers, and config into validated Codex files.

by OpenAI28.0k stars

Escape the scarcity trap — diagnose bandwidth consumption and design protected slack to restore strategic capacity.

by deciqai1 installs2 stars

linear

Official

Read and manage Linear issues, projects, labels, comments, documents, cycles, and team workflows.

by OpenAI28.0k stars

More from OpenAI

Browse all skills

chatgpt-apps

Official

Plan, scaffold, refactor, and validate ChatGPT Apps SDK projects with an MCP server and widget UI.

by OpenAI28.0k stars

Build or update full-page Figma screens with linked design-system components, variables, and styles.

by OpenAI28.0k stars

Builds a code-aligned Figma design system through phased creation, validation, and user approval.

by OpenAI28.0k stars

figma-use

Official

Runs Figma Plugin API scripts with the required call parameters, API rules, IDs, and validation workflow.

by OpenAI28.0k stars

hatch-pet

Official

Create and validate a Codex-compatible animated pet atlas from concepts, brand cues, or reference art.

by OpenAI28.0k stars

imagegen

Official

Generate or edit raster assets, validate the result, and place selected files into the project workspace.

by OpenAI28.0k stars