playbooks

home / skills / openai / skills / notion-knowledge-capture

notion-knowledge-capture skill

/skills/.curated/notion-knowledge-capture

This skill captures conversations and decisions into structured Notion pages, turning chats into wiki entries, how-tos, and FAQs for easy reuse.

npx playbooks add skill openai/skills --skill notion-knowledge-capture

Review the files below or copy the command above to add this skill to your agents.

Files (18)
SKILL.md
3.2 KB
---
name: notion-knowledge-capture
description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
metadata:
  short-description: Capture conversations into structured Notion pages
---

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

Overview

This skill converts conversations, notes, and meeting outcomes into structured, linkable Notion pages for team knowledge reuse. It helps turn chats into decisions, how-tos, FAQs, wiki entries, or documentation with correct schema, links, and owners. Use it to maintain a discoverable, up-to-date knowledge base.

How this skill works

Start by clarifying the capture purpose and audience, then select the appropriate Notion database or template from the reference set. The skill extracts facts, decisions, action items, and rationale from the source content, structures them to match the target schema, and creates or updates pages via Notion APIs. It adds properties (title, tags, owner, status, dates), backlinks to hubs, and related tasks so information is discoverable and actionable.

When to use it

  • After meetings to record decisions and action items
  • When turning a conversation or chat thread into a wiki or how-to guide
  • To create concise FAQs from recurring support or product questions
  • When documenting design rationale, alternatives, and outcomes
  • To keep documentation synchronized with evolving discussions

Best practices

  • Clarify capture intent and audience before drafting to choose the correct template
  • Search Notion first for related pages to update rather than creating duplicates
  • Include a short summary, source links, and a changelog entry on each page
  • Record alternatives and rationale for decisions to preserve context
  • Link pages to hub records and create follow-up tasks when actions are identified

Example use cases

  • Post-standup decision capture: store rationale, chosen option, and owners in the decision log
  • Customer support thread → FAQ: extract question/answer pairs and link to deeper docs
  • How-to creation: convert a troubleshooting thread into step-by-step instructions with prerequisites and edge cases
  • Onboarding docs: consolidate knowledge from multiple conversations into a team wiki page
  • Documentation update: fetch an existing page, apply edits, and add a short changelog entry

FAQ

What if the Notion connector is not configured?

Pause and configure the Notion MCP. Add the MCP, enable remote client, and log in with OAuth. After successful login restart the tool and continue the capture flow.

How do I choose the right database?

Check the reference templates (team wiki, how-to, FAQ, decision log, learning, documentation). If multiple match, ask the team which database should own the record; default to the primary wiki/documentation DB if unsure.