GitOps with ArgoCD and Flux
wshobson/agents
Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.
Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP.
Install Gitops Status
$ npx skills add harness/harness-skills --skill gitops-status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install harness/harness-skills gitops-status --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gitops-status .claude/skills/gitops-status && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .claude/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/harness/harness-skills/tree/main/skills/gitops-statusType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add harness/harness-skills --skill gitops-status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install harness/harness-skills gitops-status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gitops-status .agents/skills/gitops-status && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .agents/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add harness/harness-skills --skill gitops-status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install harness/harness-skills gitops-status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gitops-status .cursor/skills/gitops-status && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .cursor/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/harness/harness-skills.git --path skills/gitops-status--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add harness/harness-skills --skill gitops-status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install harness/harness-skills gitops-status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gitops-status .gemini/skills/gitops-status && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .gemini/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install harness/harness-skills gitops-statusInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add harness/harness-skills --skill gitops-status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gitops-status .github/skills/gitops-status && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .github/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add harness/harness-skills --skill gitops-status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install harness/harness-skills gitops-status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/harness/harness-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gitops-status .opencode/skills/gitops-status && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gitops-status" agent skill from https://github.com/harness/harness-skills/tree/main/skills/gitops-status into .opencode/skills/gitops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitops-status", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gitops-status- GitHub stars
- 115
- Token cost
- ~1.1k tokens
- SKILL.md length
- 290 words
- Files
- 1
- Skills in repo
- 64
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP.
- Works in 7 steps: Overview Dashboard → List Applications → Get Application Details → …
- User says gitops status
- SKILL.md covers Instructions, Additional Resource Types, GitOps Resource Types and Application Health States, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Gitops Status is an agent skill from harness/harness-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires Harness MCP v2 server (harness-mcp-v2)
It sits in DevOps & Cloud, covering GitOps and Container orchestration. It works with Argo CD, Model Context Protocol and Git. The repository describes itself as: A collection of structured AI agent skills that enable Claude Code, Cursor, GitHub Copilot, and other AI coding assistants to create, operate, debug, and govern Harness CI/CD… The licence is Apache-2.0.
When your agent uses it
- User says gitops status
- Application sync
- Is my app in sync
- Asks about GitOps applications
Example prompts
- “gitops status”
- “argocd status”
- “application sync”
- “/gitops-status”
Requirements
- Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2)
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c25faee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Harness MCP v2 server (harness-mcp-v2)
From compatibility in the SKILL.md frontmatter.
Context cost
Gitops Status loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 290 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from harness/harness-skills at commit c25faee, republished under its Apache-2.0 licence (© harness). 290 words, ~1,052 tokens.
Download SKILL.mdSave it as
.claude/skills/gitops-status/SKILL.md (or your agent's skills folder).- name
- gitops-status
- description
- 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.
- compatibility
- Requires Harness MCP v2 server (harness-mcp-v2)
- metadata.author
- Harness
- metadata.version
- 2.0.0
- metadata.mcp-server
- harness-mcp-v2
- license
- Apache-2.0
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
© harness, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/gitops-status of harness/harness-skills.
Open the folder on GitHubat commit c25faee
Compare with similar skills
Gitops Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gitops Status this skillharness/harness-skills | 115 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| GitOps with ArgoCD and Fluxwshobson/agents | 40k | 11 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Ksaildevantler-tech/ksail | 166 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Argocd GitopsBagelHole/DevOps-Security-Agent-Skills | 1.1k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Implementing Gitopsancoleman/ai-design-components | 526 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Argocd Gitopssickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ksail
devantler-tech/ksail
Use the ksail CLI to spin up and manage Kubernetes clusters (Kind/K3d/Talos/vCluster/KWOK — local via Docker; EKS — cloud via AWS) and GitOps workloads declaratively.
Argocd Gitops
BagelHole/DevOps-Security-Agent-Skills
Implement GitOps with ArgoCD for declarative Kubernetes deployments.
Implementing Gitops
ancoleman/ai-design-components
Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux.
Argocd Gitops
sickn33/agentic-awesome-skills
Implement GitOps with ArgoCD for declarative Kubernetes deployments.
Gitops Practitioner
FerroxLabs/wayland
GitOps expertise covering ArgoCD, Flux, declarative infrastructure management, drift detection and reconciliation, environment promotion strategies, secrets in GitOps, multi-cluster management, and…
More from harness/harness-skills
All 64 skills in this repoAudit Report
harness/harness-skills
Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.
Chaos Dr Test
harness/harness-skills
A skill your agent uses when working with Chaos Engineering steps inside a Harness pipeline.
Chaos Experiment
harness/harness-skills
A skill your agent uses when the user asks to create, edit, update, design, or configure a Harness Chaos Experiment — including faults, probes, actions, experiment YAML, fault injection, pod-delete…
Cleanup Feature Flags
harness/harness-skills
Remove a launched Harness FME feature flag from application code, keeping the treatment FME serves today, and open a pull request.
Configure Repo Scan
harness/harness-skills
Configure code scanning in Harness pipelines using STO security scanners.
Create Agent Template
harness/harness-skills
Generate Harness Agent Template files for AI-powered automation agents.
Related
Works with
Categories
Questions about Gitops Status
What does Gitops Status do?
Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP. Gitops Status is an agent skill from harness/harness-skills. Monitor GitOps application health, sync status, and manage ArgoCD deployments via Harness MCP.
When should I use Gitops Status?
Gitops Status fits situations like: user says gitops status; application sync; is my app in sync; asks about GitOps applications.
How do I install Gitops Status in Claude Code?
Run `npx skills add harness/harness-skills --skill gitops-status -a claude-code`. Or copy the skill folder (skills/gitops-status in harness/harness-skills) into .claude/skills/gitops-status in your project. Claude Code loads it when a task matches its description.
How do I install Gitops Status in Codex?
Run `npx skills add harness/harness-skills --skill gitops-status -a codex`. Or copy the skill folder (skills/gitops-status in harness/harness-skills) into .agents/skills/gitops-status in your project. Codex loads it when a task matches its description.
Can I use Gitops Status in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add harness/harness-skills --skill gitops-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitops-status, .gemini/skills/gitops-status, .github/skills/gitops-status and .opencode/skills/gitops-status in your project.
What does Gitops Status need to run?
SKILL.md names no scripts, command-line tools or credentials: Gitops Status is instructions for the agent only. Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2).
Does Gitops Status access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gitops Status safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gitops Status use?
Gitops Status is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gitops Status use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gitops Status?
Skills that share tags, products or a category with Gitops Status: GitOps with ArgoCD and Flux (wshobson/agents, 40k stars), Ksail (devantler-tech/ksail, 166 stars), Argocd Gitops (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars) and Implementing Gitops (ancoleman/ai-design-components, 526 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gitops Status?
harness (a GitHub organization) maintains it in harness/harness-skills, which has 115 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 6, 2026.
Source: harness/harness-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.