notion-knowledge-capture
Verifiedby davila7 · Updated Apr 16, 2026
Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
See It In Action
All done. Here's what's now in Notion for the ops review:
5 pages created/updated from the retro:
-
INC-2026-0412-001 — Warehouse Routing Outage (existing page, now populated with full timeline, impact, root cause, decisions summary, open questions, and all source links)
-
Decision: Add prod-scale load profiles to staging — Derek Wu, due Apr 19
-
Decision: Memory profiling in CI for route-optimizer — Priya Sharma, due Apr 26
-
Decision: Decouple carrier-api from route-optimizer releases — Carlos + Derek, RFC due May 3 (also references the prior INC-2026-0328 carrier-api coupling issue)
-
Runbook: Queue drain procedure for warehouse routing — Carlos Mendez, due Apr 16 (draft with prereqs and edge cases; steps section flagged for Carlos to fill in)
Each decision page has summary, context, action items with owners/dates, open questions, and cross-references back to the incident page. All source links (Slack, PRs, Grafana) are preserved.
One note: the Notion API version didn't allow me to create proper databases (Decision Log / Engineering Docs) via MCP, so the pages are organized as sub-pages under your workspace root. If you want them in structured databases later, you can create those DBs manually in Notion and I can move the content over.
External Tools
| Tool | Type |
|---|---|
| notion | mcp |
Permissions
| Scope | Description |
|---|---|
| network:outbound |
SKILL.md
Knowledge Capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
Quick start
- 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). - Draft the page with
Notion:notion-create-pagesusing the database's schema; include summary, context, source links, and tags/owners. - Link from hub pages and related records; update status/owners with
Notion:notion-update-pageas the source evolves.
Workflow
0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
- Add the Notion MCP:
codex mcp add notion --url https://mcp.notion.com/mcp
- Enable remote MCP client:
- Set
[features].rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- 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.mdguides; 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-pageswith the correctdata_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).
FAQ
What does notion-knowledge-capture do?
Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
When should I use notion-knowledge-capture?
Use it when you need a repeatable workflow that produces text report.
What does notion-knowledge-capture output?
In the evaluated run it produced text report.
How do I install or invoke notion-knowledge-capture?
npx skills add https://github.com/davila7/claude-code-templates --skill notion-knowledge-capture
Which agents does notion-knowledge-capture support?
Claude Code
What tools, channels, or permissions does notion-knowledge-capture need?
It uses notion; channels commonly include text; permissions include network:outbound.
Is notion-knowledge-capture safe to install?
Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.
How is notion-knowledge-capture different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does notion-knowledge-capture outperform not using a skill?
About notion-knowledge-capture
When to use notion-knowledge-capture
When you want to convert meeting notes or chat discussions into reusable Notion documentation. When you need to create or update decision logs, FAQs, how-to guides, or wiki entries in Notion. When existing Notion pages should be linked, enriched, or surfaced from new captured knowledge.
When notion-knowledge-capture is not the right choice
When the goal is only to draft content locally without creating or updating anything in Notion. When the target knowledge base is not stored in Notion.
What it produces
Produces text report.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill notion-knowledge-captureInvoke: Ask Claude Code to use notion-knowledge-capture for the task.