gitops-workflow

Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.

1.09x

Quality

78%

Does it follow best practices?

Impact

84%

1.09x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/kubernetes-operations/skills/gitops-workflow/SKILL.md

The canonical home for this skill is gitops-workflow in wshobson/agents

Quality

Content

68%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 a mostly efficient, action-dense GitOps reference with executable ArgoCD and Flux examples and well-signaled reference files. Its main weakness is workflow clarity: cluster-mutating and automated-sync operations proceed without validation checkpoints or error-recovery loops, capping that dimension at 3.

Suggestions

Add validation checkpoints to the ArgoCD/Flux setup steps (e.g., after install verify with `argocd account get-user-info` / `flux check`, and after applying an Application confirm sync health before proceeding), with a fix-and-retry loop on failure.

Move the bulkier manifest examples (Rollout, ExternalSecret, App-of-Apps) into reference files and keep only one representative snippet inline, improving both conciseness and progressive disclosure.

Trim the OpenGitOps principles preamble and 'Complete guide' intro, which restate concepts Claude already knows, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly lean — sections open with brief intros then drop into code, assuming Claude's competence. Minor over-explanation: the 'Complete guide to...' preamble and the OpenGitOps principles section restate concepts Claude already knows.	4 / 5
Actionability	Abundant copy-paste ready guidance: kubectl/flux CLI commands and full YAML manifests (Application, GitRepository, Kustomization, Rollout, ExternalSecret). Minor gaps: the App-of-Apps example uses an empty automated policy and some manifests omit namespace/destination completeness.	4 / 5
Workflow Clarity	Steps are numbered (ArgoCD setup 1-4, Flux 1-3) but operations that mutate cluster state (kubectl apply, automated prune/selfHeal, flux bootstrap) lack validation checkpoints or a validate-fix-retry feedback loop, so the destructive/batch cap applies.	3 / 5
Progressive Disclosure	Two real reference files (argocd-setup.md, sync-policies.md) are signaled inline with clear 'See references/...' pointers, and sections are well organized. However, substantial manifest content that could live in references is inlined in SKILL.md rather than split out.	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.

The description is strong: it uses third-person voice, states concrete capabilities, and provides explicit 'Use when...' trigger guidance covering several natural phrases. The main gap is slightly fuller enumeration of capabilities and a few missing synonyms (continuous delivery, standalone tool names).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('automated, declarative Kubernetes deployments with continuous reconciliation' for ArgoCD and Flux), but does not enumerate the full range of GitOps capabilities (progressive delivery, secret management, multi-cluster) that the skill body covers.	4 / 5
Completeness	Clearly answers what ('Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation') and when ('Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('GitOps', 'Kubernetes deployments', 'automating deployments', 'declarative infrastructure management'), but missing common synonyms such as 'continuous delivery', 'CD pipeline', or standalone 'ArgoCD'/'Flux' triggers a user might say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitOps via ArgoCD/Flux for Kubernetes) with distinct triggers; minimal overlap risk with adjacent skills like k8s-manifest-generator or helm-chart-scaffolding.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/kubernetes-operations/skills/gitops-workflow/SKILL.md
Commit: 6453c0b

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.