Imported from onurmicoogullari/agent-tools (OpenCode/skills/notion-knowledge-capture/SKILL.md). Install upstream with npx skills add onurmicoogullari/agent-tools --skill notion-knowledge-capture. Copyright stays with the author.

Knowledge Capture

Convert conversations and notes into structured, linkable Notion pages for easy reuse.

Tool names

Names such as Notion:notion-search below and in the references identify operations, not guaranteed callable tool names. Discover the Notion tools exposed in this session and follow their actual schemas.

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

Workflow

0) Check the Notion connection

Use an existing connected Notion integration first. If the tools are missing or authentication has expired, use the host’s connection flow. For a CLI-managed MCP connection:

1. Check the existing connection with opencode mcp list.
2. If no suitable Notion connection exists, merge "notion": {"type": "remote", "url": "https://mcp.notion.com/mcp", "enabled": true} into the active configuration’s mcp object. Preserve other settings.
3. Authenticate with opencode mcp auth notion and verify that Notion tools are available.

Let the user complete interactive authentication. Resume when tools are available; restart the session only if the host requires it. Treat other API errors according to the returned error instead of reconnecting automatically.

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