← ClaudeAtlas

export-okflisted

Use when the user wants to export their DotAIOS knowledge into an Open Knowledge Format (OKF) bundle, or asks to produce, share, or hand off a portable copy of their context/vault/projects. Gates any external sharing behind the user's own decision.
filocosta46/dotaios · ★ 3 · Data & Documents · score 70
Install: claude install-skill filocosta46/dotaios
# export-okf Export your DotAIOS knowledge (context, vault, projects, decisions, connections) into an [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog) (OKF v0.1) bundle — plain markdown + YAML frontmatter, git-shaped, readable by any OKF tool. OKF is treated as **plumbing**: the bundle is a disposable projection, not a migration. Your source files are never modified. ## How to run ```bash dotaios export-okf # writes to <aios>/build/okf-export dotaios export-okf --out ~/share # choose the output directory dotaios export-okf --path ~/work # use a non-default AIOS folder ``` It injects the OKF-required `type` field at export, generates `index.md` per directory plus a bundle-root `index.md` declaring `okf_version: "0.1"`, and rewrites resolvable `[[wikilinks]]` to absolute `/path.md` links. ## The one rule The bundle is produced **locally only**. Producing it is not publishing it. Sharing it, committing it, hosting it, or handing it to someone else is the user's explicit decision — never do it automatically. Review first: ```bash open <aios>/build/okf-export/index.md ``` ## When NOT to use - To "convert" your AIOS to OKF in place. Don't — export is read-only by design; your folder stays DotAIOS-native. - To build storage, serving, or auth on top of OKF. Out of scope (OKF non-goals).