You have access to comfy, a local CLI that drives ComfyUI (local install or Comfy Cloud).

The surface splits cleanly in two:

Discovery — read-only commands that answer "what's here?" (nodes, schemas, workflow slots, auth state, env). Safe to call freely.
Execution — state-changing commands that submit work, edit files, sign in, or install software.

Read the Ground rules first; they cross both halves. Then the two halves are independent — you can scan only what's relevant to the task.

This is one of a skill family — skim the siblings before a big task so you know what exists, and reach for the right one rather than improvising its job: comfy-director (multi-shot narrative video — story, continuity, conform), comfy-build (build a custom ComfyUI environment on the developer platform), comfy-debug (any failed job: error code → fix), comfy-relay (surface a workflow/result in chat, never leave it in /tmp). When a task spans several, load them up front instead of discovering the gap mid-render.