菜单
Logs the user into their Intility Developer Platform cluster so they can run kubectl/oc commands against it. Use when the user asks to "log in", "log into the cluster", "connect to my cluster", "oc login", or when another skill needs cluster access and the user is not authenticated.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Sets up Collector and/or PodLogCollector for the pre-installed otel-operator on the Intility Developer Platform. Use when the user asks to "set up otel collector", "install otel collector", "configure otel operator", "collect pod logs", or "set up OpenTelemetry".
Creates a single cluster on the Intility Developer Platform for an external user. Use when the user asks to "create a cluster", "get me a cluster", "set up a cluster", or is being routed here by the getting-started skill. Creates ONE cluster with sensible defaults unless the user explicitly asks for more, since this plugin assumes a many-apps-on-one-cluster model.
Generates Kubernetes manifests (Namespace, Deployment, Service) for a containerized app and deploys them to the cluster with oc apply. Use when the user wants to "deploy my app", "ship my app", "run my app on the cluster", or after prepare-app has confirmed they have a containerized image. Defaults to a one-app-per-namespace layout so the same cluster can host many apps cleanly.
Gives a deployed app a public or internal URL by creating an HTTPRoute on the Intility Developer Platform. Use when the user says "expose my app", "give my app a URL", "make my app accessible", "set up ingress", "create a route", or after deploy-app finishes and the user wants the app reachable.
Entry point for getting an app running on the Intility Developer Platform. Use when the user says things like "help me deploy", "get me started with Intility", "I want to run my app on the platform", "I'm new to Kubernetes and need to ship something", or "what do I do next?". Figures out where the user is in the journey (no cluster yet → cluster but no app → app deployed but no URL → ready to update) and routes to the right skill.
Shows a summary of what the user has on the Intility Developer Platform — their cluster, deployed apps, and the URLs those apps are exposed on. Use when the user asks "what's deployed?", "what do I have running?", "what apps are on my cluster?", "what's the URL for X?", "show me my cluster", or comes back after a break and needs a refresher.
| name | cluster-login |
| description | Logs the user into their Intility Developer Platform cluster so they can run kubectl/oc commands against it. Use when the user asks to "log in", "log into the cluster", "connect to my cluster", "oc login", or when another skill needs cluster access and the user is not authenticated. |
| allowed-tools | ["AskUserQuestion","Bash(indev cluster list*)","Bash(indev cluster login*)","Bash(oc whoami*)","Bash(oc get nodes*)"] |
Get oc whoami to succeed against the user's cluster. Browser-based OAuth — they finish in the browser, you confirm in the terminal.
If only one cluster exists, use it.
indev cluster list
If multiple, ask:
Q: "Which cluster do you want to log in to?"
Options: [one per cluster name found]
indev cluster login <cluster-name>
This opens a browser. Tell the user one sentence:
A browser will open. Sign in with your Intility account, then come back here.
If the browser doesn't open, suggest:
indev cluster login <cluster-name> --no-browser
…which prints a URL they can paste manually.
After the user says they're done in the browser, confirm:
oc whoami
oc get nodes
If oc whoami returns their username and oc get nodes lists nodes (any status), they're in. Tell them briefly:
Logged in as . Your cluster has node(s) ready.
indev cluster login <cluster-name>oc whoami says "Unauthorized": token didn't get saved — re-run loginoc get nodes says "Forbidden": the account was created but no roles attached yet. Tell the user to check with their cluster owner or reach out to the Developer Platform Admins via their collaboration channel (samhandlingskanal).Do not go further down the troubleshooting tree than this. External users should escalate; they shouldn't be debugging RBAC.
indev cluster login <cluster-name>
oc whoami
oc get nodes
See references/usage-examples.md for typical conversations (single cluster, multiple clusters, browser doesn't open, permissions missing).