gitops-status

Report health and sync state of ArgoCD deployments via Harness MCP.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill gitops-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-status
Source: https://github.com/harness/harness-skills/tree/main/skills/gitops-status
Command: npx skills add https://github.com/harness/harness-skills --skill gitops-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps GitOps deployments healthy and in sync by monitoring and managing ArgoCD resources through Harness MCP.

Core Features & Use Cases

  • Health monitoring: Check the current health state of gitops_application resources.
  • Sync management: Trigger synchronization, inspect drift, and apply repairs where possible.
  • Overview & troubleshooting: Retrieve dashboards, events, and pod logs to diagnose issues.

Quick Start

Ask it to check the health of my GitOps application in the current project.

Frequently Asked Questions about gitops-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to trigger synchronization for a drifted GitOps deployment?

GitOps health monitoring via MCP retrieves gitops_application resources to report deployment readiness and diagnose drift across multiple namespaces and clusters.

What is the best way to trigger synchronization for a drifted GitOps deployment?

Triggering GitOps synchronization via MCP uses harness_execute on gitops_application resources to inspect drift, apply repairs, and manage sync state directly.

Can I retrieve pod logs and deployment events to troubleshoot GitOps issues?

Retrieving GitOps pod logs and deployment events via MCP uses harness_get to fetch gitops_app_event and dashboard data for diagnosing deployment problems.

Does this MCP approach work for diagnosing ArgoCD health across multiple namespaces?

Diagnosing ArgoCD health across multiple namespaces via MCP applies harness_list and harness_get calls to gitops_application and gitops_dashboard resources to report deployment readiness.

Why does my GitOps application show out of sync status and how can I inspect it?

GitOps applications show out of sync status due to configuration drift; inspect this by retrieving gitops_application resources and events through Harness MCP to diagnose the exact deployment discrepancy.