# Notion Knowledge Capture

> Use when the user wants to turn chats, decisions, notes, or learnings into structured Notion pages; search existing context first, choose the right destination, then create or update pages with links, owners, and reusable structure.

- Skill: `hebertzhu/notion-knowledge-capture` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hebertzhu/notion-knowledge-capture`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hebertzhu/notion-knowledge-capture/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: hebertzhu (https://skillmd.com/u/hebertzhu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hebertzhu/notion-knowledge-capture

---


# Notion Knowledge Capture

## Intent
- Use for capturing conversations, decisions, FAQs, how-tos, wiki pages, and reusable internal knowledge in Notion.

## Default operating pattern
1. Clarify what is being captured, who the audience is, and whether this should create a new page or update an existing one.
2. Use the current host's Notion connector or MCP integration to search for existing related pages before creating duplicates.
3. Pick the right destination: wiki page, documentation database, decision log, FAQ collection, or learning archive.
4. Structure the content so future readers can reuse it quickly: summary, context, decisions, links, owners, and follow-up items.
5. Create or update the page, then link it back to the most relevant hub pages, specs, or tasks.

## Pack fit
- Included in: `knowledge-ops`
- Prefer durable, linkable knowledge over raw meeting notes or chat transcripts.

## Boundary
- Do not create duplicate documentation if an existing page only needs an update.
- Do not flatten nuanced decisions into a vague summary; preserve rationale and open questions.