notion-knowledge-capture

Name: notion-knowledge-capture
Author: davila7

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 MCP client configuration if not already connected. Extracts facts, decisions, alternatives, and rationale from conversations; structures content with required properties like title, tags, owner, status, and dates before creation or update.

INSTALLATION

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

Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$2c

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