KubeSphere OpenKruise

94TrustedInstructions only

Automated lifecycle management for OpenKruise extensions within KubeSphere environments.

What it does

Integrating this skill allows your assistant to interface directly with OpenKruise resources inside KubeSphere. It bridges the gap between standard cluster operations and the specific requirements for managing extensions, ensuring that versioning, installation, and workload configuration are handled according to cluster-specific constraints.

By providing this knowledge, your assistant gains the ability to generate precise manifest files for advanced workloads and sidecar configurations. It also equips the assistant to perform diagnostic checks on controllers and pods, effectively acting as an interface for maintaining the health and state of Kruise-specific deployments.

When it earns its place

Reach for it when…

Install this when you need to deploy or manage OpenKruise extensions specifically within a KubeSphere cluster, or when you require assistance generating valid CloneSet or SidecarSet configurations.

Look elsewhere when…

Do not use this for general KubeSphere administration that is unrelated to the OpenKruise extension, or for configuring complex workloads like BroadcastJobs that are explicitly excluded from the default management scope.

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 openkruise extension in my kubesphere cluster
  • generate a cloneset manifest for my stateless application
  • troubleshoot why my kruise-manager pod is failing
  • create a sidecarset for automatic sidecar injection
  • check if openkruise is properly configured in kubesphere

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-openkruise ~/.claude/skills/kubesphere-openkruise

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-openkruise .claude/skills/kubesphere-openkruise

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