Browser-only bundle tool

OKF Folder Validator: check a local knowledge bundle

Check a local OKF bundle folder before publishing. The browser reads only selected Markdown files, reports folder structure findings such as duplicate resources and relative links, and does not upload your files to this website.

Choose folder or files

Chrome and Edge support folder selection. If your browser does not, select multiple `.md` or `.markdown` files instead. The page reads Markdown files only, with size limits to protect the browser.

Why folder validation matters

The single-file OKF validator checks one pasted Markdown document. This folder validator checks how files work together: bundle layout, `index.md`, repeated resources, and relative links between Markdown files. An optional `llms.txt` file can point readers to the bundle, but this tool does not read or validate it.

OKF bundle validation checks

Index files

A root index.md helps readers and agents inspect the bundle scope before opening every file.

Duplicate resources

Repeated resource values usually mean two files describe the same source and need review.

Relative links

Relative Markdown links should point to files that exist inside the selected folder.

Frontmatter consistency

Each Markdown file should expose parseable frontmatter and a clear type field.

Problem
Why it matters
Fix route
Markdown files
A bundle should contain reviewable `.md` concept files.
Select `.md` or `.markdown` files.
Simple frontmatter
Machines need predictable metadata before reading the body.
Fix one file first.
type field
The draft OKF field checked by this guide must identify the concept kind.
Review common errors.
index.md
A root index helps humans and agents inspect the bundle before opening every file.
Add a root index.md.
Internal links
Relative Markdown links should point to files that exist inside the selected bundle.
Fix paths or add the target file.
Duplicate resource
Repeated canonical resources usually mean two files describe the same concept.
Merge overlap or split concepts clearly.

Repair order

  1. Select an OKF folder or several Markdown files.
  2. The page filters for Markdown files before reading file text locally in your browser.
  3. The report checks frontmatter, `type`, recommended fields, links, and duplicate resources.
  4. Fix parsing and required-field errors before index, link, and duplicate-resource warnings.
  5. Review remaining warnings with the content owner before publishing.
  6. Run the folder check again after fixing files.
Expected bundle shape
bundle/
  index.md
  llms.txt (optional public entry point; not read by this validator)
  pages/home.md
  support/contact.md

Single-file vs folder checks

Check
Use it for
What it cannot prove
OKF Validator
One pasted Markdown file, frontmatter, required fields, and body warnings.
Whether related files exist or source claims are current.
OKF Folder Validator
A selected local bundle with index.md, duplicate resources, and relative links.
Official conformance, source truth, SEO visibility, or AI citations.

Trust and privacy boundary

This folder validator checks this site's guide-profile structure for selected local files. It is useful before publishing, but it is not official OKF conformance, OpenAPI contract validation, or proof that the Markdown body is factually current.

FAQ

OKF folder validator questions

Does this upload my files?

No. The validation logic uses browser File APIs and prints the report in the page.

Does this support ZIP upload?

Not in this MVP. Select a folder in a supported browser or select multiple Markdown files.

Is a passing bundle officially certified?

No. Passing means this guide profile did not find structural errors. It is not official certification.

Can I use this in CI?

No. Use this page for browser review. For CI, use a local script or command-line validator.