New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitOps with ArgoCD and Flux

by wshobson in wshobson/agents

Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.

MITAuto-check passedDevOps & Cloud

Install GitOps with ArgoCD and Flux

skills CLI
$ npx skills add wshobson/agents --skill gitops-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wshobson/agents gitops-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/kubernetes-operations/skills/gitops-workflow .claude/skills/gitops-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gitops-workflow
GitHub stars
40k
Used in
11 other repos
Token cost
~1.5k tokens
SKILL.md length
257 words
Files
3 (incl. references)
Skills in repo
142
Repo updated
First seen
Licence
MIT

At a glance

Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.

  • Works in 7 steps: Installation → Repository Structure → Create Application → …
  • Setting up GitOps for a Kubernetes cluster with ArgoCD or Flux
  • SKILL.md covers Purpose, When to Use This Skill, OpenGitOps Principles and ArgoCD Setup, plus 7 more sections
  • Calls argocd, kubectl and brew; reaches github.com and kubernetes.default.svc

What it does

The skill builds on the four OpenGitOps principles: the system is declarative, desired state is versioned and immutable in Git, agents pull it automatically, and they continuously reconcile actual state with it. For ArgoCD it covers creating the argocd namespace and installing, a suggested repository structure with apps per environment, an Application manifest and the app-of-apps pattern. For Flux it covers installing the CLI with Homebrew and running a pre-check, then defining a GitRepository and a Kustomization.

Sync policy examples show ArgoCD automated sync with pruning and Flux reconciliation intervals, with a dedicated sync-policies reference, and an argocd-setup reference adds detail. Progressive delivery sections show canary rollouts with Argo Rollouts and a blue-green strategy. The scope also lists multi-cluster deployments and secret management in GitOps. The excerpt is cut off in the blue-green example, so the later sections are not described.

When your agent uses it

  • Setting up GitOps for a Kubernetes cluster with ArgoCD or Flux
  • Deploying applications automatically from a Git repository
  • Configuring automated sync and pruning policies
  • Rolling out changes with canary or blue-green strategies

Example prompts

  • “Set up ArgoCD on our cluster and create an Application that deploys from our gitops-repo.”
  • “Bootstrap Flux with a GitRepository and Kustomization for the staging environment.”
  • “Use the app of apps pattern to manage our production and staging apps in ArgoCD.”
  • “Add a canary rollout with Argo Rollouts for the payments service.”

Requirements

  • A Kubernetes cluster with kubectl access
  • A Git repository for the desired state
  • Homebrew for the Flux CLI example

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Installation
  2. Repository Structure
  3. Create Application
  4. App of Apps Pattern
  5. Installation
  6. Create GitRepository
  7. Create Kustomization

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • argocd
    • kubectl
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • kubernetes.default.svc
    • raw.githubusercontent.com

    Also links to:

    • fluxcd.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitOps with ArgoCD and Flux loads about 1.5k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 257 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 257 words, ~1,491 tokens.

Download SKILL.mdSave it as .claude/skills/gitops-workflow/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
gitops-workflow
description
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.

GitOps Workflow

Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.

Purpose

Implement declarative, Git-based continuous delivery for Kubernetes using ArgoCD or Flux CD, following OpenGitOps principles.

When to Use This Skill

  • Set up GitOps for Kubernetes clusters
  • Automate application deployments from Git
  • Implement progressive delivery strategies
  • Manage multi-cluster deployments
  • Configure automated sync policies
  • Set up secret management in GitOps

OpenGitOps Principles

  1. Declarative - Entire system described declaratively
  2. Versioned and Immutable - Desired state stored in Git
  3. Pulled Automatically - Software agents pull desired state
  4. Continuously Reconciled - Agents reconcile actual vs desired state

ArgoCD Setup

1. Installation
bash
# Create namespace
kubectl create namespace argocd

# Install ArgoCD
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

# Get admin password
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d

Reference: See references/argocd-setup.md for detailed setup

2. Repository Structure
gitops-repo/
├── apps/
│   ├── production/
│   │   ├── app1/
│   │   │   ├── kustomization.yaml
│   │   │   └── deployment.yaml
│   │   └── app2/
│   └── staging/
├── infrastructure/
│   ├── ingress-nginx/
│   ├── cert-manager/
│   └── monitoring/
└── argocd/
    ├── applications/
    └── projects/
3. Create Application
yaml
# argocd/applications/my-app.yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: my-app
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/org/gitops-repo
    targetRevision: main
    path: apps/production/my-app
  destination:
    server: https://kubernetes.default.svc
    namespace: production
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
4. App of Apps Pattern
yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: applications
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/org/gitops-repo
    targetRevision: main
    path: argocd/applications
  destination:
    server: https://kubernetes.default.svc
    namespace: argocd
  syncPolicy:
    automated: {}

Flux CD Setup

1. Installation

The example uses Homebrew. For other systems, follow the official Flux installation guide.

bash
# Install the Flux CLI with Homebrew
brew install fluxcd/tap/flux
flux check --pre

# Bootstrap Flux
flux bootstrap github \
  --owner=org \
  --repository=gitops-repo \
  --branch=main \
  --path=clusters/production \
  --personal
2. Create GitRepository
yaml
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: my-app
  namespace: flux-system
spec:
  interval: 1m
  url: https://github.com/org/my-app
  ref:
    branch: main
3. Create Kustomization
yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: my-app
  namespace: flux-system
spec:
  interval: 5m
  path: ./deploy
  prune: true
  sourceRef:
    kind: GitRepository
    name: my-app

Sync Policies

Auto-Sync Configuration

ArgoCD:

yaml
syncPolicy:
  automated:
    prune: true # Delete resources not in Git
    selfHeal: true # Reconcile manual changes
    allowEmpty: false
  retry:
    limit: 5
    backoff:
      duration: 5s
      factor: 2
      maxDuration: 3m

Flux:

yaml
spec:
  interval: 1m
  prune: true
  wait: true
  timeout: 5m

Reference: See references/sync-policies.md

Progressive Delivery

Canary Deployment with ArgoCD Rollouts
yaml
apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  name: my-app
spec:
  replicas: 5
  strategy:
    canary:
      steps:
        - setWeight: 20
        - pause: { duration: 1m }
        - setWeight: 50
        - pause: { duration: 2m }
        - setWeight: 100
Blue-Green Deployment
yaml
strategy:
  blueGreen:
    activeService: my-app
    previewService: my-app-preview
    autoPromotionEnabled: false

Secret Management

External Secrets Operator
yaml
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  name: db-credentials
spec:
  refreshInterval: 1h
  secretStoreRef:
    name: aws-secrets-manager
    kind: SecretStore
  target:
    name: db-credentials
  data:
    - secretKey: password
      remoteRef:
        key: prod/db/password
Sealed Secrets
bash
# Encrypt secret
kubeseal --format yaml < secret.yaml > sealed-secret.yaml

# Commit sealed-secret.yaml to Git

Best Practices

  1. Use separate repos or branches for different environments
  2. Implement RBAC for Git repositories
  3. Enable notifications for sync failures
  4. Use health checks for custom resources
  5. Implement approval gates for production
  6. Keep secrets out of Git (use External Secrets)
  7. Use App of Apps pattern for organization
  8. Tag releases for easy rollback
  9. Monitor sync status with alerts
  10. Test changes in staging first

Troubleshooting

Sync failures:

bash
argocd app get my-app
argocd app sync my-app --prune

Out of sync status:

bash
argocd app diff my-app
argocd app sync my-app --force
  • k8s-manifest-generator - For creating manifests
  • helm-chart-scaffolding - For packaging applications

© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/kubernetes-operations/skills/gitops-workflow of wshobson/agents.

  • SKILL.md
  • references/argocd-setup.md
  • references/sync-policies.md

Open the folder on GitHubat commit 46891e7

Used in 11 other repositories

We found 26 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in wshobson/agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

GitOps with ArgoCD and Flux next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitOps with ArgoCD and Flux compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitOps with ArgoCD and Flux this skillwshobson/agents40k11 repos~1.5kAutomated safety check: PassMIT
Implementing Gitopsancoleman/ai-design-components526—~2.9kAutomated safety check: PassMIT
Argocd GitopsBagelHole/DevOps-Security-Agent-Skills1.1k—~2.4kAutomated safety check: PassMIT
Deploying Applicationsancoleman/ai-design-components526—~3.1kAutomated safety check: PassMIT
Argocd Gitopssickn33/agentic-awesome-skills47k1 repos~2.6kAutomated safety check: PassMIT
Gitops PractitionerFerroxLabs/wayland608—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Implementing Gitops

    ancoleman/ai-design-components

    Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

  • Argocd Gitops

    BagelHole/DevOps-Security-Agent-Skills

    Implement GitOps with ArgoCD for declarative Kubernetes deployments.

    1.1k GitHub stars~2.4k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

  • Deploying Applications

    ancoleman/ai-design-components

    Deployment patterns from Kubernetes to serverless and edge functions.

    526 GitHub stars~3.1k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

  • Argocd Gitops

    sickn33/agentic-awesome-skills

    Implement GitOps with ArgoCD for declarative Kubernetes deployments.

    47k GitHub starsUsed in 1 repo~2.6k tokens
    DevOps & CloudAuto-check passed

  • Gitops Practitioner

    FerroxLabs/wayland

    GitOps expertise covering ArgoCD, Flux, declarative infrastructure management, drift detection and reconciliation, environment promotion strategies, secrets in GitOps, multi-cluster management, and…

    608 GitHub stars~2.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Kubernetes Architect

    Cybereason-Public/owLSM

    Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration.

    280 GitHub starsUsed in 8 repos~2.6k tokens
    DevOps & CloudAuto-check passed

More from wshobson/agents

All 142 skills in this repo

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 13 repos~1.7k tokens
    Auto-check passed

  • Billing Automation

    wshobson/agents

    Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.

    40k GitHub starsUsed in 12 repos~473 tokens
    Auto-check passed

  • Python Performance Optimization

    wshobson/agents

    Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.

    40k GitHub starsUsed in 12 repos~814 tokens
    Auto-check passed

  • Portfolio Risk Metrics

    wshobson/agents

    Covers portfolio risk measurement with VaR, CVaR, Sharpe, Sortino and drawdown, plus guidance on limits, stress tests and tail risk.

    40k GitHub starsUsed in 12 repos~502 tokens
    Auto-check passed

  • DGX Spark Memory and Thermal Ops

    wshobson/agents

    Plans memory headroom, works through out-of-memory failures and watches temperature and power during long ML training jobs on NVIDIA DGX Spark.

    40k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Bats Shell Testing Patterns

    wshobson/agents

    Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    Auto-check passed

Works with

Categories

Questions about GitOps with ArgoCD and Flux

What does GitOps with ArgoCD and Flux do?

Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets. The skill builds on the four OpenGitOps principles: the system is declarative, desired state is versioned and immutable in Git, agents pull it automatically, and they continuously reconcile actual state with it. For ArgoCD it covers creating the argocd namespace and installing, a suggested repository structure with apps per environment, an Application manifest and the app-of-apps pattern.

When should I use GitOps with ArgoCD and Flux?

GitOps with ArgoCD and Flux fits situations like: setting up GitOps for a Kubernetes cluster with ArgoCD or Flux; deploying applications automatically from a Git repository; configuring automated sync and pruning policies; rolling out changes with canary or blue-green strategies.

How do I install GitOps with ArgoCD and Flux in Claude Code?

Run `npx skills add wshobson/agents --skill gitops-workflow -a claude-code`. Or copy the skill folder (plugins/kubernetes-operations/skills/gitops-workflow in wshobson/agents) into .claude/skills/gitops-workflow in your project. Claude Code loads it when a task matches its description.

How do I install GitOps with ArgoCD and Flux in Codex?

Run `npx skills add wshobson/agents --skill gitops-workflow -a codex`. Or copy the skill folder (plugins/kubernetes-operations/skills/gitops-workflow in wshobson/agents) into .agents/skills/gitops-workflow in your project. Codex loads it when a task matches its description.

Can I use GitOps with ArgoCD and Flux in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill gitops-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitops-workflow, .gemini/skills/gitops-workflow, .github/skills/gitops-workflow and .opencode/skills/gitops-workflow in your project.

What does GitOps with ArgoCD and Flux need to run?

Going by SKILL.md and its folder, GitOps with ArgoCD and Flux needs the command-line tools its instructions call (argocd, kubectl and brew). Our summary lists: A Kubernetes cluster with kubectl access; A Git repository for the desired state; Homebrew for the Flux CLI example.

Does GitOps with ArgoCD and Flux access the network?

SKILL.md names 4 domains. In commands or code: github.com, kubernetes.default.svc and raw.githubusercontent.com; the agent is likely to contact these when it follows the instructions. As links in the text: fluxcd.io. This is read from the text; nothing was executed.

Is GitOps with ArgoCD and Flux safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitOps with ArgoCD and Flux use?

GitOps with ArgoCD and Flux is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitOps with ArgoCD and Flux use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to GitOps with ArgoCD and Flux?

Skills that share tags, products or a category with GitOps with ArgoCD and Flux: Implementing Gitops (ancoleman/ai-design-components, 526 stars), Argocd Gitops (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars), Deploying Applications (ancoleman/ai-design-components, 526 stars) and Argocd Gitops (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitOps with ArgoCD and Flux?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,254 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.