RepoAI
Browse MCPs

KubeSphere Multi Tenant Management

94TrustedShips scripts

Automated workspace and user provisioning for KubeSphere environments.

What it does

Kubesphere Multi Tenant Management integrates into your assistant to handle routine administrative tasks within your cluster. It streamlines the creation of workspaces, projects, and the assignment of standard access roles, ensuring that your organizational structure remains consistent without requiring manual API navigation for every addition. By managing these lifecycle events through your assistant, you maintain a clearer audit trail of resource allocation. The skill focuses on standard provisioning and query operations, adhering to predefined security protocols that favor built-in roles. It effectively turns high-level requests into precise API calls, allowing for faster setup of multi-tenant environments while preventing accidental deletion or unauthorized custom role configurations.

When it earns its place

Reach for it when…

Apply this skill when you need to onboard new team members to specific projects, initialize new workspaces for different departments, or verify current access levels across your infrastructure using built-in KubeSphere roles.

Look elsewhere when…

Do not attempt to use this for cleanup tasks such as deleting projects, removing users, or modifying resource lifecycle states, as those actions are explicitly restricted to the web console to ensure safety. It is also unsuitable for designing custom permission schemas, as it strictly enforces standard roles.

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.

  • create a new workspace for the finance team
  • add developer smith to the project alpha
  • check which roles are assigned to the marketing workspace
  • provision a new project for the backend service

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-multi-tenant-management ~/.claude/skills/kubesphere-multi-tenant-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-multi-tenant-management .claude/skills/kubesphere-multi-tenant-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 Multi Tenant Management changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →