Skip to content
Diagnosis · Code

gitops-cluster-debug

Debug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads…

From Fluxgithub.com/fluxcd/agent-skills ↗Source ↗Apache-2.0212 repo stars

Examining code for the line that is wrong

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 2 Oct 2026
On the repository’s main branch.

What it does

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.

When your AI uses it

Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull…

You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.

    How we know

    Listed the 23 files in the skill’s folder on GitHub; none is a script or program.

  • No known risk pattern found

    Launch7’s automated check read all 23 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit 0d1fa6c by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to fluxcd/agent-skills: 2026-10-02 (3 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

  • commit-assisted-by

    Add an Assisted-by: <agent-name>/<model-id> git trailer to commits made during an AI-assisted coding session.

    From FluxIncludes 1 script
  • flux-controller-minor-releases

    Run the upstream Flux controller minor release procedure for helm-controller, image-automation-controller, image-reflector-controller,…

    From FluxContacts outside web addresses
  • flux-controller-patch-releases

    Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller,…

    From FluxRuns terminal commands
  • gitops-knowledge

    Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging).

    From FluxAdds a connector
  • gitops-repo-audit

    Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated…

    From FluxIncludes 3 scripts