vot-config

Files (1)

• SKILL.md

SKILL.md (first lines)

# /vot-config

State lives in the user's repository under `.vot/`:
`.vot/environments/<name>.yaml` (committed) and `.vot/config.yaml`
(`current: <name>`, gitignored). Never write a secret into either.

1. **Gitignore.** Ensure the repository's `.gitignore` contains
   `.vot/config.yaml` and `.vot/run/`, appending whichever is missing
   (every run, idempotent).
2. **Choose.** List `.vot/environments/*.yaml` (name, stack) and the current
   one; offer: create one, update one, or make one current (then go to step 8).
   Resolve each stack type per the stack-guide skill (an earlier name is
   read as the current one). An environment of a planned stack type cannot
   be updated or made current: say it is not supported in this version.
3. **Stack type.** On create: ask the name and the stack type, among the
   stack-guide skill's references (a planned type is listed as planned,
   not selectable - a user who names one is told it is not supported in
   this version and asked again). Read the stack-guide skill's reference
   for that type.
4. **Tools.** Run stack-guide's common prerequisite check plus that
   reference's *Prerequisites and install* checks. For a missing tool, show
   its install command and run it only on the user's yes; what is the
   user's (a driver, a cloud login) is stated, never done.
5. **Config.** Ask the reference's *Config fields*, showing the defaults.
6. **Prepare.** When the reference has a *Prepare* section, run it.
7. **Traces.** When the reference's *Config fields* say the config gives
   the traces endpoint, `otlp_endpoint` is neither asked nor written, and
   dropped when present. Otherwise ask `otlp_endpoint` (optional, empty to
   skip); warn when it names an address the reference's *Traps* say the
   stack cannot reach.
8. **Write.** On create or update, write `.vot/environments/<name>.yaml`:

   ```yaml
   name: <name>
   stack: <stack type>
   otlp_endpoint: <url>        # omitted when empty
   config:
     <field>: <value>
   ```

   Always, including make-current: write `.vot/config.yaml` with
   `current: <name>`, and print a summary: the environment, its stack, its
   config, whether traces are exported (and where).

From using-system/vllm-on-tap, MIT.

More from using-system/vllm-on-tap