RepoAI
Browse MCPs

Openpitrix

94TrustedInstructions only

Application lifecycle management for KubeSphere repositories, templates, and releases.

What it does

Adding this skill equips your assistant to interpret technical inquiries regarding KubeSphere application management. It helps the assistant navigate the distinction between platform-level store operations and workspace-specific deployment tasks, identifying the appropriate resources and controllers involved in each flow.

The assistant gains the ability to map user questions to specific object types like repositories, templates, and releases. It understands the underlying architecture, allowing it to provide context-aware guidance when users encounter sync issues, need to troubleshoot installation states, or manage version metadata within the system.

When it earns its place

Reach for it when…

Apply this when users need to perform administrative tasks within KubeSphere, such as synchronizing Helm repositories, verifying the status of an application release, or managing the lifecycle of custom application templates across different workspaces.

Look elsewhere when…

This is not intended for managing raw Kubernetes workloads or standard Helm charts outside of the KubeSphere OpenPitrix application framework. Avoid using it for general Linux system administration, database troubleshooting, or managing network policies that do not directly involve the App Store resource hierarchy.

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.

  • why is my helm repository failing to sync in kubesphere
  • how do i publish a new version of my custom application template
  • check the status of an application release in my workspace
  • where are the application templates stored in the extension namespace

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

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

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

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

How skills and MCP servers differ →