Individual skill
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. Use when users ask to audit, analyze, validate, review, or security-check a GitOps repo.
skills/gitops-repo-audit/SKILL.md
Source commit 25da0ed5bfdd1d8f779ef79c2c7e336781978d87
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 244
- Repository last updated
- Nov 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- gitops Repository topic
- skills Repository topic
- agent-skills Repository topic
- fluxcd Repository topic
- security Derived category
- devops Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 15,337 bytesSKILL.mdcore · 15,337 bytesSKILL.mdcore · 15,337 bytesassets/schemas/alert-notification-v1.fields.txtdoc · 2,505 bytesassets/schemas/alert-notification-v1beta3.fields.txtdoc · 2,680 bytesassets/schemas/artifactgenerator-source-v1beta1.fields.txtdoc · 14,603 bytesassets/schemas/bucket-source-v1.fields.txtdoc · 8,152 bytesassets/schemas/externalartifact-source-v1.fields.txtdoc · 4,180 bytesassets/schemas/fluxinstance-fluxcd-v1.fields.txtdoc · 20,964 bytesassets/schemas/fluxreport-fluxcd-v1.fields.txtdoc · 5,523 bytesassets/schemas/gitrepository-source-v1.fields.txtdoc · 11,263 bytesassets/schemas/helmchart-source-v1.fields.txtdoc · 7,612 bytesassets/schemas/helmrelease-helm-v2.fields.txtdoc · 46,322 bytesassets/schemas/helmrepository-source-v1.fields.txtdoc · 7,537 bytesassets/schemas/imagepolicy-image-v1.fields.txtdoc · 5,783 bytesassets/schemas/imagerepository-image-v1.fields.txtdoc · 6,527 bytesassets/schemas/imageupdateautomation-image-v1.fields.txtdoc · 10,643 bytesassets/schemas/kustomization-kustomize-v1.fields.txtdoc · 20,723 bytesassets/schemas/ocirepository-source-v1.fields.txtdoc · 10,427 bytesassets/schemas/provider-notification-v1.fields.txtdoc · 3,551 bytesassets/schemas/provider-notification-v1beta3.fields.txtdoc · 3,954 bytesassets/schemas/receiver-notification-v1.fields.txtdoc · 8,143 bytesassets/schemas/resourceset-fluxcd-v1.fields.txtdoc · 10,874 bytesassets/schemas/resourcesetinputprovider-fluxcd-v1.fields.txtdoc · 10,622 bytesevals/evals.jsonasset · 17,974 bytesreferences/api-migration.mddoc · 4,352 bytesreferences/best-practices.mddoc · 15,531 bytesreferences/flux-api-summary.mddoc · 18,971 bytesreferences/flux-operator-api-summary.mddoc · 13,118 bytesreferences/repo-patterns.mddoc · 13,027 bytesreferences/security-audit.mddoc · 14,393 bytesscripts/check-deprecated.shruns · 4,172 bytesscripts/discover.shruns · 3,540 bytesscripts/validate.shruns · 22,335 bytes
Read excerpt
# GitOps Repository Auditor
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.
## Analysis Workflow
### Phase 1: Discovery