- name
- okf-knowledge-base
- description
- Open Knowledge Format (OKF) v0.2 guidance. Use when creating, reading, reviewing, or maintaining an OKF bundle; responding to OpenKnowledge `okf` plugin warnings; or choosing types, provenance, links, indexes, or logs.
- compatibility
- Any agent host with the OpenKnowledge MCP server configured. The optional `okf` plugin provides continuous conformance feedback. # This skill may live inside an OKF bundle, so it carries the required type.
- type
- Document
- metadata
- plugin: "okf" author: "Inkeep" repository: "https://github.com/inkeep/open-knowledge-skills"
Open Knowledge Format (OKF)
OKF v0.2 is a portable format for agent-readable knowledge: Markdown files, YAML frontmatter, and standard links. The /open-knowledge skill governs tool use; this skill covers OKF semantics.
Core rules
- A bundle is a directory tree of
.mdfiles. Each non-reserved file is one concept; its path without.mdis its ID. - Every concept needs parseable frontmatter with a non-empty string
type. No other field is always required. - Types are an open vocabulary. Consumers must accept unfamiliar types and metadata.
- Use standard Markdown links for portable relationships. Broken links and a missing index are allowed.
index.mdandlog.mdare reserved at every level. Use lowercase filenames.- An
index.mdnormally has no frontmatter; only the root index may declareokf_version: "0.2". - A
log.mdis newest-first; entry headings begin with an ISO date —## YYYY-MM-DD: Summary(the summary after the date is optional; a bare## YYYY-MM-DDis equally conformant). - OKF consumers read
.md, not.mdx.
Authoring judgment
- Make each concept the smallest useful link or citation target. Choose a stable, descriptive type;
Documentis only a generic fallback. - Do not invent facts, relationships, resources, sources, verification, or history. Missing knowledge is better than false structure.
- Use
title,description,resource, andtagsonly when they add real information. - Record provenance in
sources. Join claim-level citations with matchingsources[].idand Markdown footnotes. - Keep authorship and verification separate:
generatedsays who produced content;verifiedsays who confirmed it. Use exact lowercasehuman:andprocess:prefixes when applicable. - Write every provenance timestamp as an ISO 8601 datetime with an explicit UTC offset (
stale_after: 2026-12-31T00:00:00Z), never a bare date and never an offsetless time. This covers , , , , and both bounds. A entry heading is different: it stays a plain date.