okf-knowledge-base

Guides authoring and maintenance of Open Knowledge Format bundles with frontmatter, links, and provenance.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/jcafeitosa/anxionOS --skill okf-knowledge-base-jcafeitosa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okf-knowledge-base
Source: https://github.com/jcafeitosa/anxionOS/tree/main/.cursor/skills/okf-knowledge-base
Command: npx skills add https://github.com/jcafeitosa/anxionOS --skill okf-knowledge-base-jcafeitosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining agent-readable knowledge bases struggle to keep Markdown bundles conformant with the Open Knowledge Format (OKF) v0.2 spec, including correct frontmatter types, reserved index and log files, provenance fields, and portable links. ## Core Features & Use Cases - OKF Authoring Rules: Enforces core bundle rules such as one concept per file, required type frontmatter, lowercase filenames, and reserved index.md and log.md conventions. - Provenance and Trust Guidance: Explains how to record sources, generated, verified, and ISO 8601 timestamps without inventing facts or history. - Plugin Integration: Describes how to respond to OpenKnowledge okf plugin warnings, read generated .ok/okf/*.schema.json contracts, and respect machine-owned generated indexes. - Use Case: When an agent flags a broken link or missing frontmatter in your knowledge bundle, use this Skill to decide the correct type, fix the metadata, and append a truthful dated log.md entry. ## Quick Start Ask the agent to review your OKF bundle for conformance and fix any frontmatter, link, or log issues it finds.

Frequently Asked Questions about okf-knowledge-base

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

FAQPage Schema
How do I create an OKF knowledge bundle?▼

Create a directory tree of lowercase .md files where each non-reserved file is one concept with parseable frontmatter containing a non-empty string type. Add an index.md at each level and optionally a log.md with newest-first dated entries.

What frontmatter fields are required in Open Knowledge Format?▼

Only a non-empty string type field is strictly required for every concept. Fields like title, description, tags, sources, generated, and verified are optional and should be used only when they add real, truthful information.

How do I respond to okf plugin warnings in OpenKnowledge?▼

Read the generated schema contracts in .ok/okf/*.schema.json to understand the exact field requirements, then fix the reported structure, frontmatter, link, or .mdx issues. Never edit the generated schema files or machine-owned generated indexes.

Does OKF support .mdx files in knowledge bundles?▼

No, OKF consumers read only .md files, not .mdx. The okf plugin flags .mdx usage as a conformance warning, so convert content to standard Markdown for portability.

How should timestamps be formatted in OKF provenance fields?▼

Use ISO 8601 datetimes with an explicit UTC offset for generated.at, verified.at, stale_after, and sources.last_modified. The exception is log.md entry headings, which use a plain YYYY-MM-DD date.