AutoGineer
Generated banner for Notion Knowledge Capture
Generated logo for Notion Knowledge Capture

Notion Knowledge Capture

OpenAIOfficialCreated by Notion Labs, IncDistributed by OpenAI

  • Skill
  • Workflow
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

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

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach for capturing information from ongoing conversations and turning it into structured, linkable content within Notion. It guides the user through defining the content type, identifying the appropriate database, extracting key information, and creating or updating pages using standardized templates. The workflow ensures that knowledge is not lost in chat logs but is instead integrated into a team's wiki, decision logs, or documentation systems.

What it does

  • Defines the purpose and audience for captured information.
  • Identifies the correct Notion database and schema for the content type.
  • Extracts key facts, decisions, and rationale from conversations.
  • Creates or updates structured pages using predefined templates.
  • Links new content to existing hub pages and related records.
  • Handles initial setup and authentication for the Notion integration.

When to use it

  • When you need to turn a brainstorming session into a formal decision log.
  • When converting technical discussions into a reusable how-to guide.
  • When summarizing team chats into FAQ entries or wiki pages.
  • When documenting learnings or project notes for future reference.

Advantages

  • Ensures consistency across documentation through standardized templates.
  • Reduces information fragmentation by linking new content to existing hubs.
  • Provides a clear, repeatable process for knowledge management.
  • Facilitates better team collaboration by making information discoverable.

Usage examples

“Can you turn our recent discussion about the API migration into a decision log entry?”
The agent will extract the alternatives, rationale, and final decision from the chat and create a structured page in your Notion decision log database.
“Create a how-to guide for setting up the local environment based on our chat.”
The agent will identify the how-to database, structure the steps and prerequisites, and create a new page in Notion with the appropriate tags and links.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/openai/notion-knowledge-capture-lh2r/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip notion-knowledge-capture.zip -d .agents/skills

Documentation by Notion Labs, Inc

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

Files

evaluations/decision-record.json

{
  "name": "Create Decision Record",
  "skills": ["knowledge-capture"],
  "query": "Document our decision to use PostgreSQL instead of MongoDB for our new service",
  "context": "User has just explained the decision with rationale, options considered, and trade-offs",
  "expected_behavior": [
    "Recognizes this as a decision record (architectural decision) from conversation context",
    "Uses Decision structure: Context → Decision → Rationale → Options Considered (with Pros/Cons) → Consequences → Implementation",
    "Extracts from context: decision made, options considered (PostgreSQL vs MongoDB), rationale, trade-offs",
    "Creates document with proper structure including Date, Status (Accepted), and Deciders",
    "Includes both positive and negative consequences (trade-offs) in Consequences section",
    "Uses Notion:notion-search to check if decision log database exists",
    "If database exists, asks whether to add there or create standalone page",
    "If creating in database, fetches schema using Notion:notion-fetch and sets properties: Decision title, Date, Status, Domain (Architecture), Deciders, Impact",
    "Uses Notion:notion-create-pages with parent: { data_source_id } for database or { page_id } for parent page",
    "Applies proper Notion markdown formatting with sections",
    "Suggests linking from architecture docs or project pages"
  ],
  "success_criteria": [
    "Document follows Decision structure from SKILL.md content types",
    "All key sections present: Context, Decision, Rationale, Options Considered (with Pros/Cons for each), Consequences, Implementation",
    "Decision is clearly stated (PostgreSQL chosen over MongoDB)",
    "Options that were considered are documented with pros/cons structure",
    "Rationale explains why PostgreSQL was chosen based on conversation context",
    "Consequences include both positive (benefits) and negative (trade-offs)",
    "If in database, properties are set correctly from schema (Decision, Date, Status: Accepted, Domain: Architecture, Impact)",
    "Document is dated and has status 'Accepted'",
    "Uses correct tool names (Notion:notion-search, Notion:notion-fetch, Notion:notion-create-pages)"
  ]
}

Requirements and compatibility

Written for: OpenAI Codex

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Notion Labs, Inc
Publisher
OpenAI (Official)
Distributed by
OpenAI
Source
openai/skills · skills/.curated/notion-knowledge-capture · commit 49f948f
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Notion Labs, Inc or OpenAI.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download notion-knowledge-capture.zip