GitOps Agent Skills

GitOps Agent Skills are the official agent skills for Flux CD, written by the Flux project maintainers. They give your agent working knowledge of Flux, Kubernetes and GitOps practice, and your agent picks the right one from what you ask. What its skills teach your agent - gitops-knowledge: answer Flux questions and generate up-to-date YAML for every Flux resource (HelmRelease, Kustomization, GitRepository, OCIRepository, ResourceSet, FluxInstance and more), with bundled schemas and references on sources, image automation, notifications, repository patterns and the Flux Operator APIs - gitops-repo-audit: audit a GitOps repository's local files for structure, security and operational readiness. It validates manifests and rendered Kustomize overlays against schemas, finds deprecated Flux APIs, reviews secrets management, source authentication, RBAC and multi-tenancy, and writes a prioritized report - gitops-cluster-debug: troubleshoot Flux on a live cluster through the Flux Operator MCP server: installation health, failing HelmReleases and Kustomizations, controller logs and dependency chains How it connects - Install the plugin from the Flux marketplace (fluxcd/agent-skills). It also sets up the Flux Schema Catalog MCP server, which lets your agent look up real Kubernetes and cloud native field names when it writes or reviews manifests. - The skills expect the flux CLI and the flux-schema plugin on your machine. - Cluster debugging needs the flux-operator-mcp server with your kubeconfig, added separately. Run it with --read-only and your agent can't change the cluster. - The Flux team documents Claude Code, Codex and GitHub Copilot, and the skills also install with npx skills add fluxcd/agent-skills or the Flux Operator CLI, which checks the cosign signature. Good to know - The MCP server masks Kubernetes Secrets: your agent sees key names, never values. - The debug skill only applies changes to the cluster when you explicitly ask, and warns that Flux reverts manual edits to resources it manages. - Manifests come out best in a repository with an AGENTS.md or CLAUDE.md describing your clusters, structure and secret management. - Apache-2.0 licensed. The maintainers are asking for feedback on accuracy and gaps.

• “What's the recommended GitOps structure for a multi-cluster fleet?”

  Copy

• “Generate a HelmRelease for oci://ghcr.io/my-org/frontend, and a Kustomization to deploy it in the staging cluster.”

  Copy

• “How do I set up preview environments for pull requests with Flux Operator?”

  Copy

• “Audit the current repo and provide a GitOps report.”

  Copy

• “Check the Flux installation on my current cluster.”

  Copy

• “Debug the failing HelmRelease podinfo in the apps namespace.”