{"id":71962,"plugin_id":"plugin_asdk_app_6ad65dd9cb4c8191952bdfc913e7b31a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-30T00:06:28.192Z","digest":"9c24fe0fee21e543313c3184bb5d965103cd8645d7d166242fa15a8cafb552c7","against":null,"payload":{"description":"Install the Runta CLI and sign in to Runta. Use before any Runta runtime task when the `runta` command is missing, a Runta command reports `MISSING_TOKEN` or `AUTH`, or the user asks to connect, log in to, or switch Runta environments.","included_files":[],"name":"runta-setup","skill_md_contents":"---\nname: runta-setup\ndescription: Install the Runta CLI and sign in to Runta. Use before any Runta runtime task when the `runta` command is missing, a Runta command reports `MISSING_TOKEN` or `AUTH`, or the user asks to connect, log in to, or switch Runta environments.\n---\n\n# Runta setup\n\nIf the Runta MCP tools are connected, call `whoami`. When it returns the\nuser's account, setup is complete and the CLI is not needed. When the client\nasks the user to sign in to Runta, let the user finish that browser sign-in;\nnever ask for a token in the chat.\n\nWithout the MCP tools, Runta runtime tasks run through the `runta` CLI.\nConfirm it is installed and signed in before doing anything else.\n\n## 1. Check the CLI\n\n```bash\nrunta --version\n```\n\nIf the command is not found, install the CLI and check again:\n\n```bash\nnpm install -g @runta/runta-cli\n```\n\nDo not install the CLI any other way unless the user asks.\n\n## 2. Check authentication\n\n```bash\nrunta ps --json\n```\n\n- `{\"action\": \"ps\", \"runtimes\": [...]}` means the CLI is signed in. Stop here.\n- `error.code` of `MISSING_TOKEN`, `AUTH`, or `UNAUTHENTICATED` means the CLI\n  needs to sign in. Continue to step 3.\n- `error.code` of `TRANSPORT` or `INVALID_ENDPOINT`, or an `SDK` error whose\n  message starts with `http error`, means the API is unreachable or\n  misconfigured. Show the user the message and the current `RUNTA_ENDPOINT`\n  value, if set. Do not try to sign in.\n\n## 3. Sign in\n\nPrefer the browser device flow. It never exposes a secret in the conversation.\n\n```bash\nrunta login --no-wait --json\n```\n\nThe output has `status: \"authorization_pending\"`, a `user_code`, and a\n`verification_uri_complete`. Give the user the link and the code, and ask them\nto approve the request in their browser. Then wait for approval:\n\n```bash\nrunta login --resume --wait --json\n```\n\nRun `runta ps --json` again to confirm sign-in worked.\n\nIf the user already has an API key, they can set `RUNTA_TOKEN` in the\nenvironment instead. Never ask the user to paste an API key into the chat, and\nnever print, log, or store the value of `RUNTA_TOKEN`.\n\n## Environments\n\nThe CLI talks to production by default. To target another environment, the\nuser sets `RUNTA_ENDPOINT` to that API base URL, for example\n`http://127.0.0.1:8080` for the local development stack. Only change\n`RUNTA_ENDPOINT` when the user asks.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}