knowledge-base-setup

Set up a Postgres knowledge-base layer with public and per-niche schemas.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/00PZ/oopz-inc --skill knowledge-base-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-base-setup
Source: https://github.com/00PZ/oopz-inc/tree/main/skills/knowledge-base-setup
Command: npx skills add https://github.com/00PZ/oopz-inc --skill knowledge-base-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a scalable, auditable knowledge-base layer in Postgres for a new oopz-inc brand, enabling consistent data modeling, schema governance, and a repeatable KB bootstrap.

Core Features & Use Cases

  • Public schema with cross-cutting tables for migrations and niches, plus per-niche schemas for knowledge items.
  • Adapter contract, Markdown projection convention, and add-a-niche workflow to support scalable KB growth.
  • Works standalone or as Phase 2 of the company-creator workflow to bootstrap KBs in new packages.

Quick Start

Run the Phase-2 KB bootstrap by creating the public schema, provisioning the niche template, registering the niche, and configuring the markdown projection workflow.

Frequently Asked Questions about knowledge-base-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a Postgres knowledge-base for a new brand?

To bootstrap a Postgres knowledge-base, establish the database, create the public schema with cross-cutting tables, provision per-niche templates, and configure the markdown projection workflow.

What is the add-a-niche procedure for a Postgres schema?

The add-a-niche procedure provisions a per-niche schema template for knowledge items, registers the niche within the public schema, and applies the adapter contract to maintain scalable KB growth.

Can I use this knowledge-base setup standalone or do I need the company-creator workflow?

You can use this knowledge-base setup entirely standalone to add knowledge capabilities to an existing package, or run it as Phase 2 of the company-creator workflow for fresh brands.

What schema structure is needed for scalable knowledge-base management in Postgres?

Scalable knowledge-base management requires a public schema for migrations and niches, alongside separate per-niche schemas for knowledge items, governed by an adapter contract and markdown projection convention.

How does the markdown projection convention work with the adapter contract?

The markdown projection convention defines how knowledge items stored in per-niche schemas are rendered, while the adapter contract specifies the data interface, ensuring consistent and auditable KB schema governance.