gitops-workflows

GitOps deployment workflows with ArgoCD and Flux. Use this skill whenever the user mentions GitOps, ArgoCD, Flux, Flagger, Argo Rollouts, or continuous deployment to Kubernetes. Triggers include setting up ArgoCD or Flux from scratch, designing Git repository structures (monorepo vs polyrepo, app-of-apps), deploying to multiple clusters with ApplicationSets, managing secrets in Git (SOPS, Sealed Secrets, External Secrets Operator), implementing canary or blue-green deployments, troubleshooting sync or reconciliation issues, working with OCI artifacts, and comparing ArgoCD vs Flux.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%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 content is highly actionable with a strong progressive-disclosure structure pointing to real bundle files, but it loses points on conciseness from time-sensitive version clutter and a marketing claim, and on workflow clarity from missing explicit validation feedback loops around destructive/batch GitOps operations.

Suggestions

Move version numbers and dates (ArgoCD v3.1.9, Flux v2.7.1, 'October 2025', 'GA June 2025') into a clearly marked 'Version notes' or 'Deprecated' section so the main flow stays evergreen and token-efficient.

Add explicit validation checkpoints to destructive/batch workflows, e.g. after `argocd app sync` and after canary/rollout steps, a 'Verify health before proceeding' gate with a fix→retry loop.

Remove the unsupported '83% faster deployments (30min → 5min)' marketing claim or back it with a citable reference; it adds tokens without actionable value.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-heavy, but time-sensitive version/date notes ('v3.1.9', 'October 2025', 'GA June 2025') sit in the main flow rather than a deprecated section, and the '83% faster deployments' marketing claim is padding that could be trimmed.	3 / 5
Actionability	Abundant copy-paste-ready commands and complete manifests (install, ApplicationSet, GitRepository/Kustomization, SOPS workflow, Argo Rollouts, Flagger, OCIRepository) cover the common cases with exact flags and script invocations, matching the fully executable 5 anchor.	5 / 5
Workflow Clarity	The opening decision tree and numbered sections give a clear sequence, and Health Check subsections act as verification, but destructive/batch operations (sync, multi-cluster rollout, secret encryption) lack explicit validate→fix→retry feedback loops, so the destructive-ops cap holds this at 3.	3 / 5
Progressive Disclosure	The body is a well-signaled overview with one-level-deep links to real, verified bundle files (assets/, references/, scripts/) and a Resources Summary, matching the clear-overview 5 anchor with easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

100%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 across all dimensions: it concretely names capabilities, surfaces natural trigger keywords a user would say, and explicitly answers both what and when with minimal conflict risk. It follows the recommended 'Use when...' trigger convention rather than first/second-person self-reference.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — setup, repo structure, multi-cluster ApplicationSets, secrets (SOPS/Sealed/ESO), canary/blue-green, troubleshooting, OCI — giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	Explicitly states what ('GitOps deployment workflows with ArgoCD and Flux') and when ('Use this skill whenever the user mentions...') with concrete trigger phrases, satisfying the 5 anchor for both what and when.	5 / 5
Trigger Term Quality	Uses natural user-facing keywords including product synonyms (ArgoCD, Flux, Flagger, Argo Rollouts) and scenario terms (monorepo vs polyrepo, app-of-apps, canary, blue-green), matching the comprehensive synonym coverage of the 5 anchor.	5 / 5
Distinctiveness Conflict Risk	Named tools (ArgoCD, Flux, Flagger, Rollouts) and specific GitOps scenarios carve a clear niche with distinct triggers and minimal overlap with other skills, fitting the 5 anchor.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 12 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: ahmedasmar/devops-claude-skills
Path: gitops-workflows/skills/SKILL.md
Commit: 1489c33

Reviewed: 7 days 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.