RepoAI
Browse MCPs

KubeSphere DevOps Tenant

94TrustedInstructions only

Management of DevOps projects for users restricted to namespace-level permissions.

What it does

This skill provides a framework for interacting with KubeSphere DevOps resources when you do not possess cluster-admin privileges. It shifts the assistant's focus toward utilizing the native KubeSphere API layer rather than attempting to interface with underlying Jenkins configurations or hidden system secrets.

By installing this, your assistant will prioritize endpoint structures that respect namespace-scoped access control. It ensures that any automated pipeline management or project inquiries are performed through the authorized KubeSphere OAuth flow, maintaining compliance with environment security constraints.

When it earns its place

Reach for it when…

Install this when you need to automate pipeline triggers, list project resources, or manage DevOps tasks as a project administrator who lacks broad cluster access. It is appropriate for developers building CI/CD tooling or custom dashboard integrations scoped to specific Kubernetes namespaces.

Look elsewhere when…

This is not intended for cluster administrators who require full system-wide visibility or direct interaction with Jenkins controllers. It should not be used if you need to manage global secrets or infrastructure-level Jenkins configurations, as these tasks require higher-level access that bypasses these namespace restrictions.

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.

  • How do I list my DevOps projects via the KubeSphere API
  • Show me the steps to trigger a pipeline in my namespace
  • How to get an authentication token for DevOps tasks
  • Explain how to manage pipelines without cluster-admin access

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

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

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 DevOps Tenant changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →