GitOps Agent Skills plugin
Official Flux CD skills: Flux answers, manifest generation, GitOps repository audit and debugging of live-cluster failures
- 244 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The debugging skill reads live cluster state, logs and events through Flux MCP
- The skills run flux and flux-schema on your manifests
- Enable Flux MCP with --read-only, otherwise the agent may change the cluster
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/gitops-agent-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The debugging skill reads live cluster state, logs and events through Flux MCP
- The skills run flux and flux-schema on your manifests
- Enable Flux MCP with --read-only, otherwise the agent may change the cluster
This is third-party code. Review the repository files before installing.
What it does
GitOps Agent Skills is a set of skills from the Flux CD maintainers. The agent picks the right one from context. `gitops-knowledge` answers Flux questions and generates current YAML for every Flux resource. It ships with OpenAPI schemas and references for sources, HelmRelease, Kustomization, ResourceSets, image automation and notifications. `gitops-repo-audit` checks a repository's structure and security: it validates manifests against schemas, finds deprecated API versions, reviews secrets management, source authentication, RBAC and multi-tenancy, then returns a prioritized report. `gitops-cluster-debug` works through Flux MCP and diagnoses the Flux installation, failing HelmReleases and Kustomizations, events and logs, and previews what a manifest change would do on the cluster before you commit. Installed as a plugin (Claude Code, Copilot, Codex), it also wires in the Kubernetes schema catalog MCP server.
Who it is for. Platform engineers and SREs who run Kubernetes clusters with Flux and want the agent to know current Flux resources and APIs.
Good fit when
- You need a HelmRelease for an OCI image and a Kustomization for the staging cluster
- A GitOps repository needs a check: schemas, deprecated APIs, secrets, RBAC
- A HelmRelease is stuck in an error state and nobody found the cause in the logs
- Before committing you want to know what a manifest change will do on the cluster
- You need a repository layout for a fleet of several clusters
Not a fit when
- The cluster runs another GitOps tool such as Argo CD: the skills are written for Flux
- You need to change the cluster: debugging connects to Flux MCP read-only by default
- flux and flux-schema are not installed: part of the skills relies on these tools
Example request
Audit this repository as GitOps and show a prioritized report on secrets and RBACLimitations
The skills need flux 2.10 or later, flux-schema for manifest validation and flux-operator-mcp for live-cluster debugging (required by gitops-cluster-debug). On macOS the Brewfile in the repository installs the tools. Answer quality depends on the repository: the knowledge skill works best when an AGENTS.md or CLAUDE.md with cluster topology and secrets approach sits alongside. The authors ask for feedback on accuracy and gaps.
How to disable. Remove the gitops-skills plugin through /plugin or delete .agents/skills from the repository. To remove Flux MCP run claude mcp remove flux-operator-mcp.
FAQ
Which skills are included?
Three: gitops-knowledge answers questions and generates manifests, gitops-repo-audit audits the repository, gitops-cluster-debug troubleshoots a live cluster.
How do I install the skills with the Flux CLI?
Run flux plugin install operator, then in the repository root flux operator skills install ghcr.io/fluxcd/agent-skills --agent claude-code. The CLI verifies the cosign signature and extracts the skills into .agents/skills.
Can the agent change the cluster?
With Flux MCP connected using the --read-only flag the agent cannot make changes. The flag keeps debugging safe.
How do I update the skills?
With the Flux CLI: flux operator skills update. The plugin updates through the usual Claude Code, Codex or Copilot means.
Which agents are supported?
Claude Code, Codex and GitHub Copilot through the plugin marketplace, others through npx skills add or the Flux CLI. The repository includes manifests for all three.
Discussion
No questions or reviews yet.
Related
PluginsKubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
Flux CD MCP server from the Flux Operator project: an agent debugs failed rollouts in Kubernetes, compares clusters and applies manifests on request
A set of agents for Kubernetes and GKE: scheduled fleet audits, fixes through pull requests, replies in Google Chat and Slack
A collection of Copilot skills and agents for Azure, API Management, Terraform and diagrams, installed via the skills CLI or APM
A skill and plugin for Git and GitHub: branches, Conventional Commits and a pull request path to a green merge.
OpenCode agents on Kubernetes: tasks and shared settings live in manifests, and kubeoc attaches to a live agent
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| GitOps Agent Skills (this card) | yes | 244 | ||
| Flux MCP Server | yes | not required | 789 | an MCP server for operating Flux; the skills add knowledge, repository audit and debugging workflows |
| Kubernetes Skill | no | 477 | a general Kubernetes skill; this one covers Flux CD and GitOps specifically |
README in short
The skills are presented as the Flux team's official set. It covers four install routes (Flux CLI, npx, Claude Code, Codex and Copilot plugins), required tools, the schema catalog MCP server and three skills with sample prompts.