gitops-status
Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub
Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP. Use when user says "gitops status", "argocd status", "application sync", "gitops health", "is my app in sync", or asks about GitOps applications.
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 114
Healthy: - All resources running and passing health checks
- Distinctive: line 137
Check all applications in the requested scope before summarizing health status.
- Distinctive: line 144
Check git repo for recent changes
- Distinctive: line 145
Verify auto-sync is enabled if expected
- Distinctive: line 150
Check pod logs for application errors
- Distinctive: line 152
Check resource limits and quotas
- Distinctive: line 155
Verify ArgoCD agent is running
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitOps Status
Monitor GitOps application health and manage sync operations via MCP.
Instructions
Step 1: Overview Dashboard
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_dashboard"Step 2: List Applications
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_application"
org_id: "<organization>"
project_id: "<project>"Step 3: Get Application Details
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_application"
resource_id: "<app_name>"
org_id: "<organization>"
project_id: "<project>"Step 4: Check Resource Tree
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_app_resource_tree"
resource_id: "<app_name>"Step 5: Get Pod Logs (Debugging)
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_pod_log"
resource_id: "<pod_name>"Step 6: Check Events
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_app_event"Step 7: Trigger Sync
Call MCP tool: harness_execute
Parameters:
resource_type: "gitops_application"
action: "sync"
resource_id: "<app_name>"
org_id: "<organization>"
project_id: "<project>"Additional Resource Types
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_agent" # ArgoCD agents
resource_type: "gitops_cluster" # Connected clusters
resource_type: "gitops_repository" # Git repositories
resource_type: "gitops_applicationset" # ApplicationSets
resource_type: "gitops_managed_resource" # K8s resourcesGitOps Resource Types
| Resource Type | Operations | Description |
gitops_agent | list, get | ArgoCD instances |
gitops_application | list, get, sync | Applications |
gitops_applicationset | list, get | ApplicationSets |
gitops_cluster | list, get | K8s clusters |
gitops_repository | list, get | Git repositories |
gitops_app_event | list | Application events |
gitops_pod_log | get | Pod logs |
gitops_managed_resource | list | K8s resources |
gitops_app_resource_tree | get | Resource tree |
gitops_dashboard | get | Overview dashboard |
Application Health States
- Healthy - All resources running and passing health checks
- Degraded - Some resources failing health checks
- Progressing - Resources being created/updated
- Suspended - Application suspended
- Missing - Resources not found
- Unknown - Health status cannot be determined
Sync States
- Synced - Live state matches desired state in Git
- OutOfSync - Live state differs from Git (needs sync)
- Unknown - Sync status cannot be determined
Examples
- "Show me all GitOps applications" - List gitops_application
- "Is the api-gateway in sync?" - Get gitops_application, check sync status
- "Sync the payment-service" - Execute sync action
- "Get pod logs for failing service" - Get gitops_pod_log
- "Show the resource tree for my app" - Get gitops_app_resource_tree
Performance Notes
- Check all applications in the requested scope before summarizing health status.
- For out-of-sync applications, examine the resource tree to identify the specific drift.
- Gather pod logs for failing resources before diagnosing issues.
Troubleshooting
Application OutOfSync
- Check git repo for recent changes
- Verify auto-sync is enabled if expected
- Review sync errors in events
- Trigger manual sync if needed
Application Degraded
- Check pod logs for application errors
- Review resource tree for failing pods
- Check resource limits and quotas
Agent Not Connected
- Verify ArgoCD agent is running
- Check network connectivity
- Review agent configuration
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- harness/harness-skills★ 12798% same
Wrote their own version · 0
None found.
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 repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/harness.mdcCursor rule
- analyze-costsSkill
- audit-reportSkill
- chaos-experimentSkill
- create-agentSkill
- create-agent-templateSkill
- create-connectorSkill
- create-environmentSkill
- create-infrastructureSkill
- create-pipelineSkill
- create-pipeline-v1Skill
- create-policySkill
- create-secretSkill
- create-serviceSkill
- create-templateSkill
- create-triggerSkill
- debug-pipelineSkill
- dora-metricsSkill
- manage-delegatesSkill
- manage-feature-flagsSkill
- manage-rolesSkill
- manage-usersSkill
- migrate-pipelineSkill
- run-pipelineSkill
- scorecard-reviewSkill
- security-reportSkill
- template-usageSkill
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.

