Agent skill

Atmos Settings

Atmos global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior, telemetry, experimental flags, and non-subsystem atmos.yaml options

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Settings

skills CLI

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

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

GitHub CLI

$ gh skill install cloudposse/atmos atmos-settings --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-settings .claude/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .claude/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings

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-settings -a codex

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

GitHub CLI

$ gh skill install cloudposse/atmos atmos-settings --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-settings .agents/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .agents/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings -a cursor

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

GitHub CLI

$ gh skill install cloudposse/atmos atmos-settings --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-settings .cursor/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .cursor/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings

--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-settings -a gemini-cli

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

GitHub CLI

$ gh skill install cloudposse/atmos atmos-settings --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-settings .gemini/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .gemini/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings

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-settings -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-settings .github/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .github/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings -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-settings --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-settings .opencode/skills/atmos-settings && 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-settings" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-settings into .opencode/skills/atmos-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-settings", 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-settings
GitHub stars: 1.4k
Token cost: ~1k tokens
SKILL.md length: 286 words
Files: 1
Skills in repo: 70
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Atmos global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior, telemetry, experimental flags, and non-subsystem atmos.yaml options

DevOps & Cloud work in your project
SKILL.md covers Owned Sections, Common Pattern, Terminal Appearance and Color and Routing, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atmos Settings is an agent skill from cloudposse/atmos. Atmos global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior, telemetry, experimental flags, and non-subsystem atmos.yaml options

Its SKILL.md is about 1k 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. 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

“Use the atmos-settings skill to atmo global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior…”
“/atmos-settings”

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 and bash).
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 Settings loads about 1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 286 words of instructions outside code blocks.

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

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). 286 words, ~1,003 tokens.

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

name: atmos-settings
description: Atmos global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior, telemetry, experimental flags, and non-subsystem atmos.yaml options
metadata.copyright: Copyright Cloud Posse, LLC 2026
metadata.version: 1.0.0
metadata.category: core-config

Atmos Settings

Use this skill for global atmos.yaml options that are not owned by a narrower subsystem skill.

Owned Sections

Section	Use for
`settings`	Global CLI behavior, terminal behavior, telemetry, experimental options
`logs`	Log level, log file path, debug output behavior
`errors`	Error output formatting and error reporting options
`env`	Environment variables applied to Atmos operations
`docs`	Documentation generation defaults
`metadata`	Project-level metadata such as name, tags, and version
`version`	Minimum or maximum Atmos version constraints

If a setting belongs to a subsystem such as templates, validation, auth, CI, or toolchain, load that subsystem skill instead.

Common Pattern

yaml

settings:
  terminal:
    pager: false
    syntax_highlighting:
      enabled: true
  telemetry:
    enabled: false

logs:
  level: Info

env:
  AWS_REGION: us-east-1

metadata:
  name: platform-infrastructure

Terminal Appearance and Color

settings.terminal controls Atmos's terminal output appearance (color, theme, width, unicode, syntax highlighting, pager). Fields:

yaml

settings:
  terminal:
    color: true               # Explicitly force color on (overrides TTY auto-detection)
    no_color: false           # Deprecated: use the --no-color flag or ATMOS_NO_COLOR/NO_COLOR/CLICOLOR env vars instead
    force_color: false        # ENV-only (ATMOS_FORCE_COLOR) -- not settable from this config field
    theme: dracula             # Theme name; see `atmos theme list` for available names
    max_width: 120
    unicode: true
    syntax_highlighting:
      enabled: true
    pager: false               # false/true/off/on/"less"/a specific pager command

Precedence: no_color (config) is deprecated in favor of the --no-color flag/env vars below. IsColorEnabled logic: no_color forces color off; else explicit color: true forces it on; otherwise Atmos falls back to TTY auto-detection.

Flags and Environment Variables

Flag	Env vars	Effect
`--no-color`	`ATMOS_NO_COLOR`, `NO_COLOR`, `CLICOLOR`	Disable color output
`--force-color`	`ATMOS_FORCE_COLOR`, `CLICOLOR_FORCE`	Force color output even when not a TTY (e.g. piped/CI output, screenshots)

`atmos theme` Commands

Discover and preview themes (a theme controls tables, markdown rendering, and help text colors):

shell

atmos theme list                 # List all available themes
atmos theme list --recommended   # Only themes tested for optimal compatibility
atmos theme show <theme-name>    # Preview a theme's palette and sample UI elements
atmos theme browse               # Interactive/searchable theme gallery (docs site)
atmos list themes                # Alias for 'theme list'; defaults to recommended-only, use --all for all

Activate a theme via ATMOS_THEME=<theme-name> env var or settings.terminal.theme in atmos.yaml.

Routing

Need	Load
Template settings	`atmos-templates`
Validation settings and policies	`atmos-validation`, `atmos-schemas`
Auth or identity settings	`atmos-auth`
Native CI settings	`atmos-ci`
Toolchain settings	`atmos-toolchain`
Stack/component `settings` fields	`atmos-stacks`, `atmos-components`

Guardrails

Treat env as global process environment. Use component, workflow, command, or auth-specific env settings when only one execution context needs the variable.
Do not put subsystem-specific details here just because they live under settings; route to the owning skill first.
Prefer explicit, stable global settings over hidden shell assumptions.

Files

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

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Settings 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 Settings compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Atmos Settings this skillcloudposse/atmos	1.4k	—	~1k	Automated safety check: Pass	Apache-2.0	today
Monitor CInrwl/nx	29k	6 repos	~4.7k	Automated safety check: Pass	MIT	today
Terraform and OpenTofu Guideagentscope-ai/QwenPaw	35k	6 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Vercel Optimize Auditvercel-labs/agent-skills	32k	9 repos	~4.3k	Automated safety check: Pass	None	1 mo ago
Openclaw Live Updateropenclaw/openclaw	392k	—	~3.7k	Automated safety check: Pass	MIT	today
Analyze GitHub Action Logswithastro/astro	63k	1 repos	~1.3k	Automated safety check: Pass	Custom licence	yesterday

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

Questions about Atmos Settings

What does Atmos Settings do?

Atmos global settings: settings, logs, errors, env, docs, metadata, version requirements, terminal behavior, telemetry, experimental flags, and non-subsystem atmos.yaml options. Atmos Settings is an agent skill from cloudposse/atmos.

When should I use Atmos Settings?

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

How do I install Atmos Settings in Claude Code?

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

How do I install Atmos Settings in Codex?

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

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

What does Atmos Settings need to run?

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

Does Atmos Settings 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 Settings 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 Settings use?

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

About 1k 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.

What are the alternatives to Atmos Settings?

Skills that share tags, products or a category with Atmos Settings: 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 Settings?

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.

Atmos Settings

Install Atmos Settings

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 Settings

Owned Sections

Common Pattern

Terminal Appearance and Color

Flags and Environment Variables

`atmos theme` Commands

Routing

Guardrails

Files

Compare with similar skills

Similar skills

Monitor CI

Terraform and OpenTofu Guide

Vercel Optimize Audit

Openclaw Live Updater

Analyze GitHub Action Logs

KubeSphere Multi-Tenant Management

More from cloudposse/atmos

Fix Log

Atmos Lint

Changelog

Editions

Atmos Migration

PR Maintenance Loop

Questions about Atmos Settings

Install Atmos Settings

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 Settings

Owned Sections

Common Pattern

Terminal Appearance and Color

Flags and Environment Variables

atmos theme Commands

Routing

Guardrails

Files

Compare with similar skills

Similar skills

More from cloudposse/atmos

Related

Questions about Atmos Settings

`atmos theme` Commands