Agent skill

Atmos Helm

Native Helm components (experimental): Helm Go SDK rendering/apply/delete, components.helm, chart sources (local/repo/OCI), values, repositories, helm plugin, provision targets, and how this differs…

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Helm

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/skills/atmos-helm .claude/skills/atmos-helm && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .claude/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agent-skills/skills/atmos-helm .agents/skills/atmos-helm && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .agents/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agent-skills/skills/atmos-helm .cursor/skills/atmos-helm && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .cursor/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/cloudposse/atmos.git --path agent-skills/skills/atmos-helm

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agent-skills/skills/atmos-helm .gemini/skills/atmos-helm && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .gemini/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .github/skills && cp -r skills-src/agent-skills/skills/atmos-helm .github/skills/atmos-helm && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .github/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-helm -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-helm --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agent-skills/skills/atmos-helm .opencode/skills/atmos-helm && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "atmos-helm" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-helm into .opencode/skills/atmos-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-helm", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: atmos-helm
GitHub stars: 1.4k
Token cost: ~3.2k tokens
SKILL.md length: 1,253 words
Files: 1
Skills in repo: 70
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Tasks that involve Container orchestration
SKILL.md covers Related Skills, Native Helm vs. Helmfile, Component Shape and Commands, plus 4 more sections
Calls helm; reaches prometheus-community.github.io; needs HELM_REPO_PASSWORD

What it does

Atmos Helm is an agent skill from cloudposse/atmos. Native Helm components (experimental): Helm Go SDK rendering/apply/delete, components.helm, chart sources (local/repo/OCI), values, repositories, helm plugin, provision targets, and how this differs from Helmfile

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Container orchestration. It works with Helm, Git and Kubernetes. The repository describes itself as: Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Container orchestration

Example prompts

“/atmos-helm”

What it can do on your machine

Read from SKILL.md and the folder at commit 36726ae. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- helm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- prometheus-community.github.io
Also links to:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- HELM_REPO_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atmos Helm loads about 3.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 1,253 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~56
When it runs · the whole SKILL.md, loaded when a task matches: ~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cloudposse/atmos at commit 36726ae, republished under its Apache-2.0 licence (© cloudposse). 1,253 words, ~3,244 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-helm/SKILL.md (or your agent's skills folder).

name: atmos-helm
description: Native Helm components (experimental): Helm Go SDK rendering/apply/delete, components.helm, chart sources (local/repo/OCI), values, repositories, helm plugin, provision targets, and how this differs from Helmfile
metadata.copyright: Copyright Cloud Posse, LLC 2026
metadata.version: 1.0.0
metadata.category: orchestrators

Atmos Native Helm Components

Use this skill for the native Helm component type (components.helm). It deploys Helm charts — local, remote-repository, or OCI — through the Helm Go SDK, in-process. No helm or helmfile binary is required. This is a different component type than components.helmfile; see Native Helm vs. Helmfile below before choosing one.

This feature is experimental.

Need	Load
Helmfile-based deployments (shells out to `helmfile`/`helm`)	atmos-helmfile
Native Kubernetes manifests/Kustomize (no Helm charts)	atmos-kubernetes
Component dependency ordering for `--all`/`--affected`	atmos-components
Secret values in `values:` (`!secret`)	atmos-secrets
GitOps delivery targets (`provision.targets`, `kind: git`)	atmos-git
EKS/cluster authentication	atmos-aws-eks, atmos-auth
Native CI job summaries	atmos-ci

Native Helm vs. Helmfile

	Native Helm (`components.helm`)	Helmfile (`components.helmfile`)
Execution	Helm Go SDK, in-process	Shells out to the `helmfile` and `helm` binaries
Binaries required	None	`helmfile`, `helm` (plus any declared `helm plugin`s)
Multiple releases per component	One chart/release per component	One or more releases per `helmfile.yaml`
Diff engine	Embedded `helm-diff` library (no plugin install)	`helmfile diff` (needs `helm-diff` plugin, installed via `atmos helm plugin`)
Values	`values:`/`values_files:` merged through Atmos inheritance	Varfile generated from stack `vars:`
Status	Experimental	Stable

Use native Helm for straightforward chart deployments where you want no external binaries and first-class GitOps delivery targets. Use Helmfile (atmos-helmfile) for existing helmfile.yaml projects, multi-release releases files, or helm-secrets/other Helm CLI plugins. atmos helm plugin manages plugins for Helmfile components (native Helm does not run Helm CLI subcommand plugins).

Declare Helmfile plugins in the component's stack configuration; Atmos ensures them before running Helmfile. See Helmfile plugin configuration for declarations and optional cache warming. Do not add a plugin installation prerequisite to native Helm commands.

When maintaining plugin support, extend the existing generic installer in pkg/helm/plugin. Let Helm run each plugin's installation hooks. Keep plugin requirements with the consuming component or engine; a built-in alias such as diff does not justify a separate downloader or shell wrapper.

Component Shape

Define Helm releases under components.helm in stack manifests:

yaml

components:
  helm:
    monitoring:
      chart: prometheus-community/kube-prometheus-stack
      version: "65.1.1"
      repositories:
        - name: prometheus-community
          url: https://prometheus-community.github.io/helm-charts
      namespace: monitoring
      values:
        grafana:
          adminPassword: !secret grafana_admin_password
      dependencies:
        components:
          - cert-manager
      provision:
        default: cluster
        targets:
          cluster:
            kind: kubernetes
          deployment-repo:
            kind: git
            repository: deployments
            path: "clusters/{{ .vars.stage }}/monitoring"

Helm components use the same stack sections as other component types — vars, env, auth, metadata, settings, dependencies, hooks, inheritance, and overrides — plus Helm-specific fields:

Field	Purpose
`chart` (required)	Local path (`.`, `./charts/app`), `repo/name` reference, bare name with `repository`, or `oci://` reference.
`version`	Chart version constraint (repository/OCI charts).
`repository`	Explicit HTTP chart repository URL for a bare `chart` name.
`repositories`	List of chart repositories used to resolve `repo/name` references (`name`, `url`, basic auth, TLS files, `pass_credentials_all`, `insecure_skip_tls_verify`). Merges with global `atmos.yaml` `components.helm.repositories`; component-level entries with the same `name` win.
`namespace`	Target Kubernetes namespace. Defaults to `default`.
`create_namespace`	Whether Helm creates the target `namespace` during install when missing. Defaults to `true` (existing behavior). Set `false` to install into a pre-existing namespace, e.g. when a platform owns the namespace or a namespace-scoped identity (CI) cannot create namespaces.
`name`	Release name. Defaults to the component's last path segment.
`values`	The chart's values, merged through Atmos inheritance. This map is the values passed to the chart.
`values_files`	Value files layered underneath inline `values` (templated, in listed order).
`render`	Default output for `atmos helm template` (`output.path`, `output.split`).
`provision`	Delivery targets for `apply`/`deploy` — the cluster (default) or an external target such as a Git deployment repository.

Chart sources

Local chart — path relative to the component directory (chart: ., chart: ./charts/app), or absolute.
Remote repository chart — repository: https://... + chart: <name>, or a repo/name reference resolved against merged global/component repositories:. Atmos adds/updates these repositories in Helm's local repository config before chart operations.
OCI chart — an oci:// reference (e.g. chart: oci://ghcr.io/acme/charts/app).

Values and secrets

The component values: map is the Helm values, merged through the normal Atmos import/inheritance chain. values_files: overlay templated value files underneath the inline values. Helm has no native secrets concept — Atmos provides it: secret values flow in through !secret and are masked automatically wherever they'd otherwise be printed (e.g. in atmos helm diff output).

Commands

Command	Purpose
`atmos helm template <component> -s <stack>`	Render the chart to manifests via the Helm Go SDK (equivalent to `helm template`). No cluster or credentials needed. `render` is an alias.
`atmos helm diff <component> -s <stack>`	Real unified diff (embedded helm-diff library — no plugin install) against a baseline. `plan` is an alias.
`atmos helm values <component> -s <stack>`	Print the fully resolved chart values as formatted, masked YAML. Accepts the same Helm CLI value overrides as rendering operations.
`atmos helm apply <component> -s <stack>`	Install or upgrade the release (`helm upgrade --install`), or deliver to a `--target` provision target.
`atmos helm deploy <component> -s <stack>`	Alias for `apply`.
`atmos helm delete <component> -s <stack>`	Uninstall the release (`helm uninstall`). No-op if the release does not exist.
`atmos helm repo list [component] -s <stack>`	List declarative repository associations (global, component, or direct) and whether each is used by the resolved `chart`.
`atmos helm plugin list` / `atmos helm plugin install <plugin>...`	Manage Helm CLI plugins in the Atmos-managed `HELM_PLUGINS` directory — for Helmfile components, not native Helm.

Render and lifecycle commands (template, diff, plan, apply, deploy, delete) accept --all, --affected (with --base/--ref/--sha/--repo-path/--clone-target-ref/--ssh-key/ --ssh-key-password), and --include-dependents, matching atmos describe affected semantics. --all/--affected are mutually exclusive with a positional component argument.

Show full SKILL.md (422 more words)Show less

diff baselines

atmos helm diff (alias plan) compares the freshly rendered chart against one baseline, selected by flag precedence --from-manifest → --against → deployed release:

Baseline	Flag	Notes
Deployed release (default)	(none)	Reads the cluster; a nonexistent release shows every object as added. Only mode needing cluster access.
Local manifest	`--from-manifest=<path>`	Fully offline.
Provision target	`--against=target[:<name>]`	The manifests currently published in a non-cluster provision target (e.g. Git deployment repo) — offline, git access only. Without `:<name>` uses `provision.default`.

--context=<n> controls unified-diff context lines (default 3).

Runtime value overrides

template/render, diff/plan, values, and apply/deploy accept repeatable Helm-compatible -f/--values, --set, --set-string, --set-file, --set-json, and --set-literal flags. They are invocation-only and override component values_files then inline values; use the same flags with values, diff, and apply to inspect, preview, and deploy identical inputs.

template output

atmos helm template writes multi-document YAML to stdout by default. Use --output <file> for a single file, or --output-dir <dir> (with optional --split for one file per object). --output/ --output-dir only work rendering a single component — configure render.output on the component for --all/--affected runs.

Provision Targets (GitOps delivery)

Like native Kubernetes components, apply/deploy can deliver rendered manifests to a provision target instead of the cluster — e.g. committing them to a Git deployment repository reconciled by Argo CD/Flux:

yaml

components:
  helm:
    monitoring:
      provision:
        default: cluster
        targets:
          cluster:
            kind: kubernetes
          deployment-repo:
            kind: git
            repository: deployments
            path: "clusters/{{ .vars.stage }}/monitoring"

shell

atmos helm deploy monitoring -s plat-ue2-dev --target deployment-repo

--target defaults to provision.default, otherwise the cluster. See atmos-git for the underlying git target mechanics (clone/fast-forward, provenance trailers, credentials from Atmos Auth).

atmos.yaml Configuration

yaml

components:
  helm:
    base_path: components/helm          # default: components/helm
    auto_generate_files: false          # render component `generate:` before operations
    repositories:                       # reusable chart repositories, referenced as repo-name/chart-name
      - name: prometheus-community
        url: https://prometheus-community.github.io/helm-charts
      - name: internal
        url: https://charts.example.com
        username: !env HELM_REPO_USERNAME
        password: !env HELM_REPO_PASSWORD
        pass_credentials_all: true

Repository fields: name/url (required), username/password (basic auth), pass_credentials_all, cert_file/key_file/ca_file (TLS), insecure_skip_tls_verify. Component-level repositories entries override global entries with the same name.

Native CI Summaries

When ci.enabled: true and CI is detected (or --ci/ATMOS_CI forces it), Helm commands write a Markdown step summary through Atmos native CI — summaries only (no $GITHUB_OUTPUT, commit statuses, PR comments, or artifacts):

Command	Summary template
`template`, `render`	`ci.templates.helm.template`
`diff`, `plan`	`ci.templates.helm.diff`
`apply`, `deploy`	`ci.templates.helm.apply`
`delete`, `destroy`	`ci.templates.helm.delete`

Guidance

Prefer native Helm for new chart deployments that don't need Helm CLI subcommand plugins; use Helmfile for existing helmfile.yaml projects or plugin-dependent workflows (helm-secrets, etc.).
Use atmos helm diff before apply/deploy to review the real unified diff, not just a dry-run dump; secret values are redacted automatically.
Use dependencies.components so --all/--affected runs install/upgrade releases in the right order — Helm itself has no cross-release dependency ordering.
Use !secret for chart values that are sensitive (e.g. adminPassword) instead of plaintext in stack manifests.
Use provision.targets with kind: git to publish rendered manifests to a GitOps deployment repository instead of applying directly to a cluster.
Run atmos helm repo list to confirm which repository a component's chart resolves against before debugging chart-not-found errors.

Files

Just SKILL.md in agent-skills/skills/atmos-helm of cloudposse/atmos.

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Helm next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Atmos Helm compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Atmos Helm this skillcloudposse/atmos	1.4k	—	~3.2k	Automated safety check: Pass	Apache-2.0	today
Sim Helmsimstudioai/sim	30k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
Helm Chart ScaffoldingCybereason-Public/owLSM	280	13 repos	~381	Automated safety check: Pass	GPL-2.0	yesterday
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress	5.1k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Kubernetes SpecialistJeffallan/claude-skills	12k	1 repos	~2.1k	Automated safety check: Pass	MIT	5 days ago
Keloskelos-dev/kelos	336	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
30k GitHub stars~2.2k tokensUpdated today
DevOps & CloudAuto-check passed
Helm Chart Scaffolding
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
280 GitHub starsUsed in 13 repos~381 tokens
DevOps & CloudAuto-check passed
NGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
5.1k GitHub stars~1.4k tokensUpdated today
DevOps & CloudAuto-check passed
Kubernetes Specialist
Jeffallan/claude-skills
Creates and checks Kubernetes manifests, Helm charts, RBAC and network policies, and helps debug pod problems, with kubectl checks and rollback steps.
12k GitHub starsUsed in 1 repo~2.1k tokens
DevOps & CloudAuto-check passed
Kelos
kelos-dev/kelos
Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI.
336 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check passed
KubeShark for Kubernetes
LukasNiessen/kubernetes-skill
Keeps Kubernetes manifests, Helm charts and policies grounded by diagnosing six failure modes, such as insecure defaults and API drift, and loading only matching references.
444 GitHub stars~1.2k tokensUpdated 25 days ago
DevOps & CloudAuto-check passed

Questions about Atmos Helm

What does Atmos Helm do?

When should I use Atmos Helm?

Atmos Helm fits situations like: tasks that involve Container orchestration.

How do I install Atmos Helm in Claude Code?

Run `npx skills add cloudposse/atmos --skill atmos-helm -a claude-code`. Or copy the skill folder (agent-skills/skills/atmos-helm in cloudposse/atmos) into .claude/skills/atmos-helm in your project. Claude Code loads it when a task matches its description.

How do I install Atmos Helm in Codex?

Run `npx skills add cloudposse/atmos --skill atmos-helm -a codex`. Or copy the skill folder (agent-skills/skills/atmos-helm in cloudposse/atmos) into .agents/skills/atmos-helm in your project. Codex loads it when a task matches its description.

Can I use Atmos Helm in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudposse/atmos --skill atmos-helm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atmos-helm, .gemini/skills/atmos-helm, .github/skills/atmos-helm and .opencode/skills/atmos-helm in your project.

What does Atmos Helm need to run?

Going by SKILL.md and its folder, Atmos Helm needs the command-line tools its instructions call (helm) and credentials named HELM_REPO_PASSWORD.

Does Atmos Helm access the network?

SKILL.md names 2 domains. In commands or code: prometheus-community.github.io; the agent is likely to contact it when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Atmos Helm safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Atmos Helm use?

Atmos Helm is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atmos Helm use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atmos Helm?

Skills that share tags, products or a category with Atmos Helm: Sim Helm (simstudioai/sim, 30k stars), Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars), NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars) and Kubernetes Specialist (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Helm?

cloudposse (a GitHub organization) maintains it in cloudposse/atmos, which has 1,396 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 8, 2026.

Source: cloudposse/atmos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Atmos Helm

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Atmos Native Helm Components

Related Skills

Native Helm vs. Helmfile

Component Shape

Chart sources

Values and secrets

Commands

diff baselines

Runtime value overrides

template output

Provision Targets (GitOps delivery)

atmos.yaml Configuration

Native CI Summaries

Guidance

Files

Compare with similar skills

Similar skills

More from cloudposse/atmos

Related

Questions about Atmos Helm