Errors
Missing frontmatter, invalid YAML, and missing type block conformance.
OKF v0.1 checks
Open Knowledge Format Validator
Validate Markdown concepts against the minimal OKF v0.1 conformance rules.
Missing type fields are errors. Broken internal links are warnings so partial bundles remain useful.
What does an OKF concept look like?
--- type: Web Page title: Product Docs description: AI-readable documentation. --- # Summary A concise Markdown concept.
Generate OKF from a website
Paste a sitemap or up to 20 page URLs. The tool creates Markdown concepts, an index, a log, and a validation report.
Validate OKF v0.1 Markdown
Check required frontmatter, the required type field, optional quality signals, and internal links.
Frontmatter preview
type: Web Page title: Example Page description: A page converted into Open Knowledge Format.
What the OKF validator checks
OKF v0.1 conformance is intentionally small: concept files need parseable YAML frontmatter and a non-empty type field. This validator also adds quality warnings, an OKF Score, and top fixes so users know what to improve first.
Warnings
Missing descriptions, empty bodies, broken links, and weak index files.
Score
Structure, connectivity, and coverage roll up into one screenshot-friendly number.
How OKF Score is calculated
| Dimension | Checks | Why it matters |
|---|---|---|
| Structure | frontmatter, type, title, description | Agents can classify each concept. |
| Connectivity | index links, internal links, orphan concepts | Agents can traverse related knowledge. |
| Coverage | body length, summary depth, citations | Agents get enough context to cite or summarize. |
Common OKF issues
Missing type
Add a non-empty type field such as Web Page, Tool, Dataset, Metric, or Runbook.
Thin body
Add purpose, scope, key details, and source context. Valid Markdown can still be too vague.
Broken link
Repair internal Markdown links so agents can move between related concepts.