How do I install the Argocd Advanced skill?

Run npx skillmds@latest add julianobarbosa/argocd-advanced in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Argocd Advanced safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Argocd Advanced?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Argocd Advanced free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Argocd Advanced?

julianobarbosa (@julianobarbosa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Argocd Advanced by julianobarbosa — Agent Skill

Name: Argocd Advanced
Rating: 4.5 (4 reviews)
Author: julianobarbosa

Argocd Advanced

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.

File contents

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.

---name: argocd-advanceddescription: 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.

Frequently asked questions