@delta-infra/cli 1.1.18 → 1.1.21

package/skills/delta-shared/SKILL.md

@@ -1,113 +1,113 @@
----
-name: delta-shared
-description: "delta-cli shared global rules: configuration and authentication checks, security boundaries, error handling, and sandbox destruction."
----
-
-# delta-cli Shared Rules
-
-General guidance for AI agents using `delta-cli`. Core principles: **check, do not guess or expose credentials**.
-
-## Before any operation
-
-1. Verify the server address:
-   ```bash
-   delta-cli config show
-   ```
-2. Inspect the local authentication configuration:
-   ```bash
-   delta-cli auth status
-   ```
-
-- If `auth status` reports `method: token` or `method: apikey`, a credential is configured locally; **run the requested command directly without logging in or initialising configuration again**.
-- `auth status` reads local configuration and environment overrides; it does not validate the credential with the remote server. If it reports `method: none`, follow “Complete configuration” below. If a requested command returns `error.type: auth` or `permission`, follow the matching recovery action below.
-
-## Complete configuration
-
-If the server address or credentials are missing, **ask the user once**, then initialise with the flag that matches the credential type:
-
-```bash
-delta-cli config init --base-url <server-url> --token <token>
-# For an API key:
-delta-cli config init --base-url <server-url> --apikey <api-key>
-```
-
-Do not use interactive `config init` (without flags), as it may hang when stdin is unavailable.
-
-### Priority of information sources
-
-1. Environment variables: `DELTA_INFRA_BASE_URL`, `DELTA_INFRA_TOKEN`, `DELTA_INFRA_API_KEY`
-2. `base_url`, `token`, and `apikey` in `~/.delta-infra/config.json` (environment values override file values)
-3. Default value: only `base_url` has an internal default
-4. If none of the above are available, **you must ask the user**; do not make anything up
-
-### Runtime credentials
-
-The CLI sends the effective credential in the `Authorization: Bearer <credential>` header; an API key takes precedence over a token when both are configured. It adds `X-User-Uid` when it can parse a `uid` from the credential as an unverified JWT.
-
-## Querying user information and remaining credits
-
-```bash
-delta-cli usage
-```
-
-This returns the current user's information and remaining credits (through the gateway `/infra/api/users/me`; the CLI automatically attaches the configured credentials). Keep only these three fields in the output:
-
-- `data.display_name`: display name (fall back to `user_id` if missing)
-- `data.user_id`: user ID
-- `data.resources.credit`: remaining balance in credits
-
-`username`/`id`/`email`/`role`/`quota`/`group`/`tier`/`status`/`created_at`/`is_admin`, `stats` and its `total_consumed_credits` (in the database's original quota units) are internal fields and must not be exposed externally.
-
-## Security rules
-
-- **Never output credentials**: token and API key values must not appear in logs, messages or the terminal.
-- **Never construct URLs or make HTTP requests yourself**: route all requests through `delta-cli`.
-- **Do not install the CLI proactively**: if the user says it is not installed, direct them to the README or `install.sh`; do not choose an installation method yourself.
-- **Confirm intent before write or delete operations**: tell the user what commands such as `sandbox kill`, `sandbox finish` and `sandbox write` will affect.
-- `~/.delta-infra/config.json` must have `0600` permissions; do not loosen them manually.
-- **The sandbox must be destroyed**: after calling `sandbox create`, call `sandbox kill` before the current task ends. The server does not clean up automatically; failure to destroy a sandbox leaves GPU resources occupied indefinitely. Do not skip this, even if an error occurs.
-
-## JSON output conventions
-
-```json
-{"ok":true,"data":{...}}
-{"ok":false,"error":{"type":"auth","message":"...","hint":"..."}}
-```
-
-AI agent parsing rules:
-- Always check `ok`; do not rely on the exit code alone.
-- `error.type` is the stable field for branching on: `auth`, `permission`, `not_found`, `validation`, `network`, `api`, `command_failed`, `internal`.
-- `error.hint` may be shown to the user.
-
-## Exit code conventions
-
-| Type | Exit Code | Scenario |
-|------|-----------|----------|
-| validation | 2 | Invalid flag or argument |
-| auth | 3 | Not authenticated or authentication failed |
-| permission | 4 | Insufficient permissions |
-| not_found | 5 | Sandbox or file does not exist |
-| network | 6 | DNS, timeout or connection failure |
-| api | 7 | Server returned a non-2xx response |
-| command_failed | 8 | Command failed inside the sandbox (non-zero `exit_code` or an error); on the SSE path, an error envelope is appended after the `complete` frame, with the stderr tail in `message` for quick reference |
-| internal | 10 | Internal client error |
-
-## Upgrade check
-
-After completing the user's request, if the JSON contains `_notice.update`, you may recommend:
-
-```bash
-delta-cli upgrade
-```
-
-## Common recovery actions
-
-| Error / symptom | Recovery action |
-|-------------|----------|
-| `error.type: auth` / `method: none` | Check the server address and local credential configuration. If no credential is configured or the server rejects it, ask the user once for a credential; use `--apikey` for an API key or `--token` for a bearer token, or set the matching `DELTA_INFRA_API_KEY` / `DELTA_INFRA_TOKEN` environment variable. |
-| `error.type: permission` | Check whether the current credential has sufficient permissions; if needed, ask for a credential with the required permissions. |
-| `error.type: not_found` | Check `sandbox_id` / path |
-| `error.type: network` | Check `base_url` and network connectivity |
-| `error.type: validation` | Check required flags and argument formats |
-| `error.type: command_failed` | Command failed inside the sandbox: the envelope's `message` already includes the stderr tail to help locate the issue quickly; the full `stderr` / `result_summary` are in the `complete` frame. Retry or correct the command |
-| Configuration file parsing failed | Check that `~/.delta-infra/config.json` contains valid JSON |
+---
+name: delta-shared
+description: "delta-cli shared global rules: configuration and authentication checks, security boundaries, error handling, and sandbox destruction."
+---
+
+# delta-cli Shared Rules
+
+General guidance for AI agents using `delta-cli`. Core principles: **check, do not guess or expose credentials**.
+
+## Before any operation
+
+1. Verify the server address:
+   ```bash
+   delta-cli config show
+   ```
+2. Inspect the local authentication configuration:
+   ```bash
+   delta-cli auth status
+   ```
+
+- If `auth status` reports `method: token` or `method: apikey`, a credential is configured locally; **run the requested command directly without logging in or initialising configuration again**.
+- `auth status` reads local configuration and environment overrides; it does not validate the credential with the remote server. If it reports `method: none`, follow “Complete configuration” below. If a requested command returns `error.type: auth` or `permission`, follow the matching recovery action below.
+
+## Complete configuration
+
+If the server address or credentials are missing, **ask the user once**, then initialise with the flag that matches the credential type:
+
+```bash
+delta-cli config init --base-url <server-url> --token <token>
+# For an API key:
+delta-cli config init --base-url <server-url> --apikey <api-key>
+```
+
+Do not use interactive `config init` (without flags), as it may hang when stdin is unavailable.
+
+### Priority of information sources
+
+1. Environment variables: `DELTA_INFRA_BASE_URL`, `DELTA_INFRA_TOKEN`, `DELTA_INFRA_API_KEY`
+2. `base_url`, `token`, and `apikey` in `~/.delta-infra/config.json` (environment values override file values)
+3. Default value: only `base_url` has an internal default
+4. If none of the above are available, **you must ask the user**; do not make anything up
+
+### Runtime credentials
+
+The CLI sends the effective credential in the `Authorization: Bearer <credential>` header; an API key takes precedence over a token when both are configured. It adds `X-User-Uid` when it can parse a `uid` from the credential as an unverified JWT.
+
+## Querying user information and remaining credits
+
+```bash
+delta-cli usage
+```
+
+This returns the current user's information and remaining credits (through the gateway `/infra/api/users/me`; the CLI automatically attaches the configured credentials). Keep only these three fields in the output:
+
+- `data.display_name`: display name (fall back to `user_id` if missing)
+- `data.user_id`: user ID
+- `data.resources.credit`: remaining balance in credits
+
+`username`/`id`/`email`/`role`/`quota`/`group`/`tier`/`status`/`created_at`/`is_admin`, `stats` and its `total_consumed_credits` (in the database's original quota units) are internal fields and must not be exposed externally.
+
+## Security rules
+
+- **Never output credentials**: token and API key values must not appear in logs, messages or the terminal.
+- **Never construct URLs or make HTTP requests yourself**: route all requests through `delta-cli`.
+- **Do not install the CLI proactively**: if the user says it is not installed, direct them to the README or `install.sh`; do not choose an installation method yourself.
+- **Confirm intent before write or delete operations**: tell the user what commands such as `sandbox kill`, `sandbox finish` and `sandbox write` will affect.
+- `~/.delta-infra/config.json` must have `0600` permissions; do not loosen them manually.
+- **The sandbox must be destroyed**: after calling `sandbox create`, call `sandbox kill` before the current task ends. The server does not clean up automatically; failure to destroy a sandbox leaves GPU resources occupied indefinitely. Do not skip this, even if an error occurs.
+
+## JSON output conventions
+
+```json
+{"ok":true,"data":{...}}
+{"ok":false,"error":{"type":"auth","message":"...","hint":"..."}}
+```
+
+AI agent parsing rules:
+- Always check `ok`; do not rely on the exit code alone.
+- `error.type` is the stable field for branching on: `auth`, `permission`, `not_found`, `validation`, `network`, `api`, `command_failed`, `internal`.
+- `error.hint` may be shown to the user.
+
+## Exit code conventions
+
+| Type | Exit Code | Scenario |
+|------|-----------|----------|
+| validation | 2 | Invalid flag or argument |
+| auth | 3 | Not authenticated or authentication failed |
+| permission | 4 | Insufficient permissions |
+| not_found | 5 | Sandbox or file does not exist |
+| network | 6 | DNS, timeout or connection failure |
+| api | 7 | Server returned a non-2xx response |
+| command_failed | 8 | Command failed inside the sandbox (non-zero `exit_code` or an error); on the SSE path, an error envelope is appended after the `complete` frame, with the stderr tail in `message` for quick reference |
+| internal | 10 | Internal client error |
+
+## Upgrade check
+
+After completing the user's request, if the JSON contains `_notice.update`, you may recommend:
+
+```bash
+delta-cli upgrade
+```
+
+## Common recovery actions
+
+| Error / symptom | Recovery action |
+|-------------|----------|
+| `error.type: auth` / `method: none` | Check the server address and local credential configuration. If no credential is configured or the server rejects it, ask the user once for a credential; use `--apikey` for an API key or `--token` for a bearer token, or set the matching `DELTA_INFRA_API_KEY` / `DELTA_INFRA_TOKEN` environment variable. |
+| `error.type: permission` | Check whether the current credential has sufficient permissions; if needed, ask for a credential with the required permissions. |
+| `error.type: not_found` | Check `sandbox_id` / path |
+| `error.type: network` | Check `base_url` and network connectivity |
+| `error.type: validation` | Check required flags and argument formats |
+| `error.type: command_failed` | Command failed inside the sandbox: the envelope's `message` already includes the stderr tail to help locate the issue quickly; the full `stderr` / `result_summary` are in the `complete` frame. Retry or correct the command |
+| Configuration file parsing failed | Check that `~/.delta-infra/config.json` contains valid JSON |

package/skills/delta-shared/agents/openai.yaml

@@ -1,4 +1,4 @@
-interface:
-  display_name: "Delta CLI Shared Rules"
-  short_description: "Handle Delta CLI configuration, authentication, errors and security boundaries"
-  default_prompt: "Use $delta-shared to check and resolve Delta CLI configuration or authentication issues."
+interface:
+  display_name: "Delta CLI Shared Rules"
+  short_description: "Handle Delta CLI configuration, authentication, errors and security boundaries"
+  default_prompt: "Use $delta-shared to check and resolve Delta CLI configuration or authentication issues."

package/skills/manifest.json

@@ -1,19 +1,20 @@
-{
-  "skills": [
-    "delta-sandbox",
-    "delta-shared",
-    "delta-science"
-  ],
-  "retired_skills": [
-    "pubchem",
-    "rdkit",
-    "pymatgen",
-    "gsasii",
-    "lammps",
-    "delta-bo",
-    "ldm-bo",
-    "synbo-service",
-    "antbo-service",
-    "antbo-ldm-guard"
-  ]
-}
+{
+  "skills": [
+    "delta-sandbox",
+    "delta-shared",
+    "delta-science",
+    "delta-protein"
+  ],
+  "retired_skills": [
+    "pubchem",
+    "rdkit",
+    "pymatgen",
+    "gsasii",
+    "lammps",
+    "delta-bo",
+    "ldm-bo",
+    "synbo-service",
+    "antbo-service",
+    "antbo-ldm-guard"
+  ]
+}