AgentSkillsCN

documentation_database

从OpenAI导入技能:documentation_database

SKILL.md
--- frontmatter
description: Imported skill documentation_database from openai
name: documentation_database
signature: 727f6bb7a341e871ba8afe155f9b261fe6f5ecf7f5ca7a43db3ad646fee7244d
source: /a0/tmp/skills_research/openai/skills/.curated/notion-knowledge-capture/reference/documentation-database.md

General Documentation Database

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

Schema

PropertyTypeOptionsPurpose
Titletitle-Document name
TypeselectHow-To, Concept, Reference, FAQ, Decision, Post-MortemCategorize content type
CategoryselectEngineering, Product, Design, Operations, GeneralOrganize by department/topic
Tagsmulti_select-Additional categorization (languages, tools, topics)
StatusselectDraft, In Review, Final, DeprecatedTrack document lifecycle
Ownerpeople-Document maintainer
Createdcreated_time-Auto-populated creation date
Last Updatedlast_edited_time-Auto-populated last edit
Last Revieweddate-Manual review tracking

Usage

code
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:

javascript
{
  "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