Source profileQuality 61/100

openai/skills/skills/.curated/notion-knowledge-capture/SKILL.md

notion-knowledge-capture

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

Source repository stars
24,265
Declared platforms
0
Static risk flags
0
Last source update
2026-07-14
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Convert conversations and notes into structured, linkable Notion pages for easy reuse.

Best for

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/openai/skills --skill "skills/.curated/notion-knowledge-capture"
Safe inspection promptEditorial

Inspect the Agent Skill "notion-knowledge-capture" from https://github.com/openai/skills/blob/49f948faa9258a0c61caceaf225e179651397431/skills/.curated/notion-knowledge-capture/SKILL.md at commit 49f948faa9258a0c61caceaf225e179651397431. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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…

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

    Workflow

    1. Add the Notion MCP: - codex mcp add notion --url https://mcp.notion.com/mcp 2. Enable remote MCP client: - Set [features].rmcpclient = true in config.toml or run codex --enable rmcpclient 3. Log in with OAuth: - codex mcp login notion

    Add the Notion MCP:codex mcp add notion --url https://mcp.notion.com/mcpEnable remote MCP client:
  3. 03

    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].rmcpclient = true in config.toml or run codex --enable rmcpclient 3. Log in with OAuth: - codex mcp login notion

    Add the Notion MCP:codex mcp add notion --url https://mcp.notion.com/mcpEnable remote MCP client:
  4. 04

    1) Define the capture

    Ask purpose, audience, freshness, and whether this is new or an update.

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

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score61/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars24,265SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
openai/skills
Skill path
skills/.curated/notion-knowledge-capture/SKILL.md
Commit
49f948faa9258a0c61caceaf225e179651397431
License
Not declared
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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

Alternatives

Compare before choosing