mcpbeat

Kubesphere Cluster Management

kubesphere/kubesphere-cluster-management

KubeSphere cluster query Skill (read-only). Use when user requests to view cluster list, cluster status, cluster details, or cluster version info. Do not perform any write operations (create, delete, update). Use KubeSphere Console for management operations.

531 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
17017
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kubesphere/kubesphere --skill kubesphere-cluster-management

The instruction itself

4 sections, as written by the author

KubeSphere Cluster Query

> ⚠️ Security: Read-only only. Never use kubectl to create, update, or delete cluster resources. Use KubeSphere console instead.

When to Use

List or get KubeSphere cluster information: list clusters, get details, check status, identify host/member.

Commands

# List clusters
kubectl get cluster

# Get cluster details
kubectl get cluster <name> -o yaml

# Get cluster summary (name, connection type, version, status)
kubectl get cluster -o go-template='
{{printf "%-12s %-12s %-12s %-15s %-13s %-12s\n" "NAME" "CONN_TYPE" "KS_VERSION" "K8S_VERSION" "ClusterReady" "KSCORE_READY"}}
{{range .items}}{{printf "%-12s %-12s %-12s %-15s" .metadata.name .spec.connection.type .status.kubeSphereVersion .status.kubernetesVersion}}{{range .status.conditions}}{{if eq .type "Ready"}}{{printf "%-13s" .status}}{{end}}{{end}}{{range .status.conditions}}{{if eq .type "KSCoreReady"}}{{printf "%-12s" .status}}{{end}}{{end}}{{"\n"}}{{end}}'

Out of Scope

Cluster installation/upgrade/remove, any write operations. Use KubeSphere console.

How to use it

Copy the folder

Take kubesphere/kubesphere-cluster-management from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.