GBDL is a community proposal for an open format: save a multi-agent desktop assistant setup as one Markdown file whose body is YAML, then reinstate it later (connectors first, then onboarding, agents, memory, routines).
It is not an official Grok Bot product format. It is a portable, human-readable convention anyone can implement or extend.
Status: v0.1 (draft)
Why
Assistant fleets (dispatcher + specialists + routines + account links) usually live trapped inside one product session. GBDL makes the definition portable: check it into git, share an example, or rebuild the same shape on a new machine without retyping every agent prompt by hand.
Quickstart
- Read SPEC.md for semantics and validation rules.
- Copy an example from
examples/. - Edit the YAML fence: bot persona, connectors, onboarding,
user_context, agents. - Keep secrets out of the file. Connectors declare which accounts to link; credentials stay in the host.
- Point a GBDL-compatible loader at the
.gbdl.mdfile (or follow the reinstantiation order in the spec by hand).
Canonical files use the extension .gbdl.md: short Markdown intro, then exactly one yaml fence.
Examples
| File | Description |
|---|---|
| examples/minimal.gbdl.md | Smallest useful definition |
| examples/ops-team.gbdl.md | Dispatcher + Email Inbox + Workspace + Notion-style agents |
| examples/media-studio.gbdl.md | Fictional creator / media ops fleet (Northwind Media) |
Schema
JSON Schema for the YAML object: schema/gbdl-0.1.schema.json
Blog draft
blog/draft-gbdl.md - short essay on the problem and the one-file idea.
Hard rules (v0.1)
- No secrets in the file (tokens, passwords, private keys).
- No real personal PII in shared examples (use fictional names and
example.com). - Connectors are prompted before agents that need them are created.
- Spec version pinned with
gbdl: "0.1".
License
MIT. Copyright (c) 2026 Josh Simmons. See LICENSE.