flux
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with Flux CD — debugging live clusters, writing/auditing Flux resources, or asking Flux CD questions. Routes to 3 sub-skills depending on the task.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- vibecook-dev/fluxtheir own version, first seen Nov 8, 2026
- AnthonyPoschen/agent-skillstheir own version, first seen Nov 1, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- brentmercado/flux-skill-evolutiontheir own version, first seen May 30, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- simota/agent-skills★ 99same name
- AnthonyPoschen/agent-skills★ 2same name
- vibecook-dev/flux★ 2same name
- brentmercado/flux-skill-evolution★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Repo (static): Write new Flux YAML, understand CRD fields, audit existing repo → gitops-knowledge for reference, gitops-repo-audit for …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flux CD
Skill router. Pick the right sub-skill based on what user is doing.
Which Sub-Skill?
| User wants to... | Load skill | What it does |
| Debug a failing HelmRelease/Kustomization on a live cluster | gitops-cluster-debug | Inspects Flux resource status, controller logs, traces dependency chains on live K8s |
| Write/understand Flux CRDs, generate YAML, ask what a concept means | gitops-knowledge | CRD schemas, YAML patterns, API versions, Flux concepts, FluxInstance/ResourceSet |
| Audit a GitOps repo for best practices, deprecated APIs, security | gitops-repo-audit | Scans repo files, validates schemas, flags deprecated APIs, checks RBAC/secrets |
Two Domains
Cluster (live): HelmRelease stuck, Kustomization failing, FluxInstance broken → gitops-cluster-debug
Repo (static): Write new Flux YAML, understand CRD fields, audit existing repo → gitops-knowledge for reference, gitops-repo-audit for validation
Common Task Map
| Task | Sub-skill |
| "Why is my HelmRelease failing?" | gitops-cluster-debug |
| "Show me how to write a ResourceSet" | gitops-knowledge |
| "Audit my GitOps repo" | gitops-repo-audit |
| "What API version for Flux CRDs?" | gitops-knowledge |
| "Check if my repo has deprecated APIs" | gitops-repo-audit |
| "FluxInstance not ready" | gitops-cluster-debug |
| "Explain OCI-based GitOps" | gitops-knowledge |
| "Check HelmRelease valuesFrom refs" | gitops-repo-audit |
| "Monitor reconciliation, set up alerts" | gitops-knowledge |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

