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 controller logs, traces dependency chains, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, or need live cluster Flux Operator troubleshooting.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tightly structured, highly actionable debugging playbook with clear sequenced workflows, validation checkpoints, and proper progressive disclosure into verified reference files; the only drag is the duplicated HelmRelease/Kustomization workflows.

Suggestions

Collapse Workflows 2 and 3 into a single parameterized workflow (e.g., a generic 'HelmRelease/Kustomization debugging' procedure) to remove the near-identical duplication and trim tokens.

Add a brief explicit verification step at the end of the read-only workflows (e.g., 'Confirm the traced dependency chain is complete before writing the report') to make the existing feedback loop explicit in every workflow, not just Workflow 7.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely free of concepts Claude already knows, but Workflows 2 and 3 are near-duplicates (the HelmRelease and Kustomization procedures differ only in kind names), which is padding that could be unified.	4 / 5
Actionability	Every workflow names exact MCP tool calls and the precise fields/conditions to inspect (e.g. 'status.latestImage', '.spec.git.push.branch', 'chartRef or sourceRef'), giving fully actionable, copy-ready instruction guidance.	5 / 5
Workflow Clarity	Eight numbered workflows are clearly sequenced with explicit verification checkpoints ('Verify the FluxInstance reports Ready: True'), feedback loops (test-event + log watch in Workflow 7), and a guardrailed destructive action ('Do not apply resources unless explicitly requested').	5 / 5
Progressive Disclosure	The body is a well-signaled overview that points one level deep to real bundle files — 'references/flux-crds.md', 'references/troubleshooting.md', and the 'assets/schemas/*.fields.txt' field index (verified present) — with a dedicated 'Loading References' section stating when to load each.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, concise, and hits the top anchor on every dimension: concrete capabilities, natural trigger terms, explicit what-and-when guidance, and a distinct, low-conflict niche.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks' — giving comprehensive, non-abstract coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (debug/troubleshoot Flux CD via the Flux MCP server with the four named actions) and 'when' ('Use when users report...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural user-facing phrases are densely packed — 'failing, stuck, or not-ready Flux resources', 'reconciliation errors', 'artifact pull failures', 'image automation not updating tags', 'alerts or webhooks not being delivered' — covering the common ways users describe these problems.	5 / 5
Distinctiveness Conflict Risk	A clear niche — live-cluster Flux CD debugging through the Flux MCP server — sharpened by the explicit '(not local repo files)' disambiguator, minimizing overlap with repo-based Flux or general Kubernetes skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 19 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 20 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: fluxcd/agent-skills
Path: skills/gitops-cluster-debug/SKILL.md
Commit: 7fcbb9b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.