Argocd
Inspect and operate Argo CD applications from the sandbox with the argocd CLI. Use for Argo CD app status, history, sync, rollback, and resource inspection after credentials or server context are available.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Argocd when an AI agent needs a reusable SKILL.md workflow for this job: Inspect and operate Argo CD applications from the sandbox with the argocd CLI. Use for Argo CD app status, history, sync, rollback, and resource inspection after credentials or server context are available.
When not to use it
Skip Argocd when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/argocd # Save SKILL.md to ~/.claude/skills/argocd/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/argocd/SKILL.md. For a shared project, commit the folder at .claude/skills/argocd/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Argocd skill for this task: Use Argocd when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Argo CD CLI
Use this skill when the user asks about Argo CD applications, GitOps sync state, Argo CD rollbacks, app health, or why Kubernetes resources managed by Argo CD are out of sync.
If `argocd` is not on PATH, report that the sandbox runtime image does not bundle `argocd`; do not spend the turn installing it.
## Setup
Argo CD credentials are not minted by Nuphos today. Use one of these contexts:
- The user provides an Argo CD server and token. - A kubeconfig is loaded with the `kubectl` skill and Argo CD is configured for core mode. - The target cluster exposes Argo CD credentials in a known, user-approved Kubernetes Secret.
Before running mutating commands, always show the target server and app name.
```bash # Token-based login. Do not echo the token. ARGOCD_SERVER=<argocd.example.com> ARGOCD_AUTH_TOKEN=<token> argocd app list --server "$ARGOCD_SERVER" --grpc-web
# Core mode through the kubectl skill's kubeconfig. There is no current-context — name # the target cluster explicitly, exactly like kubectl. kubectl config get-contexts argocd --core --kube-context <context> app list ```
## Read-only First
Start with read-only commands. Every one of these talks to a control plane, so carry the same targeting flags you established in Setup — `--server` in server mode, `--core --kube-context <context>` in core mode (shown here as `$target`):
```bash argocd version --client --short # local only, no target needed
target="--core --kube-context <context>" # or: target="--server $ARGOCD_SERVER --grpc-web" argocd $target app list argocd $target app get <app> argocd $target app history <app> argocd $target app manifests <app> argocd $target app resources <app> argocd $target app diff <app> ```
List the available contexts with `kubectl config get-contexts` before picking one — the kubeconfig deliberately has no default.
## Mutations
Ask for explicit confirmation before:
- `argocd app sync` - `argocd app rollback` - `argocd app terminate-op` - `argocd app delete` - `argocd app set` - Any command with `--prune`, `--force`, or `--replace`
Summarize the app, project, destination cluster/namespace, revision, and any prune/force flags before running the command.
## Safety
- Do not print tokens, session cookies, or Kubernetes Secret values. - Do not assume `argocd app list` without `--server` or `--core --kube-context` is pointed at the right control plane. Name the target explicitly. - Prefer `argocd app diff` before sync when the user asks to deploy changes. - Avoid broad commands such as syncing every app in a project unless the user explicitly requests that scope.
Intended uses
- Use Argocd when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.