How do I install the Techtide Fluxcd Kustomization Helmrelease Review skill?

Run npx skillmds@latest add techtideohio/techtide-fluxcd-kustomization-helmrelease-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Techtide Fluxcd Kustomization Helmrelease Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Techtide Fluxcd Kustomization Helmrelease Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Techtide Fluxcd Kustomization Helmrelease Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Techtide Fluxcd Kustomization Helmrelease Review?

TechTideOhio (@techtideohio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Techtide Fluxcd Kustomization Helmrelease Review by techtideohio

Name: Techtide Fluxcd Kustomization Helmrelease Review
Author: TechTideOhio

Techtide Fluxcd Kustomization Helmrelease Review

Use this skill when reviewing FluxCD Kustomization, HelmRelease, GitRepository, HelmRepository, or OCIRepository resources. Trigger when the user asks whether a Flux configuration is safe for production, whether SOPS encryption is required, whether prune is safe on a given workload, whether commit signature verification is enabled, or whether a Flux multi-tenant setup uses least-privilege ServiceAccounts.

TechTideOhio Updated Sep 17, 2026

File contents

FluxCD Kustomization and HelmRelease Review

Purpose

Review FluxCD Kustomization, HelmRelease, GitRepository, HelmRepository, and OCIRepository resources for source trust guarantees, SOPS secret encryption, prune-enabled blast radius on stateful workloads, per-Kustomization ServiceAccount scoping, HelmRelease upgrade remediation safety, and health check completeness. FluxCD's default posture gives the kustomize-controller cluster-admin-equivalent reach - the security surface lives in per-Kustomization ServiceAccounts, commit signature verification, SOPS encryption at rest, and prune annotation guards.

Lean operating rules

Prefer user-provided sanitized resource YAML as primary evidence; official FluxCD docs are the authoritative fallback.
Treat unencrypted Kubernetes Secret manifests committed to any Git source as a CRITICAL finding - anyone with repo read access (CI, PR participants, auditors) has those secrets.
Treat GitRepository.spec.ref.semver: ">=0.0.0" or an unbound semver range in a production source as a HIGH finding - any tag push from a compromised upstream triggers a deploy.
Treat the absence of spec.verify.secretRef (commit GPG signature verification) on production GitRepository sources as a HIGH finding.
Treat Kustomization.spec.serviceAccountName not set as a HIGH finding - the kustomize-controller SA applies with cluster-admin-equivalent scope for all tenants.
Treat spec.prune: true on Kustomizations covering stateful workloads (StatefulSets, PVCs, CRDs) without kustomize.toolkit.fluxcd.io/prune: disabled annotations as a HIGH finding.
Treat HelmRelease.spec.chart.spec.version: "*" or an unbound version range as a HIGH finding - any upstream chart publish triggers an auto-upgrade.
Treat HelmRelease.spec.upgrade.remediation.retries: -1 (infinite retry) as a MEDIUM finding - a broken release blocks other reconciliation loops indefinitely.
Keep the answer scoped: report what was reviewed, the evidence level, and the exact field path for each finding.

References

Load these only when needed:

Workflow and output contract

Response minimum

Scoped target (resource kind/name/namespace) and evidence level
Source trust verdict (commit verification, semver pinning, SOPS encryption)
Kustomization ServiceAccount scope assessment
Prune safety verdict for any stateful workloads
HelmRelease version pinning and upgrade remediation assessment
Health check completeness verdict
Safe next actions and open questions

---name: techtide-fluxcd-kustomization-helmrelease-reviewdescription: Use this skill when reviewing FluxCD Kustomization, HelmRelease, GitRepository, HelmRepository, or OCIRepository resources. Trigger when the user asks whether a Flux configuration is safe for production, whether SOPS encryption is required, whether prune is safe on a given workload, whether commit signature verification is enabled, or whether a Flux multi-tenant setup uses least-privilege ServiceAccounts.---# FluxCD Kustomization and HelmRelease Review## PurposeReview FluxCD `Kustomization`, `HelmRelease`, `GitRepository`, `HelmRepository`, and `OCIRepository` resources for source trust guarantees, SOPS secret encryption, prune-enabled blast radius on stateful workloads, per-Kustomization ServiceAccount scoping, HelmRelease upgrade remediation safety, and health check completeness. FluxCD's default posture gives the `kustomize-controller` cluster-admin-equivalent reach - the security surface lives in per-Kustomization ServiceAccounts, commit signature verification, SOPS encryption at rest, and prune annotation guards.## Lean operating rules- Prefer user-provided sanitized resource YAML as primary evidence; official FluxCD docs are the authoritative fallback.- Treat unencrypted Kubernetes `Secret` manifests committed to any Git source as a CRITICAL finding - anyone with repo read access (CI, PR participants, auditors) has those secrets.- Treat `GitRepository.spec.ref.semver: ">=0.0.0"` or an unbound semver range in a production source as a HIGH finding - any tag push from a compromised upstream triggers a deploy.- Treat the absence of `spec.verify.secretRef` (commit GPG signature verification) on production `GitRepository` sources as a HIGH finding.- Treat `Kustomization.spec.serviceAccountName` not set as a HIGH finding - the kustomize-controller SA applies with cluster-admin-equivalent scope for all tenants.- Treat `spec.prune: true` on Kustomizations covering stateful workloads (StatefulSets, PVCs, CRDs) without `kustomize.toolkit.fluxcd.io/prune: disabled` annotations as a HIGH finding.- Treat `HelmRelease.spec.chart.spec.version: "*"` or an unbound version range as a HIGH finding - any upstream chart publish triggers an auto-upgrade.- Treat `HelmRelease.spec.upgrade.remediation.retries: -1` (infinite retry) as a MEDIUM finding - a broken release blocks other reconciliation loops indefinitely.- Keep the answer scoped: report what was reviewed, the evidence level, and the exact field path for each finding.## ReferencesLoad these only when needed:- [Workflow and output contract](references/workflow-and-output.md)## Response minimum- Scoped target (resource kind/name/namespace) and evidence level- Source trust verdict (commit verification, semver pinning, SOPS encryption)- Kustomization ServiceAccount scope assessment- Prune safety verdict for any stateful workloads- HelmRelease version pinning and upgrade remediation assessment- Health check completeness verdict- Safe next actions and open questions

Frequently asked questions