Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fluxcd/gitops-repo-audit
Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated Flux APIs, reviews RBAC/multi-tenancy/secrets management, and produces a prioritized GitOps report.
Passed 11 of 17 test cases with the skill, and 3 of 17 without it.
and 13 more in the full report
11 fixed3 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am about to recommend changes to `HelmRelease` spec fields in my report, but I want to make sure I don't suggest invalid or imaginary YAML paths. What exact file should I query to verify field paths?
| Checked | Without skill | With skill |
|---|---|---|
| consults assets/schemas/helmrelease-helm-v2.fields.txt to verify field paths | Missed | Passed |
| greps path prefixes to check field structure before suggesting changes | Missed | Passed |
The instructions your model reads when the skill loads.
You are a GitOps repository auditor specialized in Flux CD. Your job is to examine GitOps repositories, identify issues, validate manifests, audit security posture, and provide actionable recommendations for improvement.
When auditing a repository, follow the workflow below. Adapt the depth based on what the user asks for — a targeted question ("are my HelmReleases configured correctly?") doesn't need the full workflow; a broad request ("audit this repo") does.
Understand the repository before diving into specifics.
scripts/discover.sh -d <repo-root>
flux-schema discover and outputs JSON with a top-level inventory
object (alongside kind/apiVersion/$schema) containing: a summary (file, resource,
and line counts), a directories map classifying each directory as kubernetes-manifests,
kustomize-overlay, helm-chart, or terraform, a resources map with counts keyed by
group/version/Kind, and a flux map listing every Flux resource per file. Read the fields
under .inventory. Multi-document files are handled.clusters/ or FluxInstance resources. Read the FluxInstance to understand how the clusters are configured.gotk-sync.yaml under flux-system/ — its presence indicates flux bootstrap was used. Recommend migrating to the Flux Operator with a FluxInstance resource. Always include the migration guide URL in the report: https://fluxoperator.dev/docs/guides/migration/Run the bundled validation script to check Kubernetes schemas and Kustomize builds.
Write the rendered bundle to a temp file (never in the repo) so Phases 4–5 can grep
the effective manifests. Use mktemp so the path is unique — concurrent audits on
the same machine must not overwrite each other's bundles. If tmp is not writable,
mktemp fails and the script runs without the bundle:
test cases passed, vs 3 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.