Notion Knowledge Capture — Agent Skill by OpenAI

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

Download the skill as a ZIP:
https://autogineer.com/agent-skills/openai/notion-knowledge-capture-lh2r/download

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

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.

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 or run codex --enable rmcp_client
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

ATTRIBUTION.mdAdded by AutoGineer1017 B
LICENSE.txt1.0 KiB
SKILL.md3.2 KiB
agents/openai.yaml512 B
assets/notion-small.svg15.4 KiB
assets/notion.png8.3 KiB
evaluations/README.md3.4 KiB
evaluations/conversation-to-wiki.json2.0 KiB
evaluations/decision-record.json2.2 KiB
examples/conversation-to-faq.md15.9 KiB
examples/decision-capture.md3.5 KiB
examples/how-to-guide.md2.8 KiB
reference/database-best-practices.md2.8 KiB
reference/decision-log-database.md2.0 KiB
reference/documentation-database.md2.7 KiB
reference/faq-database.md2.0 KiB
reference/how-to-guide-database.md1.2 KiB
reference/learning-database.md1.3 KiB
reference/team-wiki-database.md927 B

reference/documentation-database.md

General Documentation Database

Purpose: Store all types of documentation in a searchable, organized database.

Schema

Property	Type	Options	Purpose
Title	title	-	Document name
Type	select	How-To, Concept, Reference, FAQ, Decision, Post-Mortem	Categorize content type
Category	select	Engineering, Product, Design, Operations, General	Organize by department/topic
Tags	multi_select	-	Additional categorization (languages, tools, topics)
Status	select	Draft, In Review, Final, Deprecated	Track document lifecycle
Owner	people	-	Document maintainer
Created	created_time	-	Auto-populated creation date
Last Updated	last_edited_time	-	Auto-populated last edit
Last Reviewed	date	-	Manual review tracking

Usage

Create pages with properties:
{
  "Title": "How to Deploy to Production",
  "Type": "How-To",
  "Category": "Engineering",
  "Tags": "deployment, production, DevOps",
  "Status": "Final",
  "Owner": [current_user],
  "Last Reviewed": "2025-10-01"
}

Views

By Type: Group by Type property By Category: Group by Category property
Recent Updates: Sort by Last Updated descending Needs Review: Filter where Last Reviewed > 90 days ago Draft Docs: Filter where Status = "Draft"

Creating This Database

Use Notion:notion-create-database:

{
  "parent": {"page_id": "wiki-page-id"},
  "title": [{"text": {"content": "Team Documentation"}}],
  "properties": {
    "Type": {
      "select": {
        "options": [
          {"name": "How-To", "color": "blue"},
          {"name": "Concept", "color": "green"},
          {"name": "Reference", "color": "gray"},
          {"name": "FAQ", "color": "yellow"}
        ]
      }
    },
    "Category": {
      "select": {
        "options": [
          {"name": "Engineering", "color": "red"},
          {"name": "Product", "color": "purple"},
          {"name": "Design", "color": "pink"}
        ]
      }
    },
    "Tags": {"multi_select": {"options": []}},
    "Owner": {"people": {}},
    "Status": {
      "select": {
        "options": [
          {"name": "Draft", "color": "gray"},
          {"name": "Final", "color": "green"},
          {"name": "Deprecated", "color": "red"}
        ]
      }
    }
  }
}

Best Practices

Start with this schema - most flexible for general documentation
Use relations to connect related docs
Create views for common use cases
Review properties quarterly - remove unused ones
Document the schema in database description
Train team on property usage and conventions

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.

Build MCP App
AnthropicOfficial
Build interactive UI widgets for MCP servers to render forms, pickers, and dashboards directly within the chat interface.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
MCP Integration
AnthropicOfficial
Comprehensive guide for integrating Model Context Protocol (MCP) servers into Claude Code plugins.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
Social Publishing
Seth Hobson· Community
Programmatically schedule and publish content across 13 social media platforms using the SocialClaw API.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Hermes Tweet
Seth Hobson· Community
Integrates X/Twitter research and action capabilities into the Hermes Agent framework with strict approval-gated security.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Paypal Integration
Seth Hobson· Community
A guide to integrating PayPal payment processing, including checkout flows, subscriptions, and IPN webhook handling.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Social Publishing Publisher
Seth Hobson· Community
An agent-driven social media publishing specialist for multi-platform campaign management via the SocialClaw API.
Automation and integrationsClaude Code
MITGitHub stars of the source repository42.3k

Download ZIP

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