Update to Notion

{
  "name": "notion-knowledge-capture",
  "description": "Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.",
  "included_files": [
    {
      "relative_path": "LICENSE.txt",
      "size_in_bytes": 1057
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 327
    },
    {
      "relative_path": "assets/notion-small.svg",
      "size_in_bytes": 1561
    },
    {
      "relative_path": "assets/notion.png",
      "size_in_bytes": 8526
    },
    {
      "relative_path": "evaluations/README.md",
      "size_in_bytes": 3490
    },
    {
      "relative_path": "evaluations/conversation-to-wiki.json",
      "size_in_bytes": 2027
    },
    {
      "relative_path": "evaluations/decision-record.json",
      "size_in_bytes": 2191
    },
    {
      "relative_path": "examples/conversation-to-faq.md",
      "size_in_bytes": 16283
    },
    {
      "relative_path": "examples/decision-capture.md",
      "size_in_bytes": 3628
    },
    {
      "relative_path": "examples/how-to-guide.md",
      "size_in_bytes": 3201
    },
    {
      "relative_path": "reference/database-best-practices.md",
      "size_in_bytes": 2419
    },
    {
      "relative_path": "reference/decision-log-database.md",
      "size_in_bytes": 2032
    },
    {
      "relative_path": "reference/documentation-database.md",
      "size_in_bytes": 2343
    },
    {
      "relative_path": "reference/faq-database.md",
      "size_in_bytes": 2036
    },
    {
      "relative_path": "reference/how-to-guide-database.md",
      "size_in_bytes": 1236
    },
    {
      "relative_path": "reference/learning-database.md",
      "size_in_bytes": 1321
    },
    {
      "relative_path": "reference/team-wiki-database.md",
      "size_in_bytes": 926
    }
  ],
  "skill_md_contents": "---\nname: notion-knowledge-capture\ndescription: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.\nmetadata:\n  short-description: Capture conversations into structured Notion pages\n---\n\n# Knowledge Capture\n\nConvert conversations and notes into structured, linkable Notion pages for easy reuse.\n\n## Quick start\n1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.\n2) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation).\n3) Pull any prior context from Notion with `Notion:search` → `Notion:fetch` (existing pages to update/link).\n4) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners.\n5) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool <name> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. If several query variants are useful, issue separate searches instead of writing `or` or `+` inside one query string.\n- Only pass Notion page, database, or data-source URLs/IDs to `Notion:fetch`. Search can also surface external connected-source URLs; use those as context or citations, but do not feed them into `fetch`.\n- Create pages with an explicit `parent` and a `pages` array. For database-backed pages, fetch the database first and use the returned `collection://...` data source ID.\n- To edit existing page content, fetch the current page first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` / full replacement `new_str` pairs. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`. The current deployed schema expects both top-level fields even when one is unused. Do not invent insertion-only commands.\n\n## Workflow\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Define the capture\n- Ask purpose, audience, freshness, and whether this is new or an update.\n- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.\n\n### 2) Locate destination\n- Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).\n- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.\n\n### 3) Extract and structure\n- Extract facts, decisions, actions, and rationale from the conversation.\n- For decisions, record alternatives, rationale, and outcomes.\n- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.\n- For FAQs, phrase as Q&A with concise answers and links to deeper docs.\n\n### 4) Create/update in Notion\n- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).\n- Use templates in `reference/` to structure content (section headers, checklists).\n- If updating an existing page, fetch then edit via `Notion:notion-update-page`.\n\n### 5) Link and surface\n- Add relations/backlinks to hub pages, related specs/docs, and teams.\n- Add a short summary/changelog for future readers.\n- If follow-up tasks exist, create tasks in the relevant database and link them.\n\n## References and examples\n- `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`).\n- `examples/` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).\n"
}