gitops-status SKILL.md skillA
gitops-status from harness/harness-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harness/harness-skills/gitops-status@v2.0.0Pins v2.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harness/harness-skills
- Path
skills/observability-governance/gitops-status/SKILL.md- Versions recorded
- 1
- Latest version
- v2.0.0, committed Oct 14, 2026
- Size
- 4,270 bytes
- Repository stars
- 122
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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>" …
Read the whole file at its exact version.
How to install
mdr add harness/harness-skills/gitops-status@sha256:9205012fc77e7b3bThe line at the top of this page pins the label v2.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qec6v77cepnu2f5g)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4270 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
harness/harness-skills · 122 stars · license Apache-2.0 · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qec6v77cepnu2f5g GET https://markdownregistry.com/api/v1/resolve?ref=harness/harness-skills/gitops-status GET https://markdownregistry.com/api/v1/blob/9205012fc77e7b3bb3f21231032515f2053a21eb5be9b0689b814b12ba0305dc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.