Agent skill

Atmos Config

by cloudposse in cloudposse/atmos

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Config

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

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

GitHub CLI
$ gh skill install cloudposse/atmos atmos-config --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-config .claude/skills/atmos-config && 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-config
GitHub stars
1.4k
Token cost
~994 tokens
SKILL.md length
358 words
Files
2 (incl. references)
Skills in repo
70
Repo updated
First seen
Licence
Apache-2.0

At a glance

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills

  • Works in 7 steps: config CLI flag or ATMOS_CLI_CONFIG_PATH. → Active profile selected by --profile or… → Current working directory. → …
  • Tasks that involve Infrastructure as code
  • SKILL.md covers Configuration Discovery, Root Layout, Modular Imports and Routing, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atmos Config is an agent skill from cloudposse/atmos. Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills

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

It sits in DevOps & Cloud, covering Infrastructure as code. It works with Terraform. 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 Infrastructure as code

Example prompts

  • “Use the atmos-config skill to atmo root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and…”
  • “/atmos-config”

Workflow steps

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

  1. config CLI flag or ATMOS_CLI_CONFIG_PATH.
  2. Active profile selected by --profile or ATMOS_PROFILE.
  3. Current working directory.
  4. Git repository root.
  5. Parent directory walk.
  6. Home directory.
  7. System directory.

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

    No URLs in SKILL.md.

    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 Config loads about 994 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 358 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~994
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.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 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). 358 words, ~994 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-config/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
atmos-config
description
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, base_path, imports, minimal bootstrap, and routing to narrower Atmos skills
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
core-config
references
references/sections-reference.md

Atmos Root Configuration

Use this skill for the root mechanics of atmos.yaml: how Atmos finds config files, merges them, resolves project-relative paths, imports modular config, and routes section-specific work to the right skill. Do not use this skill as a catchall for every atmos.yaml section.

Configuration Discovery

Atmos searches for atmos.yaml in this order:

  1. --config CLI flag or ATMOS_CLI_CONFIG_PATH.
  2. Active profile selected by --profile or ATMOS_PROFILE.
  3. Current working directory.
  4. Git repository root.
  5. Parent directory walk.
  6. Home directory.
  7. System directory.

When multiple configuration files apply, Atmos deep-merges them. More specific sources override broader defaults.

Root Layout

Use base_path for the project root that relative paths resolve from. Keep the root config small and point subsystem paths at their owning directories:

yaml
base_path: ""

stacks:
  base_path: stacks
  included_paths:
    - "**/*"
  excluded_paths:
    - "**/_defaults.yaml"
    - "catalog/**/*"
  name_template: "{{ .vars.stage }}"

components:
  terraform:
    base_path: components/terraform

workflows:
  base_path: stacks/workflows

For deeper path/layout guidance, load atmos-project-layout.

Modular Imports

Use import to split root config into focused files:

yaml
import:
  - atmos.d/stacks.yaml
  - atmos.d/components.yaml
  - atmos.d/auth.yaml
  - atmos.d/toolchain.yaml

Imported files are deep-merged into the active configuration. Keep imported files aligned with the subsystem they configure and load the subsystem skill before changing that section.

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

Routing

NeedLoad
Root discovery, merge order, imports, minimal bootstrapstay in atmos-config
Project paths, base_path, path conventions, relative path resolutionatmos-project-layout
Profiles, --profile, ATMOS_PROFILE, profile directory merge behavioratmos-profiles
Global CLI behavior, settings, logs, errors, env, docs, metadataatmos-settings
Stack manifests, inheritance, stack imports, vars, locals, stack namingatmos-stacks
Component structure, abstract components, metadata, component inheritanceatmos-components
Terraform/OpenTofu commands, backend defaults, Terraform component settingsatmos-terraform
Helmfile, Packer, or Ansible component behavioratmos-helmfile, atmos-packer, atmos-ansible
Workflows section and workflow syntaxatmos-workflows
Custom commands and aliasesatmos-custom-commands
Auth providers, identities, keyring, cloud auth conventionsatmos-auth
Stores and store-backed YAML functionsatmos-stores
Tool versions, dependencies.tools, registries, shell/PATH integrationatmos-toolchain
Native CI, GitHub Actions, Atlantis, matrices, CI outputsatmos-ci
Schemas and validation policy configurationatmos-schemas, atmos-validation
Templates and YAML functionsatmos-templates, atmos-yaml-functions
Vendoring external componentsatmos-vendoring
Introspection commands and querying resolved configatmos-introspection

For a compact map of top-level sections, read references/sections-reference.md.

Guardrails

  • Keep atmos-config examples minimal; detailed subsystem examples belong in their narrower skills.
  • Before editing a subsystem section, load the owning skill from the routing table.
  • Prefer atmos describe config or atmos describe component when verifying merge or path behavior.

© 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-config of cloudposse/atmos.

  • SKILL.md
  • references/sections-reference.md

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Config 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 Config compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Config this skillcloudposse/atmos1.4k—~994Automated safety check: PassApache-2.0
Terraform and OpenTofu Guideagentscope-ai/QwenPaw35k6 repos~4.2kAutomated safety check: PassApache-2.0
Terraform Skillantonbabenko/terraform-skill2.4k1 repos~5.1kAutomated safety check: PassApache-2.0
Review Docshashicorp/terraform-provider-aws11k—~1.3kAutomated safety check: PassMPL-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
Cloudflarehodgef/apiker1277 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • 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
  • Terraform Skill

    antonbabenko/terraform-skill

    A skill your agent uses when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift…

    2.4k GitHub starsUsed in 1 repo~5.1k tokens
    DevOps & CloudAuto-check passed
  • Review Docs

    hashicorp/terraform-provider-aws

    Official

    Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…

    11k GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • Cloudflare

    hodgef/apiker

    Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…

    127 GitHub starsUsed in 7 repos~2.2k tokens
    DevOps & CloudAuto-check passed
  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

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 today
    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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed

Works with

Categories

Questions about Atmos Config

What does Atmos Config do?

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills. Atmos Config is an agent skill from cloudposse/atmos.

When should I use Atmos Config?

Atmos Config fits situations like: tasks that involve Infrastructure as code.

How do I install Atmos Config in Claude Code?

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

How do I install Atmos Config in Codex?

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

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

What does Atmos Config need to run?

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

Does Atmos Config access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Atmos Config 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 Config use?

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

About 994 tokens (SKILL.md is roughly 4k 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 714 tokens, read only when the agent opens those files.

What are the alternatives to Atmos Config?

Skills that share tags, products or a category with Atmos Config: Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Terraform Skill (antonbabenko/terraform-skill, 2.4k stars), Review Docs (hashicorp/terraform-provider-aws, 11k stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Config?

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.