Skip to content
Back to search

fluxcd

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fluxcd-agent-skills/badge.svg)](/listings/fluxcd-agent-skills)

HTML

<a href="/listings/fluxcd-agent-skills"><img src="/api/listings/fluxcd-agent-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Using Flux CLI

Install the operator plugin with:

flux plugin install operator

Navigate to your GitOps repository root and run:

flux operator skills install ghcr.io/fluxcd/agent-skills --agent claude-code

The [Flux Operator](https://fluxoperator.dev/) CLI verifies the cosign signature (validating that the OCI artifact is published by the Flux team) and extracts the skills in the repo root at `.agents/skills`.

The `--agent` flag creates per-skill symlinks from agent-specific directories to the canonical location. If your agent supports the conventional `.agents/skills` path, you can omit the `--agent` flag.

To update the skills run `flux operator skills update`.

Using NPX

Install the skills with Vercel's skills tool:

npx skills add fluxcd/agent-skills

Using Claude Code

For Claude Code, add the marketplace and install the skills with:

/plugin marketplace add fluxcd/agent-skills
/plugin install gitops-skills@fluxcd

Using Codex

Add the FluxCD marketplace and install the plugin with:

codex plugin marketplace add fluxcd/agent-skills
codex plugin add gitops-skills@fluxcd

Start a new Codex thread after installation so the skills are discovered.

Using GitHub Copilot

For Copilot CLI, add the FluxCD marketplace and install the plugin with:

copilot plugin marketplace add fluxcd/agent-skills
copilot plugin install gitops-skills@fluxcd

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 29 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "fluxcd",
  3. "owner": {
  4. "name": "The Flux authors",
  5. "email": "cncf-flux-dev@lists.cncf.io"
  6. },
  7. "metadata": {
  8. "description": "AI skills for GitOps engineering with Flux CD and Kubernetes",
  9. "version": "0.4.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "gitops-skills",
  14. "description": "Collection of GitOps engineering skills for Flux CD knowledge, manifest generation, repository auditing, and cluster debugging",
  15. "source": "./",
  16. "strict": false,
  17. "category": "Development",
  18. "skills": [
  19. "./skills/gitops-knowledge",
  20. "./skills/gitops-repo-audit",
  21. "./skills/gitops-cluster-debug"
  22. ],
  23. "agents": [
  24. "./agents/claude-code/fluxcd.md"
  25. ],
  26. "mcpServers": "./.mcp.json"
  27. }
  28. ]
  29. }
README.md · README · 208 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # GitOps Agent Skills
  2. [![release](https://img.shields.io/github/release/fluxcd/agent-skills/all.svg)](https://github.com/fluxcd/agent-skills/releases)
  3. [![license](https://img.shields.io/github/license/fluxcd/agent-skills.svg)](https://github.com/fluxcd/agent-skills/blob/main/LICENSE)
  4. A collection of reusable skills that give AI Agents expertise in Flux CD,
  5. Kubernetes, and GitOps best practices for generating manifests, answering Flux questions,
  6. auditing repository structure, security, operational readiness, and debugging live
  7. cluster installations.
  8. > [!NOTE]
  9. > These are the official AI Skills for Flux CD, developed by the Flux project maintainers.
  10. > We are looking for users to try them out and provide feedback on accuracy, usefulness, and any gaps when steering Agents through GitOps tasks.
  11. > If you have suggestions for improvements or new skills, please [open an issue](https://github.com/fluxcd/agent-skills/issues/new).
  12. ## Install
  13. ### Using Flux CLI
  14. Install the operator plugin with:
  15. ```shell
  16. flux plugin install operator
  17. ```
  18. Navigate to your GitOps repository root and run:
  19. ```shell
  20. flux operator skills install ghcr.io/fluxcd/agent-skills --agent claude-code
  21. ```
  22. The [Flux Operator](https://fluxoperator.dev/) CLI verifies the cosign signature
  23. (validating that the OCI artifact is published by the Flux team)
  24. and extracts the skills in the repo root at `.agents/skills`.
  25. The `--agent` flag creates per-skill symlinks from agent-specific directories to the canonical
  26. location. If your agent supports the conventional `.agents/skills` path, you can omit the `--agent` flag.
  27. To update the skills run `flux operator skills update`.
  28. ### Using NPX
  29. Install the skills with Vercel's skills tool:
  30. ```shell
  31. npx skills add fluxcd/agent-skills
  32. ```
  33. ### Using Claude Code
  34. For Claude Code, add the marketplace and install the skills with:
  35. ```shell
  36. /plugin marketplace add fluxcd/agent-skills
  37. /plugin install gitops-skills@fluxcd
  38. ```
  39. ### Using Codex
  40. Add the FluxCD marketplace and install the plugin with:
  41. ```shell
  42. codex plugin marketplace add fluxcd/agent-skills
  43. codex plugin add gitops-skills@fluxcd
  44. ```
  45. Start a new Codex thread after installation so the skills are discovered.
  46. ### Using GitHub Copilot
  47. For Copilot CLI, add the FluxCD marketplace and install the plugin with:
  48. ```shell
  49. copilot plugin marketplace add fluxcd/agent-skills
  50. copilot plugin install gitops-skills@fluxcd
  51. ```
  52. ## Prerequisites
  53. The skills in this repository rely on the following tools being available in the environment:
  54. - `flux` v2.10 or later for dry running, deprecated API detection and manifest generation
  55. - `flux-schema` for discovering and validating Kubernetes manifests (install with `flux plugin install schema`)
  56. - `flux-operator-mcp` for debugging Flux on live Kubernetes clusters (required by `gitops-cluster-debug`)
  57. A [Brewfile](https://raw.githubusercontent.com/fluxcd/agent-skills/refs/heads/main/Brewfile) is provided for easy installation of the prerequisites on macOS.
  58. ## Kubernetes Ecosystem Schema Catalog MCP
  59. The skills are complemented by the [Flux Schema Catalog](https://schemas.fluxoperator.dev/) MCP server,
  60. which gives the agent access to JSON schemas and field indexes for
  61. core Kubernetes, OpenShift and a broad set of Cloud Native projects.
  62. The AI Agent uses it to look up the real kinds, field names, types, constraints,
  63. when generating or reviewing custom resources.
  64. When installing the skills as a plugin (Claude Code, Copilot or Codex), the schema MCP server is
  65. configured automatically. For the other installation methods, it can be added manually.
  66. See the [schema catalog documentation](https://schemas.fluxoperator.dev/agents/) for more details.
  67. ## Available Skills
  68. The skills are designed to work together and the agent automatically selects the right one
  69. based on context: `gitops-knowledge` for answering Flux questions and generating manifests,
  70. `gitops-repo-audit` for validating and auditing repository contents,
  71. and `gitops-cluster-debug` for troubleshooting live clusters.
  72. ### gitops-knowledge
  73. Answers questions about Flux CD and generates up-to-date YAML for all Flux custom resources.
  74. Bundled with OpenAPI schemas for every Flux resource and reference documentation covering
  75. sources, HelmRelease, Kustomization, ResourceSets, image automation, notifications,
  76. repository patterns, and the Flux Operator APIs.
  77. To invoke the skill, use the following prompts:
  78. ```text
  79. What's the recommended GitOps structure for a multi-cluster fleet?
  80. ```
  81. ```text
  82. Generate a HelmRelease for oci://ghcr.io/my-org/frontend,
  83. and a Kustomization to deploy it in the staging cluster.
  84. ```
  85. ```text
  86. How do I set up preview environments for pull requests with Flux Operator?
  87. ```
  88. This skill works best in the context of a GitOps repository that contains an `AGENTS.md`
  89. or `CLAUDE.md` with details about your organization's structure, cluster topology,
  90. and secret management approach. The agent combines the skill's reference files with
  91. the repository context to generate manifests tailored to your setup.
  92. ### gitops-repo-audit
  93. Audits Flux GitOps repositories for structure, security, and operational best practices.
  94. Validates manifests against OpenAPI schemas, detects deprecated API versions,
  95. reviews secrets management, source authentication, RBAC and multi-tenancy configuration,
  96. and generates a structured report with prioritized recommendations.
  97. To invoke the skill, use the following prompt:
  98. ```text
  99. Audit the current repo and provide a GitOps report.
  100. ```
  101. In Claude Code, you can also invoke the skill directly with `/gitops-repo-audit`.
  102. To run only the manifest validation phase, use:
  103. ```text
  104. Validate my repo without auditing it.
  105. ```
  106. This prompt can be used when changes have been made to the repository,
  107. and you want to re-run the validation checks without performing a full audit.
  108. You can also use the skill to audit only the files with changes:
  109. ```text
  110. Run a GitOps audit only on the files with changes.
  111. ```
  112. > [!NOTE]
  113. > Check the [Claude Code Guide](docs/claude-agent-setup.md) for how to orchestrate Flux CD sub-agents and generate audit reports in HTML format.
  114. ### gitops-cluster-debug
  115. Debugs and troubleshoots Flux CD on live Kubernetes clusters using the
  116. [Flux MCP](https://fluxoperator.dev/mcp-server/) server. Inspects Flux installation health, diagnoses
  117. HelmRelease and Kustomization failures, traces crashing workloads back to the Flux objects that deliver them,
  118. analyzes events and logs, and previews what a local manifest change will do on the cluster before you commit it.
  119. To invoke the skill, use the following prompts:
  120. ```text
  121. Check the Flux installation on my current cluster.
  122. ```
  123. ```text
  124. Debug the failing HelmRelease podinfo in the apps namespace.
  125. ```
  126. ```text
  127. Troubleshoot the Kustomization flux-system/infra-controllers in the staging cluster.
  128. ```
  129. ```text
  130. I changed the manifests in apps/podinfo, what will this do on the cluster?
  131. ```
  132. The `flux-operator-mcp` server can be configured in Claude Code with:
  133. ```bash
  134. claude mcp add --scope project --transport stdio flux-operator-mcp \
  135. --env KUBECONFIG=$HOME/.kube/config \
  136. -- flux-operator-mcp serve --read-only
  137. ```
  138. Note that the `--read-only` flag will prevent the Agent from making any changes to the cluster.
  139. The MCP server masks Kubernetes Secrets, the Agent receives only the data key names without values.
  140. ## 3rd-Party Indexing
  141. The Flux skills are indexed by various 3rd-party services:
  142. - [tessl.io/registry/skills/github/fluxcd/agent-skills](https://tessl.io/registry/skills/github/fluxcd/agent-skills)
  143. - [skills.sh/fluxcd/agent-skills](https://skills.sh/fluxcd/agent-skills)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.