RepoAI
Browse MCPs

KubeSphere DevOps Credentials

94TrustedInstructions only

Kubernetes secret configuration for KubeSphere DevOps pipeline authentication access.

What it does

Installing this skill equips your assistant to generate and validate Kubernetes manifests tailored for the KubeSphere DevOps environment. It ensures that secrets intended for pipeline use are formatted with the specific labels, annotations, and resource types required by the system's internal controllers.

By utilizing this guidance, the assistant avoids common errors such as utilizing default opaque secret types, which prevents sync failures with Jenkins. It provides the necessary structure to manage SSH keys, basic authentication, and tokens, ensuring they are recognized by the KubeSphere platform.

When it earns its place

Reach for it when…

Use this skill when defining infrastructure-as-code for KubeSphere projects that require external connectivity, such as pulling code from Git providers, pushing to container registries, or interacting with third-party service APIs through pipeline tasks.

Look elsewhere when…

Do not use this for general Kubernetes secret management unrelated to the KubeSphere DevOps stack. It does not assist with the security hardening of existing clusters or the rotation of certificates that are managed natively by Kubernetes rather than the CI/CD controller layer.

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.

  • help me create a secret for my git repository in kubesphere
  • how should i format a basic auth credential for a devops project
  • generate a kubernetes manifest for a kubesphere ssh key
  • why are my pipeline secrets stuck in pending status 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-devops-credentials ~/.claude/skills/kubesphere-devops-credentials

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

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

How skills and MCP servers differ →