Fluxcd
Inspect and operate Flux CD resources from the sandbox with the flux CLI. Use for Flux reconciliation, GitRepository/Kustomization/HelmRelease status, suspend/resume, and GitOps drift triage after kubectl has loaded the target kubeconfig.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Fluxcd when an AI agent needs a reusable SKILL.md workflow for this job: Inspect and operate Flux CD resources from the sandbox with the flux CLI. Use for Flux reconciliation, GitRepository/Kustomization/HelmRelease status, suspend/resume, and GitOps drift triage after kubectl has loaded the target kubeconfig.
When not to use it
Skip Fluxcd when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/fluxcd # Save SKILL.md to ~/.claude/skills/fluxcd/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/fluxcd/SKILL.md. For a shared project, commit the folder at .claude/skills/fluxcd/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Fluxcd skill for this task: Use Fluxcd when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Flux CD CLI
Use this skill when the user asks about Flux CD, GitOps reconciliation, Flux Kustomizations, HelmReleases, GitRepositories, ImageUpdateAutomation, or why a cluster is not applying changes from Git.
If `flux` is not on PATH, report that the sandbox runtime image does not bundle `flux`; do not spend the turn installing it.
Pick the target cluster context first (see the `kubectl` skill — its kubeconfig has a context for every reachable cluster) and pass it explicitly with `--context` on every flux command.
## Setup
```bash kubectl config get-contexts flux --context <context> version ```
If Flux might be installed in a non-default namespace, discover it first:
```bash kubectl get ns kubectl get deploy -A | grep -i flux ```
## Read-only First
Start with read-only checks:
```bash flux check flux get sources git -A flux get sources helm -A flux get kustomizations -A flux get helmreleases -A flux logs --all-namespaces --level=error --since=30m kubectl get events -A --sort-by=.lastTimestamp ```
For a specific object:
```bash flux get kustomization <name> -n <namespace> flux get helmrelease <name> -n <namespace> kubectl -n <namespace> describe kustomization/<name> kubectl -n <namespace> describe helmrelease/<name> ```
## Mutations
Ask for explicit confirmation before:
- `flux reconcile ...` - `flux suspend ...` - `flux resume ...` - `flux create ...` - `flux delete ...` - Any `kubectl patch/apply/delete` on Flux resources
Before reconciling or suspending/resuming, summarize the current cluster context, namespace, resource kind/name, and whether the operation can trigger a Helm upgrade, prune, or workload rollout.
## Common Operations
```bash # Reconcile source first, then the dependent workload. flux reconcile source git <source> -n <namespace> flux reconcile kustomization <name> -n <namespace> --with-source
# HelmRelease flux reconcile helmrelease <name> -n <namespace> --with-source
# Temporarily pause/resume reconciliation. flux suspend kustomization <name> -n <namespace> flux resume kustomization <name> -n <namespace> ```
## Safety
- Always pass `--context` explicitly — the kubeconfig deliberately sets no current-context. - Prefer `flux get ... -A` and `flux logs` before mutating. - Do not suspend broad sets of resources unless the user explicitly requests that scope. - Treat Flux changes as production deploy changes: they can roll pods, uninstall resources through prune, or update Helm releases.
Intended uses
- Use Fluxcd when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.