Pick a focused bundle
Start with a domain, workflow, category, policy area, or playbook your AI needs to understand.
Education for AI-ready knowledge
Give assistants, agents, and automation tools structured, cited, reusable knowledge instead of rebuilding context from scratch.
The problem
Most assistants can write, summarise, and plan, but they still need the right background before their output is useful. That background is often scattered across docs, wikis, tickets, spreadsheets, policies, and team memory.
Knowledge Bundles package that material into structured, source-aware context that a person can inspect and an AI tool can reuse.
How it works
Start with a domain, workflow, category, policy area, or playbook your AI needs to understand.
Use the bundle as reusable context for agents, assistants, coding tools, research workflows, or team automations.
Inspect the markdown, metadata, citations, and licence notes before relying on the output.
Keep the same structured context available across repeatable work instead of rebuilding prompts from scratch.
Use cases
Give agents reusable context, source provenance, and clearer task boundaries before they start work.
Build with better contextPackage procedures, handovers, policies, and service workflows into context assistants can reuse.
Improve operationsStart AI workflows from traceable sources, licence notes, review prompts, and clearly bounded use cases.
Work from sourcesStop rebuilding the same audience, category, positioning, and campaign context in every AI tool.
Reuse the briefTurn curriculum notes, examples, rubrics, and learner support material into AI-ready context.
Package learningTurn useful expertise into validated bundles with marketplace distribution and an 80% creator revenue share.
Package expertiseWhat bundles can contain
A bundle should be narrow enough to be useful, clear enough to review, and practical enough to plug into real assistant work.
Bundle examples
Trust layer
Open Knowledge Format gives Knowledge Bundles a simple structure: markdown files, metadata, links, and citations. That means the knowledge can be read by people and consumed by agents without a proprietary runtime.
The marketplace adds the commercial layer: discovery, samples, requests, creator submissions, review signals, and a path to buy ready-made bundles.
Learn about the formatBundles are built from ordinary files and markdown, so people can inspect the knowledge instead of trusting a black box.
Good bundles show citations, provenance, and licence notes so teams can check where important claims came from.
OKF gives bundles a simple structure that can move across tools, teams, repos, and AI workflows.
Marketplace review focuses on structure, metadata, conformance, and whether the bundle is clear enough to use responsibly.
Comparison
A prompt library stores instructions. A Knowledge Bundle stores reusable context the prompt can work from.
A wiki is written mainly for people. A bundle keeps the material readable while adding structure for AI tools.
A source folder can be useful, but a bundle adds metadata, citations, licence notes, and intended use cases.
FAQ
No. OKF is the structure underneath. Buyers can start with the bundle topic, examples, sources, and use case.
That is the goal. Bundles are designed around portable files and readable context rather than one closed app.
No. Good bundles make sources, limits, and review notes easier to inspect, but important work still needs human judgement.
Use the request path. Early demand signals help prioritise new categories, first-party bundles, and creator opportunities.
Ready to give your AI better context?