A zero-dependency PDF/Office-to-OKF compiler using Gemini Flash

[vishal-raaj-dnd]

Hello everyone,

I would like to introduce OmniOKF (Omni Open Knowledge Format Compiler), an open-source tool developed to streamline the creation of OKF v0.1 bundles from legacy and raw document repositories.

Repository: https://github.com/vishal-raaj-dnd/gemini-okf-compiler

Overview

OmniOKF is a high-performance, zero-system-dependency compiler that transforms raw, unstructured document formats (.pdf, .docx, .xlsx, .pptx, .html, and .md) into structured, agent-ready Open Knowledge Format (OKF) catalogs.

Key Capabilities

1. Zero System Dependencies: Built entirely on Python-native libraries (such as Microsoft's markitdown), eliminating the need for external system binaries like Pandoc or GPU-bound OCR models.
2. Semantic Concept Partitioning: Automatically splits files at header boundaries (#, ##), then leverages the Gemini API to analyze, categorize, and extract structured metadata (e.g., tags, descriptions) to populate the required YAML frontmatter.
3. Incremental Compilation (Caching): To optimize performance and minimize API token utilization, the compiler computes cryptographic MD5 hashes of source documents. On subsequent executions, unmodified files are skipped and resolved directly from the local manifest cache.
4. Relational Cross-Linking & Visualization: Automatically scans the generated files to construct a relational knowledge graph using relative Markdown links. It also injects a visual Mermaid flowchart directly into the root index.md, allowing both human users and Markdown preview tools to view the concept network graph immediately.

Generated OKF Bundle Structure

When pointed to a raw directory, OmniOKF compiles the assets into a standardized hierarchical bundle:

.okf/
├── index.md             # Graph index with the embedded Mermaid network diagram
├── guides/              # Categorized concepts
│   ├── onboarding.md
│   └── setup.md
└── processes/
    └── incident-response.md

Each generated concept file is complete with valid OKF-compliant YAML metadata:

---
type: process
title: Incident Response Protocol
description: Standard operating procedures when a production alert is triggered.
tags: [operations, incident, engineering]
timestamp: 2026-07-10T00:30:00Z
---
# Incident Response Protocol

[Concept body contents...]

We would highly appreciate your feedback on this compiler implementation, and we hope to propose it for listing in the catalog's community tools documentation to help other developers bootstrap their OKF knowledge catalogs.