New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atmos Templates

by cloudposse in cloudposse/atmos

Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations

Apache-2.0Auto-check: notesDevOps & Cloud

Install Atmos Templates

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

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

GitHub CLI
$ gh skill install cloudposse/atmos atmos-templates --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-templates .claude/skills/atmos-templates && 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/

Facts

Skill name
atmos-templates
GitHub stars
1.4k
Token cost
~2k tokens
SKILL.md length
570 words
Files
2 (incl. references)
Skills in repo
70
Repo updated
First seen
Licence
Apache-2.0

At a glance

Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations

  • Works in 5 steps: Prefer YAML functions over Go templates… → Prefer !store over atmos.Component for… → Use atmos.GomplateDatasource instead of… → …
  • DevOps & Cloud work in your project
  • SKILL.md covers Overview, Enabling Go Templates, Template Context Variables and Template Examples, plus 10 more sections
  • Reaches api.ipify.org

What it does

Atmos Templates is an agent skill from cloudposse/atmos. Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/go-templates.md`).

It sits in DevOps & Cloud. 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

  • DevOps & Cloud work in your project

Example prompts

  • “/atmos-templates”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Prefer YAML functions over Go templates -- Type-safe, cannot break YAML
  2. Prefer !store over atmos.Component for outputs -- Avoids Terraform initialization
  3. Use atmos.GomplateDatasource instead of datasource -- Built-in caching prevents
  4. Minimize atmos.Component usage -- Each call may initialize Terraform
  5. All template functions cache results per execution for repeated calls.

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    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:

    • api.ipify.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atmos Templates loads about 2k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 570 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:53
    | `.env.*` | Environment variables |

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). 570 words, ~2,031 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-templates/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
atmos-templates
description
Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
templating-data
references
references/go-templates.md

Atmos Go Templates

Overview

Go templates use {{ }} delimiters and are processed before YAML parsing. They support the full Go text/template syntax plus Sprig and Gomplate function libraries.

Go templates are an escape hatch for complex conditional logic, loops, dynamic key generation, or advanced string manipulation that YAML functions cannot handle. For most use cases, prefer YAML functions (see the atmos-yaml-functions skill).

Enabling Go Templates

yaml
# atmos.yaml
templates:
  settings:
    enabled: true
    evaluations: 1      # Number of processing passes
    delimiters: ["{{", "}}"]  # Default delimiters
    sprig:
      enabled: true     # Enable Sprig functions
    gomplate:
      enabled: true     # Enable Gomplate functions and datasources
      timeout: 5        # Datasource timeout in seconds

Template Context Variables

In Go templates, you can reference any value from the component's configuration (as returned by atmos describe component):

VariableDescription
.atmos_componentThe Atmos component name
.atmos_stackThe Atmos stack name
.stackAlias for .atmos_stack
.atmos_stack_fileThe stack manifest file path
.workspaceThe Terraform workspace name
.vars.*Component variables
.settings.*Component settings
.env.*Environment variables
.metadata.*Component metadata
.providers.*Provider configuration
.backend.*Backend configuration
.backend_typeBackend type string

Template Examples

yaml
components:
  terraform:
    vpc:
      vars:
        tags:
          atmos_component: "{{ .atmos_component }}"
          atmos_stack: "{{ .atmos_stack }}"
          terraform_workspace: "{{ .workspace }}"
          # Sprig function
          provisioned_by: '{{ env "USER" }}'
          # Gomplate function
          description: "{{ strings.Title .atmos_component }} in {{ .atmos_stack }}"

atmos.Component Template Function

Reads any section or attribute from another component's configuration, including Terraform outputs:

yaml
vars:
  # Read outputs (remote state)
  vpc_id: '{{ (atmos.Component "vpc" .stack).outputs.vpc_id }}'

  # Read variables from another component
  vpc_name: '{{ (atmos.Component "vpc" .stack).vars.name }}'

  # Read settings
  test_setting: '{{ (atmos.Component "test" .stack).settings.test }}'

  # Read metadata
  component_name: '{{ (atmos.Component "test" .stack).metadata.component }}'

  # Complex outputs require !template + toJson
  subnet_ids: !template '{{ toJson (atmos.Component "vpc" .stack).outputs.private_subnet_ids }}'

atmos.GomplateDatasource Template Function

Fetches external data with automatic caching:

yaml
settings:
  templates:
    settings:
      gomplate:
        datasources:
          ip:
            url: "https://api.ipify.org?format=json"
          secret:
            url: "aws+smp:///path/to/secret"

vars:
  public_ip: '{{ (atmos.GomplateDatasource "ip").ip }}'
  db_password: '{{ (atmos.GomplateDatasource "secret").password }}'

The function caches results per execution -- multiple references to the same datasource make only one external call.

atmos.Store Template Function

Reads from stores using Go template syntax (same as !store YAML function but in template form):

yaml
vars:
  vpc_id: '{{ atmos.Store "prod/ssm" .stack "vpc" "vpc_id" }}'
  config: !template '{{ (atmos.Store "redis" .stack "config" "config_map").defaults | toJSON }}'

Template Evaluations (Processing Pipelines)

Atmos supports multiple evaluation passes for template processing:

yaml
# atmos.yaml
templates:
  settings:
    enabled: true
    evaluations: 2  # Two passes

With multiple evaluations, output from the first pass becomes input to the second pass. This is useful for:

  • Combining templates from different sections
  • Using templates in datasource URLs
  • Multi-stage template resolution

Excluding Templates from Processing

Passing Templates to External Tools

Use the backtick escape or !literal to prevent Atmos from processing templates intended for external systems (ArgoCD, Helm, Datadog):

yaml
# Using !literal (recommended, see atmos-yaml-functions skill)
annotation: !literal "{{ .Values.ingress.class }}"

# Using backtick escape
annotation: "{{`{{ .Values.ingress.class }}`}}"

# Using printf
annotation: '{{ printf "{{ .Values.ingress.class }}" }}'
Templates in Imports

When using Go templates in both imports and stack manifests, templates intended for the second pass (stack processing) must be escaped in the import file:

yaml
# stacks/catalog/eks/eks_cluster.tmpl
components:
  terraform:
    eks/cluster:
      vars:
        # First pass: resolved from import context
        enabled: "{{ .enabled }}"
        name: "{{ .name }}"
        tags:
          # Second pass: escaped for stack processing
          atmos_component: "{{`{{ .atmos_component }}`}}"
          atmos_stack: "{{`{{ .atmos_stack }}`}}"

Template Configuration in Stack Manifests

Template settings can be defined in settings.templates.settings in stack manifests, which deep-merges with templates.settings in atmos.yaml. Stack manifest settings take precedence.

yaml
# stacks/orgs/acme/_defaults.yaml
settings:
  templates:
    settings:
      env:
        AWS_PROFILE: "my-profile"
      gomplate:
        timeout: 7
        datasources:
          config:
            url: "./my-config.json"

Note: enabled, sprig.enabled, gomplate.enabled, evaluations, and delimiters settings are not supported in stack manifests (only in atmos.yaml).

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

When to Use Go Templates vs. YAML Functions

ScenarioUse
Reading Terraform outputsYAML functions: !terraform.state or !terraform.output
Reading store valuesYAML functions: !store or !store.get
Environment variablesYAML function: !env
Including filesYAML function: !include
Complex outputs (lists/maps)!template with toJson
Conditional logic (if/else)Go templates
Loops and iterationGo templates
Dynamic key generationGo templates
External API dataatmos.GomplateDatasource
Advanced string manipulationGo templates with Sprig/Gomplate

Performance Best Practices

  1. Prefer YAML functions over Go templates -- Type-safe, cannot break YAML
  2. Prefer !store over atmos.Component for outputs -- Avoids Terraform initialization
  3. Use atmos.GomplateDatasource instead of datasource -- Built-in caching prevents redundant API calls
  4. Minimize atmos.Component usage -- Each call may initialize Terraform
  5. All template functions cache results per execution for repeated calls.

Common Pitfalls

  1. Go templates break YAML -- Unquoted {{ }} can cause YAML parse errors. Always quote template expressions.
  2. Type confusion -- Go templates always return strings. Use !template with toJson for complex types.
  3. Indentation issues -- Multi-line template output can break YAML indentation.
  4. Sprig/Gomplate conflicts -- The env function exists in both libraries with different syntax. Use getenv for Gomplate's version when both are enabled.
  5. Performance degradation -- Overuse of atmos.Component or !terraform.output across many stacks can dramatically slow atmos describe stacks and atmos describe affected.

Additional Resources

  • For complete Go template context variables and functions, see references/go-templates.md
  • For YAML functions (!terraform.state, !store, !env, etc.), see the atmos-yaml-functions skill

© cloudposse, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in agent-skills/skills/atmos-templates of cloudposse/atmos.

  • SKILL.md
  • references/go-templates.md

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Templates 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 Templates compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Templates this skillcloudposse/atmos1.4k—~2kAutomated safety check: NotesApache-2.0
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw35k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k9 repos~4.3kAutomated safety check: PassNone
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    35k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 9 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Analyze GitHub Action Logs

    withastro/astro

    Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed

  • KubeSphere Multi-Tenant Management

    kubesphere/kubesphere

    Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.

    17k GitHub starsUsed in 1 repo~3.1k tokens
    DevOps & CloudAuto-check passed

More from cloudposse/atmos

All 70 skills in this repo

  • Fix Log

    cloudposse/atmos

    A skill your agent uses when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should…

    1.4k GitHub stars~685 tokensUpdated yesterday
    Auto-check passed

  • Atmos Lint

    cloudposse/atmos

    Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Changelog

    cloudposse/atmos

    Blog post authoring for Atmos: MDX template, frontmatter, website/blog/tags.yml and authors.yml rules, problem-first framing, backtick-opening ban, optional cast embeds, and no-Go-internals leakage.

    1.4k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Editions

    cloudposse/atmos

    Decide whether a PR's new or changed default needs edition-journal handling (pkg/edition, docs/prd/editions.md), and do the mechanical work if so: journal entries, the four-layer default check…

    1.4k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Atmos Migration

    cloudposse/atmos

    Migrate to Atmos from native Terraform, Terraform Workspaces, Terramate, Terragrunt, Make, Just, or Task; migrate tool versions from mise or Aqua CLI; migrate AWS/GCP/Azure CLI configs, Leapp…

    1.4k GitHub stars~5.1k tokensUpdated yesterday
    Auto-check: warnings

  • PR Maintenance Loop

    cloudposse/atmos

    Start an hourly background loop that keeps the current branch's PR rebased, its addressed CodeRabbit threads resolved, its CI checks passing, its lint clean, its tests passing with adequate patch…

    1.4k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Atmos Templates

What does Atmos Templates do?

Go templates: Sprig/Gomplate functions, Atmos's own collectKeys, atmos.Component, atmos.GomplateDatasource, atmos.Store, template configuration, evaluations. Atmos Templates is an agent skill from cloudposse/atmos.

When should I use Atmos Templates?

Atmos Templates fits situations like: devOps & Cloud work in your project.

How do I install Atmos Templates in Claude Code?

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

How do I install Atmos Templates in Codex?

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

Can I use Atmos Templates 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-templates -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-templates, .gemini/skills/atmos-templates, .github/skills/atmos-templates and .opencode/skills/atmos-templates in your project.

What does Atmos Templates need to run?

SKILL.md names no scripts, command-line tools or credentials: Atmos Templates is instructions for the agent only.

Does Atmos Templates access the network?

SKILL.md names 1 domain. In commands or code: api.ipify.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Atmos Templates safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Atmos Templates use?

Atmos Templates 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 Templates use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Atmos Templates?

Skills that share tags, products or a category with Atmos Templates: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Templates?

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.