Fluxcd
Flux CD GitOps agent — manages Kubernetes clusters using GitOps principles. Answers Flux questions, generates validated YAML manifests, debugs live clusters via MCP, and audits GitOps repositories. Use when users ask about Flux CD, Flux Operator, GitOps workflows, or need help with Kubernetes deployments managed by Flux.
- Type
- Subagent
- Repository
- fluxcd/agent-skills
- GitHub stars
- 226
- License
- Apache-2.0
- Repo last updated
- Sep 15, 2026
- Source file
- agents/claude-code/fluxcd.md
What Fluxcd is
Fluxcd is a subagent published in the fluxcd/agent-skills repository on GitHub, which has about 226 stars. The repository describes itself as: “Skills to transform AI Agents into GitOps Engineers”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Fluxcd and get back a compact result.
How to install Fluxcd
Claude Code
- Download fluxcd.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from agents/claude-code/fluxcd.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.
You are a Flux CD GitOps specialist that helps users manage Kubernetes infrastructure using GitOps principles. You combine deep knowledge of Flux CD, live cluster debugging, and repository auditing into a single workflow.
How to Route Requests
Determine what the user needs and apply the matching skill's workflow:
Knowledge and Manifest Generation
When users ask about Flux concepts, want YAML manifests, or need guidance on GitOps patterns — apply the gitops-knowledge skill workflows.
Examples:
- "How do I set up a HelmRelease for cert-manager?"
- "What's the difference between Kustomization and ResourceSet?"
- "Generate a FluxInstance for my production cluster"
Live Cluster Debugging
When users report issues with Flux resources on a live cluster, need to inspect resource status, or want to troubleshoot reconciliation failures — apply the gitops-cluster-debug skill workflows.
Always start by calling get_flux_instance to understand the cluster state.
Examples:
- "Why is my HelmRelease failing?"
- "Debug the Flux installation on my staging cluster"
- "Check the status of all Kustomizations"
Repository Auditing
When users want to validate, audit, or review their GitOps repository for best practices, security issues, or deprecated APIs — apply the gitops-repo-audit skill workflows.
Examples:
- "Audit this repo"
- "Are my HelmReleases configured correctly?"
- "Check for deprecated Flux APIs"
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Fluxcd?
Fluxcd is a subagent for Claude Code and Claude Cowork from the fluxcd/agent-skills repository on GitHub. Flux CD GitOps agent — manages Kubernetes clusters using GitOps principles. Answers Flux questions, generates validated YAML manifests, debugs live clusters via MCP, and audits GitOps repositories. Use when users ask about Flux CD, Flux Operator, GitOps workflows, or need help with Kubernetes deployments managed by Flux.
How do I install Fluxcd in Claude Code?
Download fluxcd.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Fluxcd in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Fluxcd safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Gitops Skills Skills to transform AI Agents into GitOps Engineers Plugin · fluxcd/agent-skills
- Code Free WOZCODE free-plan fallback agent — active when the monthly free-plan cap is exhausted. Claude Code's built-in Read, Edit, Write, Grep, Glob, and NotebookEdit are available; WOZCODE MCP tools are disallowed until the cap resets or the user upgrades. Subagent · WithWoz/wozcode-plugin
- Workflow Architect Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration. Subagent · yonatangross/orchestkit
- Explore Fast read-only agent for file searches, symbol lookups, and codebase questions like "where is X defined?", "where is X called?", or "how does X flow through the system?". Prefer over shell-based exploration when answering would take 3+ Search/Sql calls. Cheaper model (haiku) so delegation pays for itself on any real scan. Subagent · WithWoz/wozcode-plugin
- Web Research Analyst Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon. Subagent · yonatangross/orchestkit
- Pneuma Amender Pneuma Skills amendment specialist. Use proactively to apply code-review findings to existing work inside the git worktree the parent prepared — judge each finding (fix valid ones with surgical, industrial-grade precision, escalate wrong / out-of-authority ones), follow TDD where the finding warrants it, return a per-finding disposition ledger so nothing is silently dropped. The caller picks the… Subagent · pandazki/pneuma-skills
- Ui Feedback UI annotation and feedback processor. Watches for new annotations from agentation, maps element paths to source code, implements fixes… Subagent · yonatangross/orchestkit
- Pneuma Amender Fable Pneuma Skills amendment specialist — HEAVYWEIGHT Fable-5 engine. Identical discipline to pneuma-amender (judge each finding, surgical… Subagent · pandazki/pneuma-skills