GBDL: one Markdown+YAML file to save a multi-agent Grok Bot setup
用一份文件记下整支 Bot 小队，方便进版本库。 Save a whole Bot squad in one file so it can live in version control.
jcpsimmons 的社区提案（MIT，v0.1）：用一份 `.gbdl.md`（Markdown 引言 + 单一 YAML fence）描述调度者、专精 Bot、connectors、onboarding、memory 与 routines，便于进 git / 换机复原。附 minimal / ops-team / media-studio 示例、JSON Schema 与 reinstate 顺序。非官方格式，但可复现；密钥不得写入文件。 jcpsimmons’s community proposal (MIT, v0.1): one `.gbdl.md` (Markdown intro + a single YAML fence) captures dispatcher, specialists, connectors, onboarding, memory, and routines so a fleet can be checked into git or rebuilt on a new machine. Ships minimal / ops-team / media-studio examples, a JSON Schema, and a reinstate order. Unofficial — reproducible, but keep secrets out of the file.
为什么推荐Why we recommend it HN Show 49628911（2026-09-09）。公开仓库约 2 star（2026-09-10 核对）。规格与示例可照抄；加载器需自备或手搓 reinstate。 HN Show 49628911 (2026-09-09). Public repo ~2 GitHub stars (checked 2026-09-10). Spec + examples are copyable; you still need a loader or a manual reinstate.
先在可撤回、不外发的范围内试跑一遍，确认输出可用，再考虑扩大权限。 Try it first in a reversible, non-outbound scope. Confirm the output, then widen permissions.
把跑通的步骤存成 Skill，下次同类任务直接复用，而不是重新口述。 Save the working steps as a Skill so the next similar job reuses them instead of being re-explained.
输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.
