CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitops-status

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete MCP tool calls for every step and useful domain-specific reference material (health/sync states, troubleshooting). Weaknesses are the redundant resource-type listing, inconsistent parameter completeness across steps, and the absence of a post-sync verification step.

Suggestions

Delete the "Additional Resource Types" section — it duplicates the "GitOps Resource Types" table verbatim and wastes tokens.

Make parameters consistent across all steps: include org_id/project_id in the resource tree, pod log, and event steps (Steps 4-6) just as in Steps 2-3 and 7.

Add a post-sync verification step (e.g., re-check gitops_application sync status and the resource tree after executing the sync action) to close the validation loop for the one mutating operation in the workflow.

DimensionReasoningScore

Conciseness

Content is mostly lean tables and parameter blocks, but the "Additional Resource Types" code block fully duplicates the "GitOps Resource Types" table, and the seven step blocks could be condensed. Not a 2 because there is no padding or explanation of concepts Claude already knows; not a 4 because the duplicated resource-type listing is more than a minor instance of waste.

3 / 5

Actionability

Every step names the exact MCP tool (harness_get/harness_list/harness_execute) with concrete parameters, and the Examples section maps user requests to specific calls. Not a 5 because parameter completeness is inconsistent: Steps 4-6 (resource tree, pod logs, events) omit org_id/project_id that other steps require.

4 / 5

Workflow Clarity

Steps 1-7 form a clear diagnostic sequence (dashboard → list → details → resource tree → pod logs → events → sync) with Performance Notes giving diagnostic ordering and Troubleshooting sections providing error-recovery guidance. Not a 5 because there is no verification step after triggering a sync (Step 7), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The single-file body is well organized with clear sections, a resource-type reference table, and troubleshooting sections. No bundle files exist, so everything is inline; at ~159 lines the reference-table and troubleshooting material could arguably be offloaded, which keeps it below a 5.

4 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both capability and trigger conditions with natural user phrasings and good synonym coverage (GitOps/ArgoCD). Main weakness is incomplete action coverage relative to the body (pod logs, events, resource trees are not mentioned).

Suggestions

Add pod logs, application events, and resource tree inspection to the capability list so the description covers what the body actually provides.

Add a few more natural trigger variants such as "app out of sync" or "sync my application" to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Monitor GitOps application health, sync status, and manage ArgoCD deployments" names the domain and several concrete actions. Not a 3 because more than 1-2 actions are listed; not a 5 because "manage ArgoCD deployments" is generic and body capabilities like pod logs, events, and resource trees are absent from the description.

4 / 5

Completeness

Explicitly answers both: what ("Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP") and when ("Use when user says 'gitops status', 'argocd status', ...") with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say: "gitops status", "argocd status", "application sync", "gitops health", "is my app in sync", with gitops/argocd synonym coverage. Not a 5 because common variations like "sync my app", "app out of sync", or "argocd health" are missing.

4 / 5

Distinctiveness Conflict Risk

The GitOps/ArgoCD-via-Harness-MCP niche is clear and the trigger phrases ("gitops status", "argocd status", "is my app in sync") are distinct and unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

harness/harness-ai

Path

plugins/claude/skills/gitops-status/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.