# notion-knowledge-capture

Turns a chat discussion into a structured Notion page: pulls out decisions, insights and how-tos, formats them and files them where they belong.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 567 installs · ★ 499
- Author: makenotion
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/makenotion/claude-code-notion-plugin/tree/HEAD/skills/notion/knowledge-capture/SKILL.md
- Updated: 2026-01-22
- HTML: https://affpapa.org/en/nevibecode/skills/notion-knowledge-capture-2

## What it does

The skill reads the conversation and picks out what is worth keeping: definitions, decisions with their rationale, step-by-step procedures, question-and-answer pairs, examples. It then classifies the material — concept, how-to, decision record, FAQ, meeting summary — and lays it out in the structure that fits that type.

It runs on the Notion MCP server. First it looks for a suitable wiki page or database with `Notion:notion-search`, then writes the page with `Notion:notion-create-pages`. There is a separate step for making the result findable: add a link to the wiki index, set tags and status in the database, attach the page to its parent. Skip that step and the document sits orphaned in the workspace where nobody will run into it.

A connected Notion MCP server with access to your workspace is the prerequisite — without it the `notion-search` and `notion-create-pages` calls have nowhere to go. For databases with properties the skill leans on the schemas described in `reference/database-best-practices.md`, so it pays to have the database structure in place beforehand.

## Requirements
- Works with: Notion

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/claude-code-notion-plugin --skill notion-knowledge-capture -a claude-code
```
```bash
npx skills add makenotion/claude-code-notion-plugin --skill knowledge-capture -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/knowledge-capture/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/knowledge-capture/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/claude-code-notion-plugin --skill knowledge-capture -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/knowledge-capture/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/claude-code-notion-plugin --skill knowledge-capture -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/knowledge-capture/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install makenotion/claude-code-notion-plugin knowledge-capture
```

2. **Manually: put the files in place**
- File: `.github/skills/knowledge-capture/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/claude-code-notion-plugin --skill knowledge-capture -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/makenotion/claude-code-notion-plugin --path skills/notion/knowledge-capture
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/knowledge-capture/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add makenotion/claude-code-notion-plugin --skill knowledge-capture -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/makenotion/claude-code-notion-plugin/tree/HEAD/skills/notion/knowledge-capture/SKILL.md

## When to use it
- save a decision from a thread as its own page with rationale
- build an FAQ out of questions asked in chat
- write up a how-to from steps worked out in conversation
- log meeting outcomes into a decision database
- link a new page into the wiki index so people find it

## Example prompts
- save this discussion to Notion as a decision record
- turn our conversation into a how-to and drop it in the docs database
- format this as an FAQ page and link it from the wiki index

## Similar
- [notion-meeting-intelligence](https://affpapa.org/en/nevibecode/skills/notion-meeting-intelligence.md) — skill · 15 installs
- [notion-spec-to-implementation](https://affpapa.org/en/nevibecode/skills/notion-spec-to-implementation.md) — skill · 14 installs
- [notion-mcp](https://affpapa.org/en/nevibecode/skills/notion-mcp.md) — skill · 735 installs
- [notion-api](https://affpapa.org/en/nevibecode/skills/notion-api.md) — skill · 94900 installs
- [notion](https://affpapa.org/en/nevibecode/skills/notion.md) — skill · 5600 installs
- [notion-automation](https://affpapa.org/en/nevibecode/skills/notion-automation.md) — skill · 4800 installs

## Other versions with the same name
- [notion-knowledge-capture · openai](https://affpapa.org/en/nevibecode/skills/notion-knowledge-capture.md) — 16 installs

From the same set: [makenotion/claude-code-notion-plugin](https://affpapa.org/en/nevibecode/by/makenotion/claude-code-notion-plugin.md) — 5 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md