skilld
All skills
openai avatar

/notion-knowledge-capture

@136d58a official
by openaiopenai/skills28k stars
1,891

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/notion-knowledge-capture

This session only. Nothing lands on disk.

SKILL.md

≈47 tokens always: the name and description. ≈755 when used: this file. ≈11k more on demand in 14 files.

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

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill allows for the structured capture of conversations and notes into Notion pages. While it processes user-provided data, this is consistent with its intended documentation purpose. The skill follows established patterns for service integration.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    16/16 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 136d58a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 10 months ago

Capability

metadata
{
  "short-description": "Capture conversations into structured Notion pages"
}

Topics

README badge

README badge for openai/skills/notion-knowledge-capture

What it does

Captures conversations and notes into structured Notion pages for team wikis, how-tos, decision logs, and FAQs. Uses Notion MCP to fetch context, create pages with proper schemas, and link related records across databases.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with any Notion workspace, or do I need specific setup?
You need to connect the Notion MCP (Codex integration) first using OAuth. The skill includes setup instructions; if the MCP is not connected, it will pause and guide you through `codex mcp add notion` and login.
What types of content can I capture with this skill?
The skill supports decisions, how-to guides, FAQs, wiki/concept entries, learning notes, and documentation pages. It provides templates and schemas for each type in the `reference/` directory.
Can I update an existing Notion page or does this only create new ones?
You can do both. The skill can search and fetch existing pages with `Notion:notion-search` and `Notion:notion-fetch`, then update them via `Notion:notion-update-page` if you're revising prior content.
How does this skill handle linking and cross-references?
After creating or updating a page, the skill adds relations and backlinks to hub pages, related specs, and team records, then updates status and owner fields as the source evolves.
Do I need to know the Notion database schema beforehand?
No. The skill includes reference guides for each database type (team wiki, how-to, FAQ, decision log, etc.) that show required properties like title, tags, owner, and status.

Generated from the current SKILL.md. These answers refresh after source changes.