agentleFS
thisrohanguptathisrohangupta/harness-skills/skills/gitops-status/SKILL.md

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
  1. Distinctive:

    Healthy: - All resources running and passing health checks

    line 114
  2. Distinctive:

    Check all applications in the requested scope before summarizing health status.

    line 137
  3. Distinctive:

    Check git repo for recent changes

    line 144
  4. Distinctive:

    Verify auto-sync is enabled if expected

    line 145
  5. Distinctive:

    Check pod logs for application errors

    line 150
  6. Distinctive:

    Check resource limits and quotas

    line 152
  7. Distinctive:

    Verify ArgoCD agent is running

    line 155

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 resources

GitOps Resource Types

Resource TypeOperationsDescription
gitops_agentlist, getArgoCD instances
gitops_applicationlist, get, syncApplications
gitops_applicationsetlist, getApplicationSets
gitops_clusterlist, getK8s clusters
gitops_repositorylist, getGit repositories
gitops_app_eventlistApplication events
gitops_pod_loggetPod logs
gitops_managed_resourcelistK8s resources
gitops_app_resource_treegetResource tree
gitops_dashboardgetOverview 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.