RepoAI
Browse MCPs

KubeSphere Extension Management

94TrustedInstructions only

Orchestrate addon lifecycles, configuration, and status tracking within KubeSphere clusters.

What it does

Adding this skill updates your assistant to interpret and manage the specific custom resources defined for KubeSphere extensions. It allows for clearer communication regarding the current deployment status, version availability, and dependency requirements of add-on software without needing manual verification across separate dashboard panels.

The skill provides a framework for handling installation plans and configuration updates. It helps the assistant act as an informed bridge between your intent and the cluster-level actions required to reconcile the state of extensions, mapping your requests to the appropriate background operations.

When it earns its place

Reach for it when…

Apply this when you need to deploy a new extension, transition between specific versions, or resolve inconsistencies in existing addon states. It is intended for administrators who want to streamline the process of checking extension metadata or applying configuration changes across single or multi-cluster environments.

Look elsewhere when…

This skill does not manage the underlying Kubernetes cluster infrastructure, node-level hardware, or core KubeSphere platform upgrades. Avoid using it for troubleshooting connectivity or authentication issues unrelated to the extension lifecycle, as it lacks visibility into low-level network or resource availability logs.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • install the latest version of the monitoring extension
  • check the installation status of my current extensions
  • remove the unused logging extension from the cluster
  • show me what versions are available for this extension

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/kubesphere-extension-management ~/.claude/skills/kubesphere-extension-management

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/kubesphere-extension-management .claude/skills/kubesphere-extension-management

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

KubeSphere Extension Management changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →