agentsclimarketplace
Sign in

Helm chart scaffolding

Skill shinzoxD/knackbox/skills/coding/helm-chart-scaffolding

Scaffold and review Helm charts with safe defaults for values, templates, and hooks. Use whenever the user asks for a Helm chart, Chart.yaml, values.yaml production review, Helm upgrade hooks, or packaging a service for Helm install/upgrade.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill helm-chart-scaffolding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 304 tokens by cl100k_base, as published. Nobody here has run it

Helm Chart Scaffolding

Charts encode install defaults. Prefer safe values, clear NOTES, and upgrades that do not surprise operators.

Workflow

  1. Clarify app type (stateless API, worker, stateful), envs, and secrets model.
  2. Scaffold chart layout: Chart.yaml, values.yaml, templates/, NOTES.txt.
  3. Parameterize image, resources, probes, service, ingress, and config.
  4. Avoid dangerous defaults (privileged, latest, open 0.0.0.0 without intent).
  5. Plan hooks only when necessary; document failure modes.
  6. Review upgrade/rollback: immutable tags, PDB, migrations job separation.

Output format

## Helm chart: <name>

### Files
- Chart.yaml …
- values.yaml keys …
- templates …

### Safe defaults
…

### Install / upgrade notes
…

### Risks
…

Rules

  1. Prefer values over hardcoding in templates.
  2. Secrets via external secret refs or sealed patterns — not plain values committed.
  3. Keep templates readable; limit cleverness.
  4. Document required vs optional values.
  5. Separate app chart from environment values files.
  6. Coordinate with kubernetes-review concerns for probes/RBAC/securityContext.

Edge cases

  • Subcharts/dependencies: pin versions; watch value collisions.
  • CRDs: install order and ownership.
  • Library charts: no deployable templates; document consumers.

What ships with it: 1 file

1.3 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,861. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.