workloadlisted

Manages the whole life of a declared run on a machine: declare it, provision it, list it, show it, reconcile the declaration against what is actually there, adopt something that already exists by hand, and retire it with a reason. Every declaration lives in workflow/workloads/<id>.yaml and is the truth; the unit on the machine is an artifact that can be rebuilt from it at any time. State is never read from a declared status field, always from the live service manager. Backends: launchd (user and system), systemd, cron and a dispatcher, plus manual and external for runs that are only documented. Use it whenever the question is "what runs on this machine, is it still there, and who owns it", or when a scheduled job, interval job, daemon, path watcher or agent has to be set up, moved, checked or switched off. Trigger phrases: "workload", "declare a run", "provision the job", "is the job still there", "reconcile the machine", "adopt this unit", "retire the job", "what runs on that host", "the report did not arriv
bks-lab/open-bridge · ★ 10 · AI & Automation · score 75

Install: claude install-skill bks-lab/open-bridge

# Workload One declared run, on one machine, with an owner. The declaration in `workflow/workloads/<id>.yaml` is the source of truth; the unit file on the machine is an artifact and may be rebuilt from the declaration at any time. The engine is `skills/workload/engine/` behind the shim `skills/workload/workload.sh`. The data is the declaration plus `_schema.yaml` and `_template.yaml` next to it. Nothing instance specific lives in the code: hosts come from `infra/remotes/`, paths and prefixes from the `workloads:` block of `bridge-config.yaml`. ## Guard `workloads.enabled` must not be `false` in `bridge-config.yaml`. A missing block means defaults, never a crash. A `false` refuses every subcommand with exit `3` and names the key and the file it read. `reconcile --notify` speaks through the program declared in `workloads.notify_via`, never through a name this skill knows: ```yaml workloads: notify_via: command: ["~/bin/my-notifier", "--subject", "{what}", "--host", "{where}", "--action", "{todo}"] detail: ["--body", "{detail}"] # appended only when there is detail ``` Substitution is per argv element, so a value with a space stays one argument. With no `notify_via`, `--notify` sends nothing and says so, naming the key: an alarm path this skill invented would be a dependency the repository does not ship. ## Commands ``` workload list [--host H] [--kind K] [--runtime R] [--owner O] [--scope S] [--retired] [--json] workload show