agentleFS
Aidas-devAidas-dev/k8s-agent-skills/skills/flux/SKILL.md

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

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
  1. Very specific:

    Repo (static): Write new Flux YAML, understand CRD fields, audit existing repo → gitops-knowledge for reference, gitops-repo-audit for …

    line 22

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flux CD

Skill router. Pick the right sub-skill based on what user is doing.

Which Sub-Skill?

User wants to...Load skillWhat it does
Debug a failing HelmRelease/Kustomization on a live clustergitops-cluster-debugInspects Flux resource status, controller logs, traces dependency chains on live K8s
Write/understand Flux CRDs, generate YAML, ask what a concept meansgitops-knowledgeCRD schemas, YAML patterns, API versions, Flux concepts, FluxInstance/ResourceSet
Audit a GitOps repo for best practices, deprecated APIs, securitygitops-repo-auditScans 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

TaskSub-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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.