argocd-advanced — Claude Code skill: what it does, how to install
argocd-advanced covers the automation side of ArgoCD: ApplicationSet generators, automatic image updates and bringing a new cluster into a GitOps setup. Reach for it when sync and diff commands are not enough.
MIT 231 installs ★ 17 updated 2026-10-14
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a claude-codeWhat argocd-advanced does
The skill routes you to the right deep-dive instead of dumping everything at once. Each area keeps its own reference under References/, with Workflows/, Tools/ and Samples/ next to it for cluster bootstrap and workload onboarding. Generator types all get coverage: list, cluster, git, matrix, merge, SCM, pull request, plugin. Image Updater is documented with semver, digest and newest-build strategies, plus the git write-back path.
Order matters with matrix and merge generators, because the parent result feeds the child. Get it backwards and the parameter set comes out empty, with nothing in the logs. Git write-back also needs a credential that can push. A read-only repo credential leaves images stuck on the old version, so look for permission denied in the Image Updater pod logs.
Cluster secrets registered during bootstrap have to carry the labels your generators select on. Miss the label and the ApplicationSets match nothing. The application-install template assumes a particular multi-repo layout, so outside that setup it works as a pattern to adapt rather than a runnable recipe. Version support decides adoption: ApplicationSet ships with ArgoCD 2.3+, while the SCM and pull request generators need 2.5+ — check yours before you start.
What it helps with
- fan one application definition across many clusters with generators
- commit fresh image builds back to git without manual bumps
- register a new cluster in a multi-repo GitOps layout
- label a cluster so existing ApplicationSet generators pick it up
- onboard a service through the shared ApplicationSet template
Example prompts for the agent
- Build an ApplicationSet with a matrix generator so the same app lands on every cluster carrying the right labels.
- Set up Image Updater so new image builds get committed back to the repo on their own.
- Register a new cluster and confirm its labels match what the current ApplicationSets select on.
How to install argocd-advanced
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a claude-code2Manually: put the files in place
~/.claude/skills/argocd-advanced/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/argocd-advanced/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a codex2Manually: put the files in place
.agents/skills/argocd-advanced/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a cursor2Manually: put the files in place
.cursor/skills/argocd-advanced/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install julianobarbosa/claude-code-skills skills/argocd-advanced2Manually: put the files in place
.github/skills/argocd-advanced/SKILL.md1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a gemini-cli2Platform CLI
gemini skills install https://github.com/julianobarbosa/claude-code-skills --path skills/argocd-advancedManually: put the files in place
.devin/skills/argocd-advanced/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about argocd-advanced
How do I install argocd-advanced in Claude Code?
Run npx skills add julianobarbosa/claude-code-skills --skill argocd-advanced -a claude-code. The skill file lands at ~/.claude/skills/argocd-advanced/SKILL.md.
What does argocd-advanced do?
It covers ArgoCD automation: ApplicationSet generators, image updates with git write-back, cluster bootstrap and workload onboarding through a template. Routine sync, status and diff work stays with the core argocd skill.
Why does my matrix generator return an empty parameter set?
The parent and child generators are most likely in the wrong order. Parent output feeds the child, and a reversed order fails without an error.
Source text
SKILL.md · MIT
--- name: argocd-advanced description: Advanced ArgoCD operations beyond the core CLI/API — multi-cluster ApplicationSet generators, automated image updates, new-cluster bootstrapping, and workload onboarding via templated ApplicationSets. USE WHEN working with ApplicationSet CRDs (list, cluster, git, matrix, merge, SCM, pull request, plugin generators), configuring ArgoCD Image Updater (semver/digest/newest-build update strategies + git write-back), bootstrapping a new Kubernetes cluster into a multi-repo GitOps setup, registering clusters with proper labels for ApplicationSet targeting, onboarding a new workload via the standard ApplicationSet template, or troubleshooting any of these. For routine app sync/status/diff work use the core `argocd` skill instead. --- # ArgoCD Advanced Routing entrypoint for advanced/automation-oriented ArgoCD operations. Each sub-area has its own deep reference, preserved verbatim from the pre-consolidation skills, under `References/`. ## Scope routing | If you need to… | Read | |---|---| | Implement multi-cluster app propagation with ApplicationSet generators (list / cluster / git / matrix / merge / SCM / pull-request / plugin) | `References/applicationset.md` plus `References/applicationset/` for deep-dive reference docs | | Automate container image updates for ArgoCD-managed workloads (update strategies, ImageUpdater CRD, git write-back) | `References/image-updater.md` + `References/image-updater/` + `References/ArgocdImageUpdater/` + `Samples/image-updater/` | | Bootstrap a new Kubernetes cluster into the multi-repo GitOps environment | `References/cluster-bootstrapping.md` + `References/cluster-bootstrapping/` + `References/ArgocdClusterBootstrapping/` | | Onboard a new workload via the standardized ApplicationSet template | `References/application-install.md` + `Workflows/application-install/` + `Tools/application-install/` | ## Decision tree ``` Need new cluster registered with ArgoCD? -> cluster-bootstrapping Need new service deployed to existing clusters? -> application-install Need to fan one app definition across N clusters? -> applicationset Need images to roll forward automatically? -> image-updater ``` ## Gotchas - **ApplicationSet generators are ordered.** With matrix/merge generators, the parent generator's result is the input to the child — get the order wrong and you get an empty parameter set with no error. - **Image Updater + git write-back requires a write credential.** A read-only repo cred will silently leave images stuck on the original version. Check Image Updater pod logs for `permission denied` on push. - **Bootstrap cluster secrets must carry the labels your ApplicationSet generators select on.** A cluster registered without the expected label key/value is invisible to existing ApplicationSets — and there is no error, just zero apps. - **`application-install` ships a your organization/ExampleApp-specific template.** The Workflows assume the multi-repo layout. If you're not in that environment, treat it as a reference pattern, not a runnable recipe. - **CRD versions matter.** ApplicationSet ships with ArgoCD 2.3+; certain generators (SCM, pull request) need 2.5+. Read `References/applicationset.md` Version Compatibility before adopting.
© julianobarbosa · MIT · julianobarbosa/claude-code-skills