Update to Runta

{
  "description": "Manage the lifecycle of Runta runtimes (isolated microVMs) - create, list, inspect, boot, shut down, pause, resume, resize, and delete them. Use when the user asks about their Runta runtimes, sandboxes, or VMs, or wants to change their state.",
  "included_files": [],
  "name": "runta-runtimes",
  "skill_md_contents": "---\nname: runta-runtimes\ndescription: Manage the lifecycle of Runta runtimes (isolated microVMs) - create, list, inspect, boot, shut down, pause, resume, resize, and delete them. Use when the user asks about their Runta runtimes, sandboxes, or VMs, or wants to change their state.\n---\n\n# Runta runtimes\n\nPrefer the Runta MCP tools when they are available. Otherwise, manage runtimes\nwith the `runta` CLI. If `runta` is missing or a command reports\n`MISSING_TOKEN`, `AUTH`, or `UNAUTHENTICATED`, follow the `runta-setup` skill\nfirst.\n\n## MCP tools\n\nWhen the `runta` MCP server is connected, use these tools instead of the CLI:\n\n| Task | Tool | Arguments |\n| --- | --- | --- |\n| Show the signed-in account | `whoami` | none |\n| List runtimes | `list_runtimes` | optional `status` list, `limit`, `cursor` |\n| Inspect one runtime | `get_runtime` | `runtime` (name or id) |\n| Create a runtime | `create_runtime` | `name`, optional `image`, `vcpus`, `memory_mib`, `disk_size_gib` |\n| Start, stop, pause, resume | `start_runtime`, `stop_runtime`, `pause_runtime`, `resume_runtime` | `runtime` |\n| Change memory | `resize_runtime` | `runtime`, `memory_mib` |\n| Delete | `delete_runtime` | `runtime` |\n\nThe rules below still apply: lifecycle tools return as soon as Runta accepts\nthe request, so call `get_runtime` until `status` reaches the expected state,\nand confirm with the user before `stop_runtime`, `resize_runtime`, or\n`delete_runtime`. When `list_runtimes` returns `has_more: true`, pass\n`next_cursor` as `cursor` to read the next page. If a tool reports that Runta\nno longer accepts the connection, ask the user to reconnect the Runta app.\n\nUse the CLI below for anything the MCP tools don't cover, such as disk resize,\npublished ports, or idle policies.\n\n## Rules\n\n- Always pass `--json` and read the result from the JSON, not from prose.\n- A runtime can be addressed by its name or its UUID. When a name is\n  ambiguous or unknown, list runtimes first and confirm which one the user\n  means.\n- On failure the output is `{\"error\": {\"kind\", \"code\", \"message\",\n  \"required_action\"?}}` and the exit status is nonzero. Report the message.\n  When `required_action.type` is `run_command`, that command is the suggested\n  next step.\n- Lifecycle requests are asynchronous. A command returning means the API\n  accepted the request, not that the runtime reached its new state. Confirm\n  with `runta inspect NAME --json` before telling the user the change is done.\n- Ask the user to confirm before running `rm`, `shutdown`, or `resize`. Name\n  the exact runtimes affected. `rm` permanently deletes the runtime's disk and\n  memory. `shutdown` stops every process in the runtime.\n- Do not run commands inside a runtime, copy files, or change secrets, egress,\n  SSH, or checkpoints. Those are outside this skill.\n\n## Runtime states\n\n`status` is one of `creating`, `running`, `paused`, `suspended`, `shutdown`,\n`deleting`, `error`, `crashed`, or `unavailable`. `desired_status` is the\nstate Runta is moving toward. `degraded: true` on a running runtime means it\nhas not reported a heartbeat for at least 60 seconds.\n\n## List and inspect\n\n```bash\nrunta ps -a --json            # every runtime: id, name, status, vcpus, memory_mib, image_id\nrunta ps --json               # only running and suspended runtimes\nrunta inspect NAME --json     # full runtime object under \"runtime\"\n```\n\nIn `inspect` output, read `runtime.status`, `runtime.desired_status`,\n`runtime.vcpus`, and `runtime.cur_memory_mib`.\n\n## Create\n\n```bash\nrunta run --name NAME --wait --json\n```\n\nOptional flags:\n\n- `--image ID`: Runtime Image variant. Omit it for the default image.\n- `--cpus N` and `--memory MIB`: sizes. Omit them to use the image's\n  recommendation.\n- `--disk-size-gib GIB`: writable disk size.\n- `--publish PORT/http` or `--publish PORT/https`: repeatable ingress rule.\n- `--idle-mode suspend-only|suspend-and-wakeup --idle-timeout SECS`: suspend\n  the runtime when idle.\n- `--timeout-secs SECS`: how long `--wait` polls (default 180).\n\n`--wait` returns once the runtime can accept commands, or fails on error or\ntimeout. Without `--wait`, the result has `accepted` and `desired_status`;\npoll `runta inspect NAME --json` until `status` is `running`.\n\nOnly set flags the user asked for. Report the runtime's name, id, and status.\n\n## Power\n\n```bash\nrunta boot NAME --json        # start a shut-down runtime\nrunta shutdown NAME --json    # stop a runtime (confirm first)\nrunta pause NAME --json       # freeze a running runtime in memory\nrunta resume NAME --json      # continue a paused runtime\n```\n\nAfter each one, inspect the runtime until `status` matches the expected state:\n`running` after `boot` or `resume`, `shutdown` after `shutdown`, and `paused`\nafter `pause`.\n\n## Resize\n\n```bash\nrunta resize NAME --memory MIB --json\nrunta resize NAME --disk-size-gib GIB --json\n```\n\nPass at least one flag. Confirm the new sizes with the user first, then\ninspect the runtime to confirm they were applied.\n\n## Delete\n\n```bash\nrunta rm NAME [NAME...] --wait --timeout 120 --json\n```\n\nEach result's `status` is one of:\n\n- `deleted`: Runta verified the runtime is gone.\n- `delete_requested`: deletion was accepted but not verified (without\n  `--wait`).\n- `cleanup_unverified` with `accepted: true` and `ok: false`: deletion was\n  accepted but verification failed or timed out. Tell the user deletion is\n  in progress but unconfirmed. Do not say it was deleted, and do not request\n  deletion again.\n\nThe command exits nonzero if any runtime failed. Report each runtime's result\nseparately.\n"
}