ellf-cli 4.0.146__tar.gz → 4.0.151__tar.gz

{ellf_cli-4.0.146/ellf_cli.egg-info → ellf_cli-4.0.151}/PKG-INFO

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

{ellf_cli-4.0.146 → ellf_cli-4.0.151}/ellf_cli/about.json

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

{ellf_cli-4.0.146 → ellf_cli-4.0.151}/ellf_cli/ellf.json

@@ -1,7 +1,7 @@
 {
   "prog": "ellf",
   "help": "Ellf Command Line Interface.",
-  "version": "4.0.145",
+  "version": "4.0.150",
   "extra_key": "_extra",
   "commands": {
     "actions": {
@@ -204,7 +204,7 @@
           "orig_type": "bool"
         }
       ],
-      "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    ",
+      "description": "\nLog in to your Ellf account. You normally don't need to call this\nmanually. 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": "\n    Return an auth token for the current user\n    ",
+      "description": "\nReturn 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": "\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    ",
+      "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",
       "allow_extra": false,
       "parent": null,
       "is_placeholder": false
@@ -368,7 +368,7 @@
           "orig_type": "bool"
         }
       ],
-      "description": "\n    Populate Ellf with data for projects, tasks, actions, assets and paths.\n    ",
+      "description": "\nPopulate 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": "\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    ",
+        "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",
         "allow_extra": true,
         "parent": "actions",
         "is_placeholder": false
@@ -480,7 +480,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "description": "\nList the actions on the cluster. By default, this includes their ID, name\nand 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": "\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    ",
+        "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",
         "allow_extra": true,
         "parent": "agents",
         "is_placeholder": false
@@ -1035,7 +1035,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "description": "\nList the agents on the cluster. By default, this includes their ID, name\nand current state, e.g. created or completed\n",
         "allow_extra": false,
         "parent": "agents",
         "is_placeholder": false
@@ -1529,7 +1529,7 @@
             "orig_type": "bool"
           }
         ],
-        "description": "\n    Get detailed info for an asset uploaded to the cluster and registered\n    with Ellf\n    ",
+        "description": "\nGet detailed info for an asset uploaded to the cluster and registered\nwith Ellf\n",
         "allow_extra": false,
         "parent": "assets",
         "is_placeholder": false
@@ -1629,7 +1629,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "assets",
         "is_placeholder": false
@@ -1700,7 +1700,7 @@
       "import": {
         "name": "import",
         "args": [],
-        "description": "Read a serialised FileSecrets blob from stdin and write it to\n    the local secrets file.\n\n    Counterpart to ``ellf auth push``. Existing local auth state is\n    overwritten; the file is written 0600 by FileSecrets.save.\n    ",
+        "description": "Read a serialised FileSecrets blob from stdin and write it to\nthe local secrets file.\n\nCounterpart to ``ellf auth push``. Existing local auth state is\noverwritten; the file is written 0600 by FileSecrets.save.\n",
         "allow_extra": false,
         "parent": "auth",
         "is_placeholder": false
@@ -1735,7 +1735,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Push local auth state to a remote machine via SSH.\n\n    Reads the local FileSecrets, JSON-serialises it, and pipes it to\n    ``<remote_ellf> auth import`` over an SSH connection to *host*.\n    Authentication is delegated to ssh \u2014 anything in your ssh config\n    (host aliases, ProxyJump, key-based auth) just works.\n\n    The pushed blob includes id_token, api_token, and any cached\n    broker_tokens. id_token expiry is dictated by the issuer (typically\n    ~1h), so this is a \"give the remote a usable session\" operation,\n    not a permanent provisioning. Re-run when the token expires.\n    ",
+        "description": "Push local auth state to a remote machine via SSH.\n\nReads the local FileSecrets, JSON-serialises it, and pipes it to\n``<remote_ellf> auth import`` over an SSH connection to *host*.\nAuthentication is delegated to ssh \u2014 anything in your ssh config\n(host aliases, ProxyJump, key-based auth) just works.\n\nThe pushed blob includes id_token, api_token, and any cached\nbroker_tokens. id_token expiry is dictated by the issuer (typically\n~1h), so this is a \"give the remote a usable session\" operation,\nnot a permanent provisioning. Re-run when the token expires.\n",
         "allow_extra": false,
         "parent": "auth",
         "is_placeholder": false
@@ -1903,7 +1903,7 @@
             "orig_type": "Union[str, UUID]"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -1990,7 +1990,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -2073,7 +2073,7 @@
             "orig_type": "str"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "clusters",
         "is_placeholder": false
@@ -2858,7 +2858,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Export all the examples from a dataset and save it in the designated file as\n    JSONL (newline-delimited JSON).\n    ",
+        "description": "Export all the examples from a dataset and save it in the designated file as\nJSONL (newline-delimited JSON).\n",
         "allow_extra": false,
         "parent": "datasets",
         "is_placeholder": false
@@ -3293,7 +3293,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3537,7 +3537,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "Install cluster infrastructure prerequisites (Traefik, cert-manager).\n\n    These operations are idempotent and safe to re-run.\n    ",
+        "description": "Install cluster infrastructure prerequisites (Traefik, cert-manager).\n\nThese operations are idempotent and safe to re-run.\n",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3820,7 +3820,7 @@
             "orig_type": "str"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "infra",
         "is_placeholder": false
@@ -3844,7 +3844,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "\n    Run a job directly on the cluster from a YAML spec file, bypassing PAM.\n    ",
+        "description": "\nRun a job directly on the cluster from a YAML spec file, bypassing PAM.\n",
         "allow_extra": false,
         "parent": "jobs",
         "is_placeholder": false
@@ -4922,7 +4922,7 @@
             "orig_type": "str"
           }
         ],
-        "description": "\n    Upload and advertise a recipes package from your Python environment.\n    ",
+        "description": "\nUpload and advertise a recipes package from your Python environment.\n",
         "allow_extra": false,
         "parent": "publish",
         "is_placeholder": false
@@ -5035,7 +5035,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "publish",
         "is_placeholder": false
@@ -5708,7 +5708,7 @@
             "orig_type": "List[str]"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": true,
         "parent": "tasks",
         "is_placeholder": false
@@ -5743,7 +5743,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "description": "\nList the tasks on the cluster. By default, this includes their ID, name\nand current state, e.g. created or completed\n",
         "allow_extra": false,
         "parent": "tasks",
         "is_placeholder": false
@@ -6174,7 +6174,7 @@
             "orig_type": "bool"
           }
         ],
-        "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    ",
+        "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",
         "allow_extra": false,
         "parent": "tasks",
         "is_placeholder": false

ellf_cli-4.0.151/ellf_cli/ellf_skills/bin/write-current-session.py

@@ -0,0 +1,71 @@
+#!/usr/bin/env python3
+from __future__ import annotations
+
+import json
+import os
+import subprocess
+import sys
+from datetime import datetime, timezone
+from pathlib import Path
+
+
+def _load_hook_input() -> dict:
+    try:
+        raw = sys.stdin.read()
+    except Exception:
+        return {}
+    if not raw.strip():
+        return {}
+    try:
+        data = json.loads(raw)
+    except json.JSONDecodeError:
+        return {}
+    return data if isinstance(data, dict) else {}
+
+
+def _normalize_project_dir(project_dir: str) -> str:
+    cwd = Path(project_dir).resolve()
+    try:
+        result = subprocess.run(
+            ["git", "rev-parse", "--show-toplevel"],
+            check=False,
+            capture_output=True,
+            text=True,
+            cwd=str(cwd),
+        )
+    except Exception:
+        return str(cwd)
+    root = result.stdout.strip()
+    return str(Path(root).resolve()) if root else str(cwd)
+
+
+def main() -> int:
+    hook_input = _load_hook_input()
+    session_id = str(
+        hook_input.get("session_id") or os.environ.get("CLAUDE_SESSION_ID", "")
+    ).strip()
+    project_dir = str(
+        hook_input.get("cwd") or os.environ.get("CLAUDE_PROJECT_DIR", "")
+    ).strip()
+    if not session_id or not project_dir:
+        return 0
+
+    target = Path.home() / ".claude" / "current_session.json"
+    target.parent.mkdir(parents=True, exist_ok=True)
+
+    payload = {
+        "session_id": session_id,
+        "project_dir": _normalize_project_dir(project_dir),
+        "updated_at": datetime.now(timezone.utc)
+        .isoformat(timespec="seconds")
+        .replace("+00:00", "Z"),
+    }
+
+    tmp_path = target.with_suffix(".tmp")
+    tmp_path.write_text(json.dumps(payload), encoding="utf-8")
+    tmp_path.replace(target)
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

ellf_cli-4.0.151/ellf_cli/ellf_skills/hooks/hooks.json

@@ -0,0 +1,37 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PLUGIN_ROOT/bin/write-current-session.py\""
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PLUGIN_ROOT/bin/write-current-session.py\""
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PLUGIN_ROOT/bin/write-current-session.py\""
+          }
+        ]
+      }
+    ]
+  }
+}

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

@@ -0,0 +1,168 @@
+---
+name: ellf-annotate
+description: "Set up and launch annotation in the Ellf cluster once the methodology, schema, and data are ready. Use when the user wants to start annotating data in Ellf, launch an annotation task, choose the right built-in Ellf recipe, verify that annotation is ready to launch, run a review workflow, or add an annotation agent to a task. Also trigger on \"I want to annotate\", \"start annotation\", \"set up a labeling task\", \"which Ellf recipe should I use\", \"launch a review task\", \"start review\", \"set up an annotation agent\", or \"help me run annotation in Ellf\". This skill is the annotation readiness gatekeeper: it applies the audit checklist before launch, prefers built-in Ellf task recipes when possible, and delegates to `/ellf-prodigy` when a new custom recipe must be implemented."
+argument-hint: "[describe what you want to annotate]"
+---
+
+# Launch Annotation In Ellf
+
+Help the user get from an annotation-ready plan to a working Ellf task.
+
+$ARGUMENTS
+
+## Your role
+
+You are responsible for:
+- checking that annotation is ready to launch
+- choosing the right built-in Ellf annotation and/or agent task 
+- deciding whether an existing custom recipe is sufficient
+- deciding when a new custom recipe is required
+- setting up the Ellf task
+- optionally setting up an annotation agent after the task is sound
+- verifying that the task is actually running and accessible
+
+You do not implement new recipes in this skill. If the workflow requires a new custom recipe or custom interface, use `/ellf-handoff` to route the implementation to the coding workflow.
+
+## 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
+- create and start the task first
+- then identify an annotation-capable `agent_recipe`
+- create and start the agent
+- assign 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_prepare_create` with the recipe ID and any known partial args
+- treat the returned field spec as the authoritative source for: exact arg keys, required vs optional fields, missing required values, and dataset/asset/secret validation — this is the assistant-side equivalent of running `ellf-dev preview` locally
+- fill args from context and the project plan where possible
+- ask only for the values `mcp__pam__recipe_prepare_create` reports as missing and required
+
+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.
+
+If too many required values are still missing, or the user would be better off reviewing the configuration visually, direct them to the appropriate task creation flow in the app instead of guessing.
+
+
+## Launch flow
+
+### 1. Confirm unresolved values
+
+If required values are still missing:
+- ask only for the missing values, tied directly to the recipe fields
+- confirm the full configuration with `AskUserQuestion` before creating
+
+### 2. Create the task
+
+```
+mcp__pam__task_create(
+  recipe_id="<from recipe_list>",
+  name="<task_name>",
+  args=<resolved from recipe_prepare_create>,
+  worker_class="<class if needed>"
+)
+```
+
+### 3. Read back the created task
+
+Call `mcp__pam__task_read` with the returned task ID. You need the full object to build the start payload — specifically `id`, `name`, `plan.container`, `plan.recipe_name`, `plan.args`, `plan.positional_fields`, `plan.cli_names`, `plan.package_name`, and `plan.objects`.
+
+### 4. Start the task
+
+```
+mcp__broker__broker_request(
+  method="POST",
+  path="/api/v1/jobs/start-job",
+  body={
+    "job_id": "<task.id>",
+    "job_type": "task",
+    "name": "<task.name>",
+    "container": "<task.plan.container>",
+    "plan": {
+      "recipe_name": "<task.plan.recipe_name>",
+      "args": "<task.plan.args>",
+      "positional_fields": "<task.plan.positional_fields>",
+      "cli_names": "<task.plan.cli_names>",
+      "package_name": "<task.plan.package_name>",
+      "objects": "<task.plan.objects>"
+    }
+  }
+)
+```
+
+Do not omit fields from `plan`.
+
+### 5. Add an annotation agent if requested
+
+If the user wants automated annotation:
+1. call `mcp__pam__recipe_list` to find an annotation-capable agent recipe
+2. call `mcp__pam__recipe_prepare_create` to get the agent args
+3. create the agent with `mcp__pam__agent_create`
+4. read it back with `mcp__pam__agent_read` to get the full plan
+5. start it via broker `/api/v1/jobs/start-job` with `"job_type": "agent"`
+6. assign it with `mcp__pam__task_assign_bot(task_id=..., agent_id=...)`
+
+## Verification after launch
+
+A launch is not complete until you verify the task is usable.
+
+After start:
+- check broker status at `GET /api/v1/jobs/{id}/status`
+- confirm the task is running or healthy
+- provide the task mention/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 broker error or logs at `GET /api/v1/jobs/{id}/logs`
+- if this is an operational problem, use `/ellf-monitor` (or consult `/ellf-ops` for the relevant broker/PAM commands)
+- 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 spec
+- if not launching, explain exactly what is missing and where you are routing the user next

{ellf_cli-4.0.146 → ellf_cli-4.0.151}/ellf_cli/ellf_skills/skills/ellf-annotate.coding/SKILL.md

@@ -183,11 +183,3 @@ When you finish:
 - state which runtime target will be used
 - summarize the launch spec clearly
 - if not launching, 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 for cluster |
-| `${CLAUDE_SKILL_DIR}/references/builtin_prodigy_recipes.md` | Built-in standalone Prodigy recipes | Recipe selection for local |

{ellf_cli-4.0.146 → ellf_cli-4.0.151}/ellf_cli/ellf_skills/skills/ellf-handoff/SKILL.md

@@ -21,7 +21,6 @@ the **AskUserQuestion** tool to ask — do NOT ask in plain text.
 |---|---|
 | **description** | Specific and actionable. Not "implement NER" but "Create a custom ner.correct recipe with Ctrl+Enter keybinding for accept_best." |
 | **context_summary** | 2-3 paragraphs condensing the conversation: what was discussed, decisions made, constraints, label schemes, data formats. |
-| **plan_docs** | List of plan names the coding agent should read for project context. Use `project_plan_list` to see what exists, then pass only the plans relevant to this handoff (e.g. the overview plan plus the component plan the work targets). Leave empty if no plans exist yet. |
 
 ## Step 2: Create the request
 
@@ -30,8 +29,7 @@ Call the `todo_create` PAM tool — do NOT use Bash or ellf:
 ```
 todo_create(
   description="<description>",
-  context_summary="<context_summary>",
-  plan_docs=["project_plan", ...]
+  context_summary="<context_summary>"
 )
 ```