Run any Skill in Manus with one click

cluster-login

Stars3

Forks0

UpdatedJuly 3, 2026 at 10:30

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

intility

intility/for-developers-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

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)"]

Cluster login

Goal

Get oc whoami to succeed against the user's cluster. Browser-based OAuth — they finish in the browser, you confirm in the terminal.

Step 1 — Pick the cluster

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]

Step 2 — Run the login

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.

Step 3 — Verify

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.

Step 4 — When it fails

Browser auth times out: re-run indev cluster login <cluster-name>
oc whoami says "Unauthorized": token didn't get saved — re-run login
oc 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.

Quick reference

indev cluster login <cluster-name>
oc whoami
oc get nodes

Examples

See references/usage-examples.md for typical conversations (single cluster, multiple clusters, browser doesn't open, permissions missing).

More from this repository

same repository

otel-operator

intility/for-developers-plugin

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".

2026-07-143

create-cluster

intility/for-developers-plugin

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.

2026-07-033

deploy-app

intility/for-developers-plugin

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.

2026-07-033

expose-app

intility/for-developers-plugin

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.

2026-07-033

getting-started

intility/for-developers-plugin

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.

2026-07-033

status

intility/for-developers-plugin

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.

2026-07-033

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)"]

Cluster login

Goal

Get oc whoami to succeed against the user's cluster. Browser-based OAuth — they finish in the browser, you confirm in the terminal.

Step 1 — Pick the cluster

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]

Step 2 — Run the login

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.

Step 3 — Verify

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.

Step 4 — When it fails

Browser auth times out: re-run indev cluster login <cluster-name>
oc whoami says "Unauthorized": token didn't get saved — re-run login
oc 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.

Quick reference

indev cluster login <cluster-name>
oc whoami
oc get nodes

Examples

See references/usage-examples.md for typical conversations (single cluster, multiple clusters, browser doesn't open, permissions missing).