argocd
Skill2 starsChanged 28 days agoMITView on GitHub
Automate GitOps via ArgoCD API and CLI. Manage Applications, ApplicationSets, and multi-cluster deployments; configure Projects (RBAC), Repositories (Git/Helm/OCI), and Cluster credentials. Supports all REST API and CLI operations using bearer token authentication.
- Reads credentials
- Sends data out
5 other projects use a version of this.
Adopted by
Most recently taken up by
- rezkam/boring-but-goodtheir own version, first seen Nov 1, 2026
- kaynetik/skillstheir own version, first seen Oct 20, 2026
- abevz/devops-skillstheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- greedychipmunk/agent-skillstheir own version, first seen May 25, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- greedychipmunk/agent-skills★ 24same name
- G1Joshi/Agent-Skills★ 15same name
- kaynetik/skills★ 1same name
- rezkam/boring-but-good★ 1same name
- abevz/devops-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository192 other files it gives its agents.
- clickhouse-architecture-advisor/AGENTS.mdAGENTS.md
- clickhouse-best-practices/AGENTS.mdAGENTS.md
- unsafe-checker/AGENTS.mdAGENTS.md
- alertmanager-querySkill
- analyzing-range-distributionSkill
- analyzing-schema-change-storage-riskSkill
- aspire-configurationSkill
- aspire-integration-testingSkill
- aspire-service-defaultsSkill
- auditing-cloud-cluster-securitySkill
- auditing-table-statisticsSkill
- benchmarking-transaction-patternsSkill
- cepthSkill
- chdb-datastoreSkill
- chdb-sqlSkill
- clickhouse-architecture-advisorSkill
- clickhouse-best-practicesSkill
- clickhousectl-cloud-deploySkill
- clickhousectl-local-devSkill
- cockroachdb-sqlSkill
- coding-guidelinesSkill
- configuring-audit-loggingSkill
- configuring-ip-allowlistsSkill
- configuring-log-exportSkill
- configuring-private-connectivitySkill
- configuring-sso-and-scimSkill
- create-technical-architecture-documentSkill
- csharp-mstestSkill
- csharp-tunitSkill
- csharp-xunitSkill
- designing-application-transactionsSkill
- designing-multi-region-applicationsSkill
- domain-cliSkill
- domain-cloud-nativeSkill
- domain-embeddedSkill
- domain-fintechSkill
- domain-iotSkill
- domain-mlSkill
- domain-webSkill
- dotnet-aot-wasmSkill
- dotnet-aspire-patternsSkill
- dotnet-benchmarkdotnetSkill
- dotnet-blazor-authSkill
- dotnet-blazor-componentsSkill
- dotnet-blazor-patternsSkill
- dotnet-blazor-testingSkill
- dotnet-channelsSkill
- dotnet-ci-benchmarkingSkill
- dotnet-cli-architectureSkill
- dotnet-cli-distributionSkill
- dotnet-cli-packagingSkill
- dotnet-cli-release-pipelineSkill
- dotnet-containersSkill
- dotnet-cryptographySkill
- dotnet-csharp-dependency-injectionSkill
- dotnet-csharp-modern-patternsSkill
- dotnet-csharp-nullable-reference-typesSkill
- dotnet-csharp-source-generatorsSkill
- dotnet-maui-doctorSkill
- dotnet-maui-doctorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
All API calls use this pattern:
- Very specific: line 47
Use the helper script at scripts/argocd-api.sh for common operations.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ArgoCD Skill
Complete ArgoCD operations via REST API and CLI with bearer token authentication.
Authentication Setup
Generate and use bearer tokens for all operations:
# Generate token (requires existing login)
argocd login $ARGOCD_SERVER --username admin --password $ARGOCD_PASSWORD
ARGOCD_TOKEN=$(argocd account generate-token)
# Or generate for service account
ARGOCD_TOKEN=$(argocd account generate-token --account cibot --expires-in 7d)
# Export for subsequent commands
export ARGOCD_SERVER="argocd.example.com"
export ARGOCD_AUTH_TOKEN="$ARGOCD_TOKEN"Service account setup (in argocd-cm ConfigMap):
data:
accounts.cibot: apiKey,login
accounts.cibot.enabled: "true"REST API Pattern
All API calls use this pattern:
curl -s -H "Authorization: Bearer $ARGOCD_AUTH_TOKEN" \
-H "Content-Type: application/json" \
"https://$ARGOCD_SERVER/api/v1/{endpoint}"Use the helper script at scripts/argocd-api.sh for common operations.
Quick Reference
Applications
# List all applications
argocd app list -o json
# Create application
argocd app create myapp \
--repo https://github.com/org/repo.git \
--path manifests \
--dest-server https://kubernetes.default.svc \
--dest-namespace default \
--sync-policy automated \
--auto-prune \
--self-heal
# Sync with options
argocd app sync myapp --prune --force --timeout 300
# Sync specific resources only
argocd app sync myapp --resource apps:Deployment:nginx
# Dry run
argocd app sync myapp --dry-run
# Wait for health
argocd app wait myapp --health --sync --timeout 300
# Get status
argocd app get myapp -o json | jq '{health: .status.health.status, sync: .status.sync.status}'
# Rollback
argocd app history myapp
argocd app rollback myapp 2
# Delete (cascade deletes resources)
argocd app delete myapp --cascade -y
# Terminate running operation
argocd app terminate-op myappApplicationSets
# Create/update ApplicationSet
argocd appset create appset.yaml --upsert
# List
argocd appset list
# Get details
argocd appset get myappset -o yaml
# Delete
argocd appset delete myappset -yProjects
# Create project
argocd proj create myproject -d https://kubernetes.default.svc,default -s https://github.com/org/*
# Add destinations/sources
argocd proj add-destination myproject https://kubernetes.default.svc 'team-*'
argocd proj add-source myproject 'https://github.com/org/*'
# Manage roles
argocd proj role create myproject deployer
argocd proj role add-policy myproject deployer -a sync -p allow -o '*'
argocd proj role add-group myproject deployer my-sso-group
# Generate role token
argocd proj role create-token myproject deployer --expires-in 24h
# Sync windows
argocd proj windows add myproject --kind allow --schedule "0 22 * * *" --duration 2h
argocd proj windows list myprojectRepositories
# Add HTTPS repo with token
argocd repo add https://github.com/org/repo --username git --password $GH_TOKEN
# Add SSH repo
argocd repo add git@github.com:org/repo.git --ssh-private-key-path ~/.ssh/id_rsa
# Add Helm repo
argocd repo add https://charts.example.com --type helm --name myrepo
# Add OCI registry
argocd repo add registry.example.com --type helm --enable-oci --username user --password pass
# Credential template (applies to matching repos)
argocd repocreds add https://github.com/myorg/ --username git --password $TOKEN
# List/remove
argocd repo list
argocd repo rm https://github.com/org/repoClusters
# Add cluster from kubeconfig context
argocd cluster add my-context --name production
# List clusters
argocd cluster list
# Get cluster details
argocd cluster get https://production.example.com
# Rotate credentials
argocd cluster rotate-auth production
# Remove cluster
argocd cluster rm https://production.example.comAccounts
# List accounts
argocd account list
# Generate token
argocd account generate-token --account cibot --expires-in 7d --id deploy-token
# Check permissions
argocd account can-i sync applications '*'
argocd account can-i get applications 'myproject/*'
# Update password
argocd account update-password --account admin
# Get user info
argocd account get-user-infoREST API Examples
See references/api-reference.md for complete endpoint documentation.
Create Application via API
curl -X POST -H "Authorization: Bearer $ARGOCD_AUTH_TOKEN" \
-H "Content-Type: application/json" \
"https://$ARGOCD_SERVER/api/v1/applications" \
-d '{
"metadata": {"name": "myapp", "namespace": "argocd"},
"spec": {
"project": "default",
"source": {
"repoURL": "https://github.com/org/repo.git",
"path": "manifests",
"targetRevision": "HEAD"
},
"destination": {
"server": "https://kubernetes.default.svc",
"namespace": "default"
},
"syncPolicy": {
"automated": {"prune": true, "selfHeal": true},
"syncOptions": ["CreateNamespace=true"]
}
}
}'Sync Application via API
curl -X POST -H "Authorization: Bearer $ARGOCD_AUTH_TOKEN" \
-H "Content-Type: application/json" \
"https://$ARGOCD_SERVER/api/v1/applications/myapp/sync" \
-d '{
"revision": "HEAD",
"prune": true,
"dryRun": false,
"strategy": {"hook": {}},
"syncOptions": {"items": ["CreateNamespace=true"]}
}'Get Application Status
curl -s -H "Authorization: Bearer $ARGOCD_AUTH_TOKEN" \
"https://$ARGOCD_SERVER/api/v1/applications/myapp" | \
jq '{name: .metadata.name, health: .status.health.status, sync: .status.sync.status}'Application Spec Reference
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: myapp
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/org/repo.git
targetRevision: HEAD
path: manifests
# Helm options
helm:
releaseName: my-release
valueFiles: [values.yaml, values-prod.yaml]
parameters:
- name: image.tag
value: v1.0.0
# Kustomize options
kustomize:
namePrefix: prod-
images: [gcr.io/image:v1.0.0]
destination:
server: https://kubernetes.default.svc
namespace: default
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
- ServerSideApply=true
- PruneLast=true
retry:
limit: 5
backoff:
duration: 5s
factor: 2
maxDuration: 3m
ignoreDifferences:
- group: apps
kind: Deployment
jsonPointers: [/spec/replicas]ApplicationSet Generators
See references/api-reference.md for complete generator patterns.
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
name: cluster-apps
namespace: argocd
spec:
generators:
# List generator
- list:
elements:
- cluster: dev
url: https://dev.example.com
- cluster: prod
url: https://prod.example.com
# Cluster generator
- clusters:
selector:
matchLabels:
environment: production
# Git directory generator
- git:
repoURL: https://github.com/org/apps.git
directories:
- path: apps/*
# Matrix generator (combine two generators)
- matrix:
generators:
- clusters: {}
- git:
repoURL: https://github.com/org/apps.git
directories: [{path: apps/*}]
template:
metadata:
name: '{{.cluster}}-{{.path.basename}}'
spec:
project: default
source:
repoURL: https://github.com/org/apps.git
targetRevision: HEAD
path: '{{.path.path}}'
destination:
server: '{{.url}}'
namespace: '{{.path.basename}}'Sync Options Reference
| Option | Description |
Prune=true | Delete resources not in Git |
PruneLast=true | Prune after sync completes |
Replace=true | Use replace instead of apply |
ServerSideApply=true | Use server-side apply |
CreateNamespace=true | Create namespace if missing |
ApplyOutOfSyncOnly=true | Only sync changed resources |
Validate=false | Skip kubectl validation |
Force=true | Force resource replacement |
RespectIgnoreDifferences=true | Respect ignoreDifferences on sync |
Resource Hooks and Waves
metadata:
annotations:
# Sync wave (lower = earlier)
argocd.argoproj.io/sync-wave: "-1"
# Hook phase
argocd.argoproj.io/hook: PreSync|Sync|PostSync|SyncFail|PostDelete
# Hook deletion policy
argocd.argoproj.io/hook-delete-policy: HookSucceeded|HookFailed|BeforeHookCreationHealth Status Values
| Status | Description |
Healthy | Resource running correctly |
Progressing | Deployment in progress |
Degraded | Health check failed |
Suspended | Resource paused |
Missing | Resource doesn't exist |
Unknown | Cannot determine health |
CLI Global Flags
| Flag | Description |
--server | ArgoCD server address |
--auth-token | Bearer token |
--grpc-web | Use gRPC-web (for proxies) |
--insecure | Skip TLS verification |
--plaintext | Disable TLS |
--config | Config file path |
-o json/yaml/wide | Output format |
Error Handling
# Check if app exists before operations
if argocd app get myapp &>/dev/null; then
argocd app sync myapp
else
argocd app create myapp ...
fi
# Wait with timeout and handle failure
if ! argocd app wait myapp --health --timeout 300; then
echo "App failed to become healthy"
argocd app get myapp
exit 1
fi
# Idempotent upsert pattern
argocd app create myapp --upsert ...
argocd repo add https://repo --upsert ...Common Workflows
Deploy and Wait Pattern
argocd app sync myapp --prune --async
argocd app wait myapp --health --sync --timeout 300Canary/Blue-Green with Argo Rollouts
# Promote rollout
argocd app actions run myapp promote --kind Rollout --resource-name my-rolloutMulti-Cluster Deployment
# Register clusters
argocd cluster add dev-context --name dev
argocd cluster add prod-context --name prod
# Use ApplicationSet with cluster generatorFor complete API endpoint documentation, see references/api-reference.md.
For complete CLI command reference, see references/cli-reference.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

