manage-cluster SKILL.md skillA
manage-cluster from gke-labs/kube-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gke-labs/kube-agents/manage-cluster@git:20261016.b3c83b3Pins git:20261016.b3c83b3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gke-labs/kube-agents
- Path
agents/platform/skills/manage-cluster/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261016.b3c83b3, committed Oct 16, 2026
- First version recorded
- Jul 28, 2026
- Size
- 5,212 bytes
- Repository stars
- 124
- License
- Apache-2.0
Bring an existing GKE cluster under management on user request (e.g. "manage my cluster <name> in <location>") by creating its Cluster Agent profile, or take one out of management by excluding it. Use whenever a user asks to manage/onboard/watch a specific existing cluster, or to stop managing, exclude or offboard one.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Manage Cluster Skill
When a user asks you to **manage** (onboard / start watching) a specific existing GKE cluster — e.g. _"manage my cluster `payments-prod` in `us-central1`"_ — bring it under management by creating its **Cluster Agent profile**. After this, the cluster gets a per-cluster agent and is delegable via the kanban board.
This is the explicit, user-driven counterpart to onboarding-time creation (`gke-cluster-creation`). It is safe to run repeatedly (idempotent).
## Steps
1. **Gather the target.** You need `project`, `cluster`, and `location`.
- Use any values the user gave. If the user omits the **project**, resolve it:
- default to the platform's active project: `gcloud config get-value project`; then
- confirm the cluster exists in that project (next step). If it isn't there, or the name is ambiguous, run `gcloud container clusters list --format="value(name,location,resourceLabels)"` (optionally `--project <p>`) to locate it, and ask the user only if still ambiguous.
2. **Verify the cluster exists** before creating a profile (clean error instead of a half-scaffold):
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/manage-cluster@sha256:6f060fcf64379086The line at the top of this page pins the label git:20261016.b3c83b3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4jroeybxradnh27p)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jul 28, 2026 and Oct 16, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.b3c83b3 latest | 2026-10-16 | b3c83b3 | 5,212 B | A | view · diff |
| git:20261016.adf067f | 2026-10-16 | adf067f | 5,164 B | A | view · diff |
| git:20261015.5895c3f | 2026-10-15 | 5895c3f | 5,066 B | A | view · diff |
| git:20260923.0dcc0b4 | 2026-09-23 | 0dcc0b4 | 3,532 B | A | view · diff |
| git:20260820.e0ddc12 | 2026-08-20 | e0ddc12 | 3,380 B | A | view · diff |
| git:20260807.d47bdf1 | 2026-08-07 | d47bdf1 | 3,404 B | A | view · diff |
| git:20260728.aca5b5c | 2026-07-28 | aca5b5c | 3,404 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5212 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gke-labs/kube-agents · 124 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4jroeybxradnh27p GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/manage-cluster GET https://markdownregistry.com/api/v1/blob/6f060fcf64379086cd2ef38709c587bcbc0b9346f2ea4abcdc081414af397eba
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.