Index of every page on this site: llms.txt
All skills
makenotion avatar

/knowledge-capture

@016c74f official
Run it yourself

Captures conversations and supplied notes as Notion wiki pages, how-to guides, FAQs, decision records, or retrospectives. Use when saving or updating durable knowledge from existing context; use research-documentation when new source discovery and synthesis is the main task.

  • 18 files
  • 50.2 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/makenotion/claude-code-notion-plugin/knowledge-capture

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencedocumentation-database.md

≈918 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 016c74f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for makenotion/claude-code-notion-plugin/knowledge-capture