Best use case
gitops is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
GitOps tooling expertise for Argo CD and Flux-based continuous delivery
Teams using gitops should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gitops/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gitops Compares
| Feature / Agent | gitops | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
GitOps tooling expertise for Argo CD and Flux-based continuous delivery
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitOps Skill ## Overview Specialized skill for GitOps-based continuous delivery using Argo CD and Flux. Provides deep expertise in declarative, Git-driven infrastructure and application deployment. ## Capabilities ### Argo CD Configuration - Create and manage Application resources - Configure ApplicationSet for multi-cluster/multi-tenant - Set up AppProject for access control - Implement sync policies and strategies - Configure resource hooks and waves ### Flux Configuration - Set up GitRepository and HelmRepository sources - Create Kustomization and HelmRelease resources - Configure ImageUpdateAutomation - Implement multi-tenancy with namespaces - Set up Flux notifications ### Sync Strategies - Configure automatic vs manual sync - Implement sync windows and freezes - Set up health checks and degraded detection - Handle sync failures and retries - Design progressive delivery patterns ### Drift Detection - Configure drift detection and reconciliation - Set up resource diffing and comparison - Implement self-healing policies - Handle out-of-band changes - Configure pruning strategies ### Secret Management - Integrate SOPS for encrypted secrets - Configure Sealed Secrets - Set up External Secrets Operator - Implement Vault integration - Handle secret rotation in GitOps ### Multi-Cluster Setup - Configure multi-cluster deployments - Implement cluster generators - Set up cross-cluster sync - Handle cluster credentials securely - Design hub-spoke architectures ## Target Processes - `cicd-pipeline-setup.js` - GitOps-based deployment pipelines - `kubernetes-setup.js` - Declarative cluster management - `idp-setup.js` - Platform self-service deployment ## Usage Context This skill is invoked when processes require: - Setting up GitOps-based continuous delivery - Configuring Argo CD or Flux - Implementing drift detection and reconciliation - Managing secrets in GitOps workflows - Multi-cluster GitOps architectures ## Dependencies - argocd CLI (for Argo CD) - flux CLI (for Flux) - kubectl for verification - Git repository access - SOPS/Sealed Secrets for secret management ## Output Formats - Argo CD Application/ApplicationSet manifests - Flux GitRepository/Kustomization/HelmRelease manifests - Sync policy configurations - Multi-cluster setup guides - Secret management configurations
Related Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.