What is gitops-cluster-debug?

A troubleshooting tool for Flux CD, a system that keeps Kubernetes clusters in sync with files stored in Git. It examines live clusters, Flux resources, controller logs, dependencies, and installation health.

Investigate unhealthy Flux resources, inspect Kubernetes and controller status, trace dependency problems, and check whether Flux is installed and working correctly.

It helps find why a GitOps deployment is failing, stuck, or not ready without guessing from repository files alone. It connects the reported problem to the relevant cluster status and logs.

gitops-cluster-debug — Skill for Claude Code by fluxcd/agent-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add fluxcd/agent-skills --skill gitops-cluster-debug

Clone the repo

git clone --depth 1 https://github.com/fluxcd/agent-skills

Made for: Claude Code.

Or install gitops-skills, the plugin that ships this one along with the rest of its 3 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-cluster-debug/github.svg)](https://agentmods.dev/skills/fluxcd/agent-skills/gitops-cluster-debug)

Your own site

<a href="https://agentmods.dev/skills/fluxcd/agent-skills/gitops-cluster-debug"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-cluster-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fluxcd/agent-skills/gitops-cluster-debug"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-cluster-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,847 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 1 Oct 2026
Snyk warn 1 Oct 2026
NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 43
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 45
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00096	$0.03847
Opus 5.5	$0.00038	$0.01539
Sonnet 5.5	$0.00019	$0.00769
Haiku 4.5	$0.00010	$0.00385

Measured 1mo ago against content hash 04acf50a728e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitops-cluster-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

gitops-cluster-debug — 97% identical, 19 lines differ

skills/gitops-cluster-debug/SKILL.md · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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, analyze status conditions, inspect logs, and identify root causes.

General Rules

Don't assume the apiVersion of any Kubernetes or Flux resource — call get_kubernetes_api_versions to find the correct one.
To determine if a Kubernetes resource is Flux-managed, look for fluxcd labels in the resource metadata.
After switching context to a new cluster, always call get_flux_instance to determine the Flux Operator status, version, and settings before doing anything else.
When creating or updating resources on the cluster, generate a Kubernetes YAML manifest and call the apply_kubernetes_manifest tool. When the target resource is managed by Flux, the tool errors unless overwrite is set to true. Do not apply resources unless explicitly requested by the user. Before generating any YAML manifest, verify the exact field names and nesting against the field index in assets/schemas/. Index files follow the naming convention {kind}-{group}-{version}.fields.txt; each line is a dotted field path — grep by path prefix (e.g. grep '^spec\.' assets/schemas/kustomization-kustomize-v1.fields.txt) instead of reading the whole file (see the CRD reference table below).
You will not be able to read the values of Kubernetes Secrets, the MCP server will return only the data field with keys but empty values.

Cluster Context

If the user specifies a cluster name:

Call get_kubeconfig_contexts to list available contexts.
Find the context matching the user's cluster name.
Call set_kubeconfig_context to switch to it.
Call get_flux_instance to verify the Flux installation on that cluster.

If no cluster is specified, debug on the current context. Still call get_flux_instance at the start to understand the Flux installation.

Read the full file on GitHub · 258 lines

Files

What ships with it

22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 258 lines · 96 tokens per session scan A 04acf50a728e

Subscribe to this mod's changes

gitops-cluster-debug is a skill published in the GitHub repository fluxcd/agent-skills (233 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 3,847 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging DevOps and cloud agent-skills ai-agents fluxcd gitops skills

gke-workload-scaling-troubleshooting

Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…

google/skills · 170 tokens

gke-ai-troubleshooting-tpu-performance-degradation

Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (gcloud alpha mldiagnostics monitored-events / hypercomputecluster.googleapis.com/v1alpha) and 1-minute Cloud Monitoring system metrics (kubernetes.io/node/accelerator/).…

google/skills · 200 tokens

gke-ai-troubleshooting-jobset-interruption

Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…

google/skills · 83 tokens

gke-node-notready

Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…

google/skills · 112 tokens

jetpack-compose-performance

Diagnose and optimize Android Jetpack Compose UI code. Use this skill when analyzing performance bottlenecks of existing code to minimize recomposition overhead and prevent dropped frames and UI lag.

android/skills · 41 tokens

systematic-debugging

A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.

jnMetaCode/superpowers-zh · 24 tokens