ellf-cli 4.0.94__tar.gz → 4.0.96__tar.gz

{ellf_cli-4.0.94/ellf_cli.egg-info → ellf_cli-4.0.96}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ellf-cli
-Version: 4.0.94
+Version: 4.0.96
 Summary: Ellf Command Line Interface
 Home-page: https://prodi.gy
 Author: ExplosionAI GmbH

{ellf_cli-4.0.94 → ellf_cli-4.0.96}/ellf_cli/about.json

@@ -1,7 +1,7 @@
 {
   "title": "Ellf CLI",
   "name": "ellf-cli",
-  "version": "4.0.94",
+  "version": "4.0.96",
   "summary": "Ellf Command Line Interface",
   "uri": "https://prodi.gy",
   "prog": "ellf",

{ellf_cli-4.0.94 → ellf_cli-4.0.96}/ellf_cli/ellf.json

@@ -1,7 +1,7 @@
 {
   "prog": "ellf",
   "help": "Ellf Command Line Interface.",
-  "version": "4.0.93",
+  "version": "4.0.95",
   "extra_key": "_extra",
   "commands": {
     "actions": {
@@ -204,7 +204,7 @@
           "orig_type": "bool"
         }
       ],
-      "description": "\nLog in to your Ellf account. You normally don't need to call this\nmanually. It will automatically authenticate when needed.\n",
+      "description": "\n    Log in to your Ellf account. You normally don't need to call this\n    manually. It will automatically authenticate when needed.\n    ",
       "allow_extra": false,
       "parent": null,
       "is_placeholder": false
@@ -257,7 +257,7 @@
           "orig_type": "Literal[api, cluster, id, ci]"
         }
       ],
-      "description": "\nReturn an auth token for the current user\n",
+      "description": "\n    Return an auth token for the current user\n    ",
       "allow_extra": false,
       "parent": null,
       "is_placeholder": false
@@ -333,7 +333,7 @@
           "orig_type": "list[Literal[tasks, actions, assets, datasets, paths]]"
         }
       ],
-      "description": "\nSave the state of the current app JSON file. If an assets directory is\nprovided, assets will be downloaded and referenced in the JSON accordingly.\n",
+      "description": "\n    Save the state of the current app JSON file. If an assets directory is\n    provided, assets will be downloaded and referenced in the JSON accordingly.\n    ",
       "allow_extra": false,
       "parent": null,
       "is_placeholder": false
@@ -368,7 +368,7 @@
           "orig_type": "bool"
         }
       ],
-      "description": "\nPopulate Ellf with data for projects, tasks, actions, assets and paths.\n",
+      "description": "\n    Populate Ellf with data for projects, tasks, actions, assets and paths.\n    ",
       "allow_extra": false,
       "parent": null,
       "is_placeholder": false
@@ -445,7 +445,7 @@
             "orig_type": "List[str]"
           }
         ],
-        "description": "\nCreate a new action. The available action recipes are fetched from your\ncluster and are added as dynamic subcommands. You can see more details\nand available arguments by calling the subcommand with --help, e.g. create\n[name] --help\n",
+        "description": "\n    Create a new action. The available action recipes are fetched from your\n    cluster and are added as dynamic subcommands. You can see more details\n    and available arguments by calling the subcommand with --help, e.g. create\n    [name] --help\n    ",
         "allow_extra": true,
         "parent": "actions",
         "is_placeholder": false
@@ -480,7 +480,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nList the actions on the cluster. By default, this includes their ID, name\nand current state, e.g. created or completed\n",
+        "description": "\n    List the actions on the cluster. By default, this includes their ID, name\n    and current state, e.g. created or completed\n    ",
         "allow_extra": false,
         "parent": "actions",
         "is_placeholder": false
@@ -926,7 +926,7 @@
             "orig_type": "List[str]"
           }
         ],
-        "description": "\nCreate a new agent. The available agent recipes are fetched from your\ncluster and are added as dynamic subcommands. You can see more details\nand available arguments by calling the subcommand with --help, e.g. create\n[name] --help\n",
+        "description": "\n    Create a new agent. The available agent recipes are fetched from your\n    cluster and are added as dynamic subcommands. You can see more details\n    and available arguments by calling the subcommand with --help, e.g. create\n    [name] --help\n    ",
         "allow_extra": true,
         "parent": "agents",
         "is_placeholder": false
@@ -1035,7 +1035,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nList the agents on the cluster. By default, this includes their ID, name\nand current state, e.g. created or completed\n",
+        "description": "\n    List the agents on the cluster. By default, this includes their ID, name\n    and current state, e.g. created or completed\n    ",
         "allow_extra": false,
         "parent": "agents",
         "is_placeholder": false
@@ -1529,7 +1529,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nGet detailed info for an asset uploaded to the cluster and registered\nwith Ellf\n",
+        "description": "\n    Get detailed info for an asset uploaded to the cluster and registered\n    with Ellf\n    ",
         "allow_extra": false,
         "parent": "assets",
         "is_placeholder": false
@@ -1629,7 +1629,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nCreate an asset on the cluster and register it with Ellf. Assets\npoint to files or directories you control. The Ellf server only has\na reference to them. This command doesn't transfer any data. See `ellf files`\nfor utilities to transfer files to and from your cluster\n",
+        "description": "\n    Create an asset on the cluster and register it with Ellf. Assets\n    point to files or directories you control. The Ellf server only has\n    a reference to them. This command doesn't transfer any data. See `ellf files`\n    for utilities to transfer files to and from your cluster\n    ",
         "allow_extra": false,
         "parent": "assets",
         "is_placeholder": false
@@ -1858,7 +1858,7 @@
             "orig_type": "Union[str, UUID]"
           }
         ],
-        "description": "\nDelete a cluster from PAM. This only removes PAM's record\nof it. The cluster itself will continue to exist - you need\nto shut it down separately.\n",
+        "description": "\n    Delete a cluster from PAM. This only removes PAM's record\n    of it. The cluster itself will continue to exist - you need\n    to shut it down separately.\n    ",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -1945,7 +1945,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "Check the health of a cluster deployment.\n\nRuns CLI-side connectivity checks against the cluster and PAM.\nUse --deep to also trigger cluster-side deployment checks (K8s API,\nNFS, database, etc.).\n",
+        "description": "Check the health of a cluster deployment.\n\n    Runs CLI-side connectivity checks against the cluster and PAM.\n    Use --deep to also trigger cluster-side deployment checks (K8s API,\n    NFS, database, etc.).\n    ",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -2028,7 +2028,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Rotate the cluster RSA keypair.\n\nGenerates a new keypair, updates the cluster record in PAM with the\nnew public key, patches the K8s secret with the new private key,\nand restarts the cluster deployment.\n",
+        "description": "Rotate the cluster RSA keypair.\n\n    Generates a new keypair, updates the cluster record in PAM with the\n    new public key, patches the K8s secret with the new private key,\n    and restarts the cluster deployment.\n    ",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -2813,7 +2813,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Export all the examples from a dataset and save it in the designated file as\nJSONL (newline-delimited JSON).\n",
+        "description": "Export all the examples from a dataset and save it in the designated file as\n    JSONL (newline-delimited JSON).\n    ",
         "allow_extra": false,
         "parent": "datasets",
         "is_placeholder": false
@@ -3248,7 +3248,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "Deploy or upgrade the Ellf Helm chart.\n\nCreates the namespace, image pull secret, cluster keypair secret,\nthen runs helm upgrade --install with the provided values.\n",
+        "description": "Deploy or upgrade the Ellf Helm chart.\n\n    Creates the namespace, image pull secret, cluster keypair secret,\n    then runs helm upgrade --install with the provided values.\n    ",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3492,7 +3492,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Install cluster infrastructure prerequisites (Traefik, cert-manager).\n\nThese operations are idempotent and safe to re-run.\n",
+        "description": "Install cluster infrastructure prerequisites (Traefik, cert-manager).\n\n    These operations are idempotent and safe to re-run.\n    ",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3775,7 +3775,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Manage TLS certificates for local cluster access.\n\nUse --self-signed when you have direct kubectl access to the cluster.\nUse --setup HOST to do everything from your laptop over SSH.\nUse --trust HOST to fetch and install an existing CA from a remote cluster.\n",
+        "description": "Manage TLS certificates for local cluster access.\n\n    Use --self-signed when you have direct kubectl access to the cluster.\n    Use --setup HOST to do everything from your laptop over SSH.\n    Use --trust HOST to fetch and install an existing CA from a remote cluster.\n    ",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3799,7 +3799,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "\nRun a job directly on the cluster from a YAML spec file, bypassing PAM.\n",
+        "description": "\n    Run a job directly on the cluster from a YAML spec file, bypassing PAM.\n    ",
         "allow_extra": false,
         "parent": "jobs",
         "is_placeholder": false
@@ -4877,7 +4877,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "\nUpload and advertise a recipes package from your Python environment.\n",
+        "description": "\n    Upload and advertise a recipes package from your Python environment.\n    ",
         "allow_extra": false,
         "parent": "publish",
         "is_placeholder": false
@@ -4990,7 +4990,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nTransfer data to the cluster, and advertise it to Ellf.\n\nThese steps can also be done separately. See `ellf files` to transfer\ndata to the cluster without creating an Asset record for it, and\n`ellf assets create` to create an Asset without transfer.\n",
+        "description": "\n    Transfer data to the cluster, and advertise it to Ellf.\n\n    These steps can also be done separately. See `ellf files` to transfer\n    data to the cluster without creating an Asset record for it, and\n    `ellf assets create` to create an Asset without transfer.\n    ",
         "allow_extra": false,
         "parent": "publish",
         "is_placeholder": false
@@ -5663,7 +5663,7 @@
             "orig_type": "List[str]"
           }
         ],
-        "description": "\nCreate a new task. The available task recipes are fetched from your\ncluster and are added as dynamic subcommands. You can see more details\nand available arguments by calling the subcommand with --help, e.g. create\n[name] --help\n",
+        "description": "\n    Create a new task. The available task recipes are fetched from your\n    cluster and are added as dynamic subcommands. You can see more details\n    and available arguments by calling the subcommand with --help, e.g. create\n    [name] --help\n    ",
         "allow_extra": true,
         "parent": "tasks",
         "is_placeholder": false
@@ -5698,7 +5698,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\nList the tasks on the cluster. By default, this includes their ID, name\nand current state, e.g. created or completed\n",
+        "description": "\n    List the tasks on the cluster. By default, this includes their ID, name\n    and current state, e.g. created or completed\n    ",
         "allow_extra": false,
         "parent": "tasks",
         "is_placeholder": false
@@ -6129,7 +6129,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "Fetch a batch of questions from a running annotation task.\n\nMirrors the web app: asks the broker for a Prodigy login token, then talks\nto the task pod directly via its public task_url. Note that requesting a\nbatch reserves those questions for this CLI's session \u2014 they will not be\nhanded to other annotators until they are answered or another session\nruns out of work and steals them.\n",
+        "description": "Fetch a batch of questions from a running annotation task.\n\n    Mirrors the web app: asks the broker for a Prodigy login token, then talks\n    to the task pod directly via its public task_url. Note that requesting a\n    batch reserves those questions for this CLI's session \u2014 they will not be\n    handed to other annotators until they are answered or another session\n    runs out of work and steals them.\n    ",
         "allow_extra": false,
         "parent": "tasks",
         "is_placeholder": false

ellf_cli-4.0.96/ellf_cli/ellf_skills/skills/ellf-annotate.assistant/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: ellf-annotate
+description: "Prepares annotation for launch in the Ellf cluster: audits readiness, selects the right recipe, and resolves arguments. Delegates to `/ellf-ops` to actually create the task (and optionally start it) once the audit passes. Use when the user is setting up annotation from scratch, choosing the right built-in recipe, verifying readiness, or planning an annotation agent — not for `run X` / `start Y` requests on a known recipe, which go directly to `/ellf-ops`. Use `/ellf-handoff` when a new custom recipe is needed (routes the implementation to the coding agent), and `/ellf-project` when broader project planning is required."
+argument-hint: "[describe what you want to annotate]"
+---
+
+# Prepare Annotation In Ellf
+
+Help the user get from an annotation-ready plan to a running annotation task.
+
+$ARGUMENTS
+
+## Your role
+
+You are responsible for:
+- checking that annotation is ready to launch (the audit)
+- choosing the right built-in Ellf annotation and/or agent recipe
+- deciding whether an existing custom recipe is sufficient
+- deciding when a new custom recipe is required
+- resolving the natural-scalar arguments the user can answer in chat
+- delegating to `/ellf-ops` to actually create (and optionally start) the task
+
+You do not call `*_create` tools yourself — that is `/ellf-ops`'s job. After
+the audit and arg resolution, delegate. You also do not implement new recipes.
+If the workflow requires a new custom recipe or custom interface, use
+`/ellf-handoff` to route the implementation to the coding workflow. If broader
+methodology or schema work is needed, use `/ellf-project`.
+
+**Never narrate routing or argument inference to the user.** The user does
+not need to know that you're delegating to `/ellf-ops`, what `auto_start`
+value you inferred from their verb, or which cli-name you chose for which
+field. Say only what the user can act on: the outcome, the next step, the
+link. The audit summary is useful when something failed and the user needs
+to fix it; otherwise skip it and let the create tool's artifact (card,
+form link, or prerequisite link) do the talking.
+
+## Required readiness audit
+
+Before choosing a recipe or building a launch spec, read:
+
+- `${CLAUDE_SKILL_DIR}/references/annotation_audit.md`
+- `${CLAUDE_SKILL_DIR}/references/builtin_ellf_annotation_recipes.md`
+
+The audit exists because launching with a poorly designed schema or a
+mismatched recipe wastes annotation effort and produces training data the
+model can't learn from. Use it to catch problems before you touch the
+platform.
+
+Do not launch until you have confirmed:
+- the annotation objective is clear
+- the schema or review target is stable enough
+- the recipe choice actually matches the task
+- the input data is ready
+- the target dataset is clear
+
+If the audit surfaces a problem:
+- methodological issues (schema design, task decomposition) → route to `/ellf-project`
+- recipe implementation needs (custom UI, routing logic) → route to `/ellf-handoff`
+
+## Recipe selection
+
+### Built-in task recipe first
+
+Prefer a built-in Ellf task recipe whenever it fits cleanly. The built-in
+recipes are documented in
+`${CLAUDE_SKILL_DIR}/references/builtin_ellf_annotation_recipes.md`.
+
+Call `mcp__pam__recipe_list` to confirm the recipe is available in the
+current environment before committing to it.
+
+### Existing custom recipe
+
+If the user names an existing cluster recipe and it matches the workflow,
+use it.
+
+### New custom recipe required
+
+If the audit shows the user needs a custom interface, routing logic, or
+annotation flow that built-ins cannot express cleanly:
+- do not force a bad built-in fit
+- use `/ellf-handoff` to assign custom recipe implementation to the coding agent
+- describe what the custom recipe must do
+
+## Annotation agents
+
+If the user wants automated annotation:
+- first ensure the base task is methodologically sound
+- prepare the task spec first
+- then identify an annotation-capable `agent_recipe` and prepare its args
+- both task and agent get created via `/ellf-ops` (separate `*_create` calls,
+  then `mcp__pam__task_assign_bot` to attach the agent to the task)
+
+Do not treat the agent as a replacement for task setup. The task is the
+base annotation workflow.
+
+## Recipe arguments
+
+Once the recipe is selected:
+- call `mcp__pam__recipe_list` to find the recipe ID
+- call `mcp__pam__recipe_schema` with the recipe ID
+- treat the returned field spec as the authoritative source for: exact arg keys, types, required vs optional fields, union variants, and cli-name remappings
+- fill args from context and the project plan where possible
+- ask only for natural-scalar values the user can answer in a sentence (a name, a language, a label list); object-typed args belong to the form
+- the create tool runs validation internally and decides what the user sees — do not narrate the schema response back to the user
+
+The annotation interface itself (what annotators see) cannot be previewed
+from the assistant. If the user needs to verify the annotation UI before
+cluster launch, they should use `ellf-dev run <recipe> [args]` in their
+local coding environment.
+
+## Execute via /ellf-ops
+
+After audit + recipe selection + arg resolution, delegate to `/ellf-ops` to
+create the task (and optionally start it):
+
+```text
+mcp__pam__task_create(
+  recipe_id=<from recipe_list>,
+  args=<resolved scalar args>,
+  name=<optional; PAM auto-names from recipe + timestamp when omitted>,
+  auto_start=<true if the user said run/start/launch, false for create/save/set up>,
+)
+```
+
+If an annotation agent was also planned, call `mcp__pam__agent_create(...)`
+for the agent. After the agent is created and started, attach it to the
+task with `mcp__pam__task_assign_bot(task_id=..., agent_id=...)`.
+
+The create tool's internal validation routes every case to a useful
+user-facing artifact:
+- confirmation card (three buttons: `Create and start` / `Create only` / `Cancel`) on clean validation
+- form-handoff link on missing scalars or complex JSON args
+- missing-prerequisite link on a referenced asset / dataset / secret that doesn't exist on the cluster
+
+Do not stop early to flag schema issues, preview validation problems, or
+direct the user elsewhere. The create tool produces a more useful artifact
+than your commentary. See `/ellf-ops` for the full create workflow and the
+forbidden patterns ("this won't validate, please fix", "the schema requires
+X, Y, Z", any pre-emptive validation reasoning).
+
+## After creation
+
+Once the user confirms the create card (or the form-handoff link is followed
+through to completion), help verify and run any follow-ups:
+
+- if the task wasn't auto-started (user clicked `Create only`): use `/ellf-ops`
+  start workflow when the user is ready
+- check cluster status at `GET /api/v1/jobs/{id}/status` to confirm the task
+  is running or healthy
+- provide the task link and tell the user where to open it in the app
+- if an agent was added, confirm it is assigned with `mcp__pam__task_bots_read`
+
+If startup or assignment fails:
+- inspect the cluster error or logs at `GET /api/v1/jobs/{id}/logs`
+- if this is an operational problem, use `/ellf-monitor` (or consult `/ellf-ops`)
+- if this is a recipe-capability problem, use `/ellf-handoff`
+
+When you finish:
+- state whether the setup passed the readiness audit
+- state which recipe path you selected
+- summarize the launch outcome (created / created and started / handed off to form / blocked on missing prerequisite)
+- if not launched, explain exactly what is missing and where you are routing the user next
+
+## Reference files
+
+| File | What it covers | When to read |
+|------|---------------|--------------|
+| `${CLAUDE_SKILL_DIR}/references/annotation_audit.md` | Readiness checklist: objective, schema, recipe fit, data, dataset | Before every launch |
+| `${CLAUDE_SKILL_DIR}/references/builtin_ellf_annotation_recipes.md` | Built-in Ellf task and agent recipes with supported workflows | Recipe selection |

{ellf_cli-4.0.94 → ellf_cli-4.0.96}/ellf_cli/ellf_skills/skills/ellf-monitor.assistant/SKILL.md

@@ -29,7 +29,7 @@ If an action is needed:
 ## Tool surface
 
 Use:
-- `mcp__broker__broker_request` for runtime status, logs, errors, cluster health, and dataset counts
+- `mcp__cluster__cluster_request` for runtime status, logs, errors, cluster health, and dataset counts
 - PAM read/list tools when you need persisted object details such as task, action, or agent identity
 
 Do not guess cluster state. Always check.
@@ -44,7 +44,7 @@ Before monitoring, determine what to monitor.
 
 Use:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/status")
 ```
 
 If there are multiple plausible jobs, use `AskUserQuestion` to let the user choose.
@@ -56,11 +56,11 @@ If there are multiple plausible jobs, use `AskUserQuestion` to let the user choo
 Read:
 - `${CLAUDE_SKILL_DIR}/references/training_monitoring.md`
 - `${CLAUDE_SKILL_DIR}/../ellf-train/references/training_troubleshooting.md`
-Use broker calls such as:
+Use cluster calls such as:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/status")
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 100})
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/errors")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 100})
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/errors")
 ```
 
 Your job is to:
@@ -75,10 +75,10 @@ If follow-up action is needed, route to `/ellf-ops` or `/ellf-handoff`.
 
 ### Annotation tasks
 
-Use broker calls such as:
+Use cluster calls such as:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/status")
-mcp__broker__broker_request(method="GET", path="/api/v1/datasets/example-count", query={"dataset": "<name>"})
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/datasets/example-count", query={"dataset": "<name>"})
 ```
 
 Read when needed:
@@ -95,11 +95,11 @@ If useful, combine task status with task detail from PAM reads to confirm the da
 
 ### Agents
 
-Use broker calls such as:
+Use cluster calls such as:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/status")
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 50})
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/errors")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 50})
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/errors")
 ```
 
 Report:
@@ -114,9 +114,9 @@ If the agent is failing repeatedly, recommend `/ellf-ops` for stop/restart or `/
 
 For non-training actions:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/status")
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 50})
-mcp__broker__broker_request(method="GET", path="/api/v1/jobs/{id}/errors")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/logs", query={"tail_lines": 50})
+mcp__cluster__cluster_request(method="GET", path="/api/v1/jobs/{id}/errors")
 ```
 
 Report:
@@ -129,9 +129,9 @@ Report:
 
 When the user asks about the cluster itself, use:
 ```text
-mcp__broker__broker_request(method="GET", path="/api/v1/status")
-mcp__broker__broker_request(method="GET", path="/api/v1/nodes")
-mcp__broker__broker_request(method="GET", path="/api/v1/worker-types")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/status")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/nodes")
+mcp__cluster__cluster_request(method="GET", path="/api/v1/worker-types")
 ```
 
 Report:
@@ -144,7 +144,7 @@ Report:
 
 Use compact summaries and tables.
 
-Never dump raw JSON or raw broker responses.
+Never dump raw JSON or raw cluster responses.
 
 When presenting logs:
 - summarize the important lines

{ellf_cli-4.0.94 → ellf_cli-4.0.96}/ellf_cli/ellf_skills/skills/ellf-monitor.assistant/references/training_monitoring.md

@@ -4,7 +4,7 @@ How to monitor training jobs from the web assistant and interpret their signals.
 
 ## What the web assistant can do
 
-Use broker-backed status, logs, and errors to determine:
+Use cluster-backed status, logs, and errors to determine:
 - whether the training action is running
 - whether it completed or failed
 - whether logs show loss, score, or alert-like signals

{ellf_cli-4.0.94 → ellf_cli-4.0.96}/ellf_cli/ellf_skills/skills/ellf-monitor.coding/SKILL.md

@@ -167,7 +167,7 @@ Use the captured output or process info from the launch context when available.
 # Connectivity and service health
 ellf clusters check
 
-# Deeper broker-side checks (K8s, NFS, database)
+# Deeper cluster-side checks (K8s, NFS, database)
 ellf clusters check --deep
 
 # Node capacity and utilization (cpu, memory, gpu, pod count)