Open Knowledge Vault

Keep the knowledge readable without Obsidian. Use OKF v0.2 as the core, and make Dataview an optional view. Preserve existing human content and metadata when maintaining a vault.

Choose the scope

Inspect the requested vault, its instructions, schema, links, plugins, and current sources before writing. Infer the goal from the request; ask only for missing choices that affect the outcome. For a new bundle default to portable Markdown, with Obsidian setup or Dataview only when requested. Do not assume the user's personal vault is the destination.

Profiles are optional producer conventions, not OKF requirements:

• meeting: sources, concepts, ideas, events, questions, actions, people, organisations, maps
• learning: domains, courses, lessons, concepts, scenarios, questions, review tasks
• research/project: references, claims, decisions, procedures, questions, actions

Adapt the taxonomy to the material. Do not create empty notes to hit a count. A framework can organise a talk, but mark planned sections separately from delivered content.

Setup and audit

Use scripts/vault.py init PATH --title TITLE --profile meeting|learning|research for a new bundle. It only creates missing files. Add --obsidian for local Markdown-link preferences and --dataview for a dashboard with ordinary links plus optional queries. Templates are outside the bundle in this skill, not untyped Markdown inside it.