Manages declarative GitOps deployments for Kubernetes clusters.

Install

mkdir -p .claude/skills/gitops && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14206" && unzip -o skill.zip -d .claude/skills/gitops && rm skill.zip

Installs to .claude/skills/gitops

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

GitOps workflows with ArgoCD and Flux for declarative Kubernetes deployments. Use when setting up GitOps, ArgoCD sync, or Kubernetes declarative infrastructure. NOT for simple deploys (use vercel-deploy) or general CI/CD (use cicd-pipeline).
241 chars✓ has a “when” trigger
Advanced

Key capabilities

  • →Decide between ArgoCD and Flux for Kubernetes deployments
  • →Configure sync policies per environment (Manual, Auto, Prune, Self-Heal)
  • →Implement secret management strategies using Sealed Secrets or External Secrets
  • →Define repository structure for GitOps workflows
  • →Ensure OpenGitOps compliance with four principles

How it works

The skill provides architecture and strategy for GitOps delivery, guiding decisions between ArgoCD and Flux based on criteria like UI and multi-cluster support. It defines sync policies, secret management, and repository structure to ensure declarative Kubernetes deployments.

Inputs & outputs

You give it
Kubernetes deployment requirements or architecture review request
You get back
GitOps architecture decisions and configuration recommendations

When to use gitops

  • →Setting up ArgoCD or Flux
  • →Defining GitOps sync policies
  • →Managing Kubernetes secrets securely
  • →Implementing declarative deployments

About this skill

GitOps Delivery

Operate Kubernetes through declarative, versioned, continuously reconciled desired state.

Workflow

  1. Define repository ownership, environment boundaries, approvers, and cluster trust.
  2. Separate application source, built artifacts, and environment configuration.
  3. Keep credentials out of Git; reference an approved secret-management system.
  4. Pin immutable artifact identities and validate manifests before promotion.
  5. Configure reconciliation, pruning, health, sync windows, and drift alerts by environment.
  6. Promote through reviewed commits; avoid out-of-band cluster mutation.
  7. Test rollback as a desired-state change and verify both controller and workload health.

Routing

Safety Gate

Block automatic pruning or broad cluster permissions until scope, preview, recovery, and monitoring are verified. Treat an unavailable controller, repository, signature check, or health signal as an incomplete deployment.

When not to use it

  • →When deploying simple applications (use vercel-deploy)
  • →When setting up general CI/CD pipelines (use cicd-pipeline)
  • →When performing cluster modifications

Prerequisites

Kubernetes clusterkubectlArgoCD or Flux installed

Limitations

  • →No auto-sync to production is allowed
  • →No secrets are stored in Git repositories
  • →Does not handle cluster provisioning

How it compares

This approach focuses on declarative Kubernetes deployments using Git as the single source of truth and continuous reconciliation, which differs from traditional imperative deployment methods or general CI/CD pipelines.

Compared to similar skills

gitops side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gitops (this skill)04moNo flagsAdvanced
k8s-helm88moReviewIntermediate
gitops-workflow53moReviewAdvanced
deployment-engineer45moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry