AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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.

Original source
openai
License
MIT
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--notion-knowledge-capture at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

reference/documentation-database.md

General Documentation Database

Purpose: Store all types of documentation in a searchable, organized database.

Schema

| Property | Type | Options | Purpose | |----------|------|---------|---------| | Title | title | - | Document name | | Type | select | How-To, Concept, Reference, FAQ, Decision, Post-Mortem | Categorize content type | | Category | select | Engineering, Product, Design, Operations, General | Organize by department/topic | | Tags | multi_select | - | Additional categorization (languages, tools, topics) | | Status | select | Draft, In Review, Final, Deprecated | Track document lifecycle | | Owner | people | - | Document maintainer | | Created | created_time | - | Auto-populated creation date | | Last Updated | last_edited_time | - | Auto-populated last edit | | Last Reviewed | date | - | Manual review tracking |

Usage

Create pages with properties:
{
  "Title": "How to Deploy to Production",
  "Type": "How-To",
  "Category": "Engineering",
  "Tags": "deployment, production, DevOps",
  "Status": "Final",
  "Owner": [current_user],
  "Last Reviewed": "2025-10-01"
}

Views

By Type: Group by Type property By Category: Group by Category property
Recent Updates: Sort by Last Updated descending Needs Review: Filter where Last Reviewed > 90 days ago Draft Docs: Filter where Status = "Draft"

Creating This Database

Use Notion:notion-create-database:

{
  "parent": {"page_id": "wiki-page-id"},
  "title": [{"text": {"content": "Team Documentation"}}],
  "properties": {
    "Type": {
      "select": {
        "options": [
          {"name": "How-To", "color": "blue"},
          {"name": "Concept", "color": "green"},
          {"name": "Reference", "color": "gray"},
          {"name": "FAQ", "color": "yellow"}
        ]
      }
    },
    "Category": {
      "select": {
        "options": [
          {"name": "Engineering", "color": "red"},
          {"name": "Product", "color": "purple"},
          {"name": "Design", "color": "pink"}
        ]
      }
    },
    "Tags": {"multi_select": {"options": []}},
    "Owner": {"people": {}},
    "Status": {
      "select": {
        "options": [
          {"name": "Draft", "color": "gray"},
          {"name": "Final", "color": "green"},
          {"name": "Deprecated", "color": "red"}
        ]
      }
    }
  }
}

Best Practices

  1. Start with this schema - most flexible for general documentation
  2. Use relations to connect related docs
  3. Create views for common use cases
  4. Review properties quarterly - remove unused ones
  5. Document the schema in database description
  6. Train team on property usage and conventions