flux

Routes Flux CD tasks to sub-skills for cluster debugging, CRD knowledge, and repo auditing.

4|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill flux-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flux
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/flux
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill flux-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Flux CD spans three distinct activities—debugging live clusters, writing or understanding Flux resources, and auditing GitOps repositories—and choosing the wrong approach wastes time. This Skill acts as a router that directs each Flux CD task to the correct specialized sub-skill. ## Core Features & Use Cases - Task Routing: Maps user intent to one of three sub-skills: gitops-cluster-debug, gitops-knowledge, or gitops-repo-audit. - Live Cluster Debugging: Routes HelmRelease failures, stuck Kustomizations, and broken FluxInstances to live-cluster inspection workflows. - Repo and Knowledge Workflows: Directs YAML authoring, CRD schema questions, deprecated API checks, and RBAC/secrets audits to the appropriate static-analysis sub-skill. - Use Case: When you ask "Why is my HelmRelease failing?", the router loads gitops-cluster-debug to inspect Flux resource status, controller logs, and dependency chains on the live cluster. ## Quick Start Ask the agent to debug a failing HelmRelease on your cluster and it will route the request to the correct Flux sub-skill.

Frequently Asked Questions about flux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing HelmRelease in Flux CD?▼

Use the gitops-cluster-debug sub-skill, which inspects Flux resource status, controller logs, and dependency chains on the live Kubernetes cluster. It handles stuck HelmReleases, failing Kustomizations, and broken FluxInstances.

How do I audit a GitOps repo for deprecated Flux APIs?▼

Use the gitops-repo-audit sub-skill, which scans repository files, validates schemas, flags deprecated API versions, and checks RBAC and secrets configurations against best practices.

What API version should I use for Flux CRDs?▼

The gitops-knowledge sub-skill covers CRD schemas, API versions, and YAML patterns for Flux resources including FluxInstance and ResourceSet. Ask it for the current API version of any Flux CRD.

When should I use cluster debugging versus repo auditing in Flux?▼

Use gitops-cluster-debug for live cluster issues like failing reconciliations, and gitops-repo-audit for static analysis of repository files. The router distinguishes between the live cluster domain and the static repo domain.

Can this skill write Flux YAML for ResourceSets?▼

Yes, requests to write or understand Flux YAML are routed to gitops-knowledge, which provides CRD schemas, YAML patterns, and explanations of concepts like OCI-based GitOps and ResourceSets.