notion-knowledge-capture

davila7/claude-code-templates · updated Apr 8, 2026

$npx skills add https://github.com/davila7/claude-code-templates --skill notion-knowledge-capture
0 commentsdiscussion
summary

Capture conversations and decisions into structured, linkable Notion pages for documentation and knowledge reuse.

  • Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas.
  • Workflow includes search and fetch of existing Notion pages to avoid duplication and establish proper linking and relations.
  • Requires Notion MCP connection; includes setup steps for OAuth login and remote MC
skill.md

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-searchNotion: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).

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.643 reviews
  • Alexander Huang· Dec 24, 2024

    notion-knowledge-capture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Neel Jackson· Dec 24, 2024

    Registry listing for notion-knowledge-capture matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Arya Srinivasan· Nov 15, 2024

    notion-knowledge-capture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Luis Liu· Nov 15, 2024

    notion-knowledge-capture reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Nia Park· Oct 6, 2024

    Solid pick for teams standardizing on skills: notion-knowledge-capture is focused, and the summary matches what you get after install.

  • Mateo Lopez· Oct 6, 2024

    We added notion-knowledge-capture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Anika Bhatia· Sep 21, 2024

    notion-knowledge-capture reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Diego Chawla· Sep 17, 2024

    Keeps context tight: notion-knowledge-capture is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Alexander Choi· Sep 17, 2024

    We added notion-knowledge-capture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Arjun Liu· Sep 13, 2024

    I recommend notion-knowledge-capture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 43

1 / 5