openai/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.
npx skills add https://github.com/openai/skills --skill notion-knowledge-capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
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.
codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter 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.
reference/*-database.md guides; confirm required properties (title, tags, owner, status, date, relations).Notion:notion-create-pages with the correct data_source_id; set properties (title, tags, owner, status, dates, relations).reference/ to structure content (section headers, checklists).Notion:notion-update-page.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).Take openai/notion-knowledge-capture from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.