argocd
Skill1 starsChanged 15 days agoApache-2.0View on GitHub
Interact with ArgoCD GitOps deployments via REST API. Use when checking application sync status, health, triggering syncs, viewing deployment history, inspecting Kubernetes resources, reading pod logs, rolling back deployments, listing projects/clusters/repos, or managing ArgoCD applications.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- TeddyAlbina/skillstheir 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
- TeddyAlbina/skills★ 2same name
- kaynetik/skills★ 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-chatSkill
- code-reviewSkill
- commitSkill
- dependency-trackSkill
- financeSkill
- handoffSkill
- java-21-to-25-migrationSkill
- jenkinsSkill
- jiraSkill
- perplexitySkill
- pr-readySkill
- researchSkill
- shipSkill
- skanetrafikenSkill
- sonarqubeSkill
- tddSkill
- to-tasksSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run ./setup.sh from the repo root (recommended), or create config files manually:
- Very specific: line 95
Use argocd-app-history.sh to find the history ID.
- Distinctive: line 168
All endpoints are under the ArgoCD server URL:
“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
Interact with an ArgoCD server via its REST API.
Configuration
Run ./setup.sh from the repo root (recommended), or create config files manually:
mkdir -p ~/.boring/argocd
echo 'https://argocd.example.com' > ~/.boring/argocd/url
echo 'your-bearer-token' > ~/.boring/argocd/token
chmod 600 ~/.boring/argocd/tokenGenerate a token:
- API token:
argocd account generate-token --account <account-name> - Session token:
curl -s $ARGOCD_URL/api/v1/session -d '{"username":"admin","password":"PASSWORD"}'
Scripts
List applications
scripts/argocd-app-list.sh [--project PROJECT] [--repo REPO]Application details
scripts/argocd-app-get.sh <app-name> [--project PROJECT]Shows sync status, health, repo, target revision, conditions, last operation.
Sync an application
scripts/argocd-app-sync.sh <app-name> [--revision REV] [--prune] [--dry-run] [--project PROJECT]Wait for sync and health
scripts/argocd-app-wait.sh <app-name> [--timeout SECONDS] [--project PROJECT]Polls until the app is Synced + Healthy (or timeout). Default timeout: 300s.
Sync history
scripts/argocd-app-history.sh <app-name> [--project PROJECT]Resource tree
scripts/argocd-app-resources.sh <app-name> [--project PROJECT]Shows all Kubernetes resources managed by the app with their health and status.
Pod logs
scripts/argocd-app-logs.sh <app-name> [--resource NAME] [--container NAME] [--tail LINES] [--project PROJECT]Rendered manifests
scripts/argocd-app-manifests.sh <app-name> [--project PROJECT]Live vs desired diff
scripts/argocd-app-diff.sh <app-name> [--project PROJECT]Shows resources that differ between the live cluster state and the desired state in Git.
Rollback
scripts/argocd-app-rollback.sh <app-name> <history-id> [--project PROJECT]Use argocd-app-history.sh to find the history ID.
Resource actions
scripts/argocd-app-actions.sh <app-name> --kind KIND --name RESOURCE_NAME [--run ACTION] [--namespace NS] [--group GROUP] [--project PROJECT]List available actions (omit --run) or execute one (e.g. restart a Deployment).
Delete application
scripts/argocd-app-delete.sh <app-name> [--cascade|--no-cascade] [--project PROJECT]--cascade (default) also deletes Kubernetes resources. --no-cascade removes from ArgoCD only.
List projects
scripts/argocd-project-list.shProject details
scripts/argocd-project-get.sh <project-name>List clusters
scripts/argocd-cluster-list.shList repositories
scripts/argocd-repo-list.shRaw API
scripts/argocd-api.sh <endpoint> [curl-options...]Typical workflow
S=scripts
# Check what's deployed
$S/argocd-app-list.sh
$S/argocd-app-get.sh my-service
$S/argocd-app-resources.sh my-service
# After pushing code changes, sync
$S/argocd-app-sync.sh my-service
$S/argocd-app-wait.sh my-service --timeout 600
# Debug if unhealthy
$S/argocd-app-logs.sh my-service --resource my-service-pod --tail 200
$S/argocd-app-diff.sh my-service
# Rollback if needed
$S/argocd-app-history.sh my-service
$S/argocd-app-rollback.sh my-service 5
$S/argocd-app-wait.sh my-serviceAPI endpoints reference
All endpoints are under the ArgoCD server URL:
/api/v1/applications— list/create applications/api/v1/applications/{name}— get/update/delete app/api/v1/applications/{name}/sync— trigger sync (POST)/api/v1/applications/{name}/rollback— rollback (POST)/api/v1/applications/{name}/resource-tree— resource tree/api/v1/applications/{name}/managed-resources— managed resources with diffs/api/v1/applications/{name}/manifests— rendered manifests/api/v1/applications/{name}/logs— pod logs/api/v1/applications/{name}/resource/actions— resource actions/api/v1/projects— list/create projects/api/v1/projects/{name}— get/update project/api/v1/clusters— list clusters/api/v1/repositories— list repositories/api/v1/session/userinfo— current user info
Auth: Authorization: Bearer <token>. All endpoints accept optional project query param.
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.

