knowledge-base

Standardize knowledge-base frontmatter and file paths with a shared Zod schema.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge-base contract standardizes the format for niche knowledge bases, ensuring consistent frontmatter, file-path conventions, and a shared Zod schema across adapters and agents.

Core Features & Use Cases

  • Normalized Markdown Frontmatter: Enforces schema_version, niche_slug, source_type, source_identifier, timestamps, engagement, hooks, quotes, tags, and provenance.
  • Unified File-Path Convention: Standardizes storage and retrieval of knowledge items under .evidence/knowledge/<niche-slug>/<source-type>/<YYYY-MM-DD>-<slug>.md.
  • Adapter Compatibility & Validation: Provides a canonical frontmatter schema (schema.ts) used by all adapters for validation and by agents for ingestion.

Quick Start

Create a knowledge item by writing a YAML frontmatter that includes the required fields and a body that follows the published contract.

Frequently Asked Questions about knowledge-base

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

FAQPage Schema
How do I standardize markdown frontmatter for a niche knowledge base?

Standardize markdown frontmatter by writing a YAML header that includes required fields like niche_slug, source_type, timestamps, and provenance, followed by a body adhering to the published schema contract.

What schema fields are required for validating markdown knowledge items?

Required schema fields for validating markdown knowledge items include schema_version, niche_slug, source_type, source_url, source_identifier, captured_at, published_at, engagement_signals, extracted_hooks, tags, provenance, and content_hash.

What is the standard file path convention for storing markdown knowledge items?

The standard file path convention for storing markdown knowledge items is .evidence/knowledge/<niche-slug>/<source-type>/<YYYY-MM-DD>-<slug>.md, ensuring consistent storage and retrieval across adapters.

Do I need a Zod schema to validate markdown frontmatter across adapters?

Yes, a canonical Zod schema (schema.ts) is used to validate markdown frontmatter across adapters and by agents for ingestion, ensuring consistent file layouts and schemas for niche knowledge bases.

Why does my markdown frontmatter validation fail when ingesting knowledge items?

Markdown frontmatter validation fails when ingesting knowledge items if the YAML header is missing required fields like schema_version, niche_slug, source_type, or content_hash, or if the body does not follow the defined schema.