Individual skill
gitops-cluster-debug
Debug and troubleshoot Flux CD on live Kubernetes clusters via the Flux MCP server — inspects Flux resource status, events and controller logs, traces workloads back to the Flux objects and sources that deliver them, previews what a GitOps change will do on the cluster, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, crashing or misbehaving workloads deployed by Flux, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, want to know what a local manifest change would modify on the cluster before committing, or need live cluster Flux Operator troubleshooting.
skills/gitops-cluster-debug/SKILL.md
Source commit 25da0ed5bfdd1d8f779ef79c2c7e336781978d87
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 244
- Repository last updated
- Nov 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- gitops Repository topic
- skills Repository topic
- agent-skills Repository topic
- fluxcd Repository topic
- devops Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesSKILL.mdcore · 23,888 bytesassets/schemas/alert-notification-v1.fields.txtdoc · 2,505 bytesassets/schemas/alert-notification-v1beta3.fields.txtdoc · 2,680 bytesassets/schemas/artifactgenerator-source-v1beta1.fields.txtdoc · 14,603 bytesassets/schemas/bucket-source-v1.fields.txtdoc · 8,152 bytesassets/schemas/externalartifact-source-v1.fields.txtdoc · 4,180 bytesassets/schemas/fluxinstance-fluxcd-v1.fields.txtdoc · 20,964 bytesassets/schemas/fluxreport-fluxcd-v1.fields.txtdoc · 5,523 bytesassets/schemas/gitrepository-source-v1.fields.txtdoc · 11,263 bytesassets/schemas/helmchart-source-v1.fields.txtdoc · 7,612 bytesassets/schemas/helmrelease-helm-v2.fields.txtdoc · 46,322 bytesassets/schemas/helmrepository-source-v1.fields.txtdoc · 7,537 bytesassets/schemas/imagepolicy-image-v1.fields.txtdoc · 5,783 bytesassets/schemas/imagerepository-image-v1.fields.txtdoc · 6,527 bytesassets/schemas/imageupdateautomation-image-v1.fields.txtdoc · 10,643 bytesassets/schemas/kustomization-kustomize-v1.fields.txtdoc · 20,723 bytesassets/schemas/ocirepository-source-v1.fields.txtdoc · 10,427 bytesassets/schemas/provider-notification-v1.fields.txtdoc · 3,551 bytesassets/schemas/provider-notification-v1beta3.fields.txtdoc · 3,954 bytesassets/schemas/receiver-notification-v1.fields.txtdoc · 8,143 bytesassets/schemas/resourceset-fluxcd-v1.fields.txtdoc · 10,874 bytesassets/schemas/resourcesetinputprovider-fluxcd-v1.fields.txtdoc · 10,622 bytesevals/evals.jsonasset · 5,681 bytesreferences/flux-crds.mddoc · 14,977 bytesreferences/troubleshooting.mddoc · 12,043 bytes
Read excerpt
# Flux Cluster Debugger
You are a Flux cluster debugger specialized in troubleshooting GitOps pipelines on live
Kubernetes clusters. You use the `flux-operator-mcp` MCP tools to connect to clusters,
fetch Flux and Kubernetes resources, trace delivery pipelines, analyze status conditions,
events and logs, and identify root causes.
## MCP Tools
The server exposes read-only tools in every mode and write tools only when it is not started
with `--read-only`. Check which tools you actually have before planning an action.
| Purpose | Tool | Mode |
|---|---|---|