Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions…
Install Atmos Container
$ npx skills add cloudposse/atmos --skill atmos-container -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cloudposse/atmos atmos-container --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/skills/atmos-container .claude/skills/atmos-container && rm -rf skills-srcUse ~/.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/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .claude/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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 install https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-containerType 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.
$ npx skills add cloudposse/atmos --skill atmos-container -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cloudposse/atmos atmos-container --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agent-skills/skills/atmos-container .agents/skills/atmos-container && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .agents/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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.
$ npx skills add cloudposse/atmos --skill atmos-container -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cloudposse/atmos atmos-container --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agent-skills/skills/atmos-container .cursor/skills/atmos-container && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .cursor/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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 https://github.com/cloudposse/atmos.git --path agent-skills/skills/atmos-container--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cloudposse/atmos --skill atmos-container -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cloudposse/atmos atmos-container --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agent-skills/skills/atmos-container .gemini/skills/atmos-container && rm -rf skills-srcUse ~/.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/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .gemini/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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.
$ gh skill install cloudposse/atmos atmos-containerInstalls 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).
$ npx skills add cloudposse/atmos --skill atmos-container -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .github/skills && cp -r skills-src/agent-skills/skills/atmos-container .github/skills/atmos-container && rm -rf skills-srcUse ~/.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/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .github/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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.
$ npx skills add cloudposse/atmos --skill atmos-container -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cloudposse/atmos atmos-container --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agent-skills/skills/atmos-container .opencode/skills/atmos-container && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "atmos-container" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-container into .opencode/skills/atmos-container/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-container", 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-container- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 538 words
- Files
- 1
- Skills in repo
- 70
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions…
- Works in 6 steps: Inventory Compose services and split… → Move shared .env values into stack vars,… → Use composition: so former Compose… → …
- Tasks that involve Containers
- SKILL.md covers Related Skills, Component Shape, Commands and Workflow Steps, plus 2 more sections
- Calls docker
What it does
Atmos Container is an agent skill from cloudposse/atmos. Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions, and hooks
Its SKILL.md is about 1.3k 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 Containers. It works with Docker. 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 Containers
Example prompts
- “Use the atmos-container skill to atmo container components: components.container, Docker Compose migration…”
- “/atmos-container”
Requirements
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Inventory Compose services and split long-lived services into separate container components.
- Move shared .env values into stack vars, component env, declared secrets, or !secret
- Use composition: so former Compose services validate and run as one system.
- Replace docker compose up/down/logs/exec/ps with the matching atmos container commands.
- Use workflow container, wait, wait-all, and explicit dependencies for startup order
- Prefer first-class components.container for Atmos-managed services. Keep a native Compose
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:
docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
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 Container loads about 1.3k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 538 words of instructions outside code blocks.
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:102
2. Move shared `.env` values into stack vars, component env, declared secrets, or `!secret`
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). 538 words, ~1,345 tokens.
Download SKILL.mdSave it as
.claude/skills/atmos-container/SKILL.md (or your agent's skills folder).- name
- atmos-container
- description
- Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions, and hooks
- metadata.copyright
- Copyright Cloud Posse, LLC 2026
- metadata.version
- 1.0.0
- metadata.category
- orchestrators
Atmos Container Components
Use this skill for first-class Atmos containers. A container component is a stack-scoped service: one component maps to one container, with image build/push/pull and optional persistent runtime.
Related Skills
| Need | Load |
|---|---|
| Grouping services into systems | atmos-compositions |
Workflow container steps | atmos-workflows |
| Lifecycle hooks around components | atmos-hooks |
| Local cloud/API emulators | atmos-emulator |
| Secret and env migration | atmos-secrets |
Component Shape
Define containers under components.container in stack manifests.
components:
container:
api:
image: ghcr.io/acme/api:latest
build:
context: services/api
dockerfile: Dockerfile
tags:
- ghcr.io/acme/api:latest
run:
ports:
- host: 8080
container: 8080
command: ./api
env:
LOG_LEVEL: info
composition: appContainer components can participate in hooks, compositions, workflows, and stack-specific config the same way other Atmos component types do.
Relative build.context, build.dockerfile, and run.mounts[].source resolve against the
component's own directory — components.container.base_path (default components/container) joined
with component:/metadata.component, the same mechanism Terraform/Helmfile/Kubernetes/Helm use —
not the directory atmos is invoked from. A component declaring source: is auto-provisioned into a
workdir (same JIT support as other component types), and that workdir becomes the anchor instead.
Commands
| Command | Purpose |
|---|---|
atmos container build <name> -s <stack> | Build the component image |
atmos container push <name> -s <stack> | Push the image to its registry |
atmos container pull <name> -s <stack> | Pull the image |
atmos container run <name> -s <stack> | Run one foreground container |
atmos container up <name> -s <stack> | Create/start the persistent container |
atmos container down <name> -s <stack> | Stop and remove the persistent container |
atmos container ps -s <stack> | Show running state |
atmos container list -s <stack> | List container components and state |
atmos container logs <name> -s <stack> | Show logs |
atmos container exec <name> -s <stack> -- <cmd> | Execute inside the container |
atmos container also supports attach, restart, start, stop, and rm. Use --dry-run to
preview operations.
Workflow Steps
Use the workflow container step type when a workflow should build, run, push, or operate a
container as part of orchestration. Use components.container when the container is a reusable
stack-scoped component with persistent lifecycle.
Show full SKILL.md (247 more words)Show less
Migrating from Docker Compose
When replacing docker compose with Atmos containers, translate one Compose service at a time
into components.container.<service>. Keep multi-service grouping with composition, not by
collapsing several services into one container component.
| Docker Compose field | Atmos container mapping |
|---|---|
services.<name>.image | components.container.<name>.image |
build.context, build.dockerfile | build.context, build.dockerfile |
ports | run.ports |
environment, env_file | env, stack vars, or secrets.vars with !secret |
command, entrypoint | run.command or the supported runtime command fields |
volumes | runtime mount settings supported by the container component |
depends_on | workflow/composition ordering, readiness checks, wait, or wait-all |
| Compose project name | shared composition: <name> across related container components |
Migration process:
- Inventory Compose services and split long-lived services into separate container components.
- Move shared
.envvalues into stack vars, component env, declared secrets, or!secretreferences. - Use
composition: <name>so former Compose services validate and run as one system. - Replace
docker compose up/down/logs/exec/pswith the matchingatmos containercommands. - Use workflow
container,wait,wait-all, and explicit dependencies for startup order instead of Compose-onlydepends_onassumptions. - Prefer first-class
components.containerfor Atmos-managed services. Keep a native Compose file only when the project must remain compatible with external Compose tooling.
Operational Guidance
- Use stack names to isolate container instances.
- Prefer declared
image,build,run, andenvblocks over ad hoc shelldockercommands. - Use
compositionwhen a container fulfills a named service in a system. - Use hooks for pre/post actions such as scans, artifact publication, or store writes.
- Use registry auth skills such as
atmos-aws-ecrwhen pushing to private registries.
© 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
Just SKILL.md in agent-skills/skills/atmos-container of cloudposse/atmos.
Open the folder on GitHubat commit 36726ae
Compare with similar skills
Atmos Container 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Atmos Container this skillcloudposse/atmos | 1.4k | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 15k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
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…
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
Omnigent Docker Compose Deploy
omnigent-ai/omnigent
Brings up the Omnigent server and Postgres as a Docker compose stack on any Docker host, and covers the Dockerfile's runtime and host build targets for extending it to a new platform.
More from cloudposse/atmos
All 70 skills in this repoFix 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…
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.
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.
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…
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…
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…
Related
Works with
Categories
Questions about Atmos Container
What does Atmos Container do?
Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions…. Atmos Container is an agent skill from cloudposse/atmos.
When should I use Atmos Container?
Atmos Container fits situations like: tasks that involve Containers.
How do I install Atmos Container in Claude Code?
Run `npx skills add cloudposse/atmos --skill atmos-container -a claude-code`. Or copy the skill folder (agent-skills/skills/atmos-container in cloudposse/atmos) into .claude/skills/atmos-container in your project. Claude Code loads it when a task matches its description.
How do I install Atmos Container in Codex?
Run `npx skills add cloudposse/atmos --skill atmos-container -a codex`. Or copy the skill folder (agent-skills/skills/atmos-container in cloudposse/atmos) into .agents/skills/atmos-container in your project. Codex loads it when a task matches its description.
Can I use Atmos Container 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-container -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-container, .gemini/skills/atmos-container, .github/skills/atmos-container and .opencode/skills/atmos-container in your project.
What does Atmos Container need to run?
Going by SKILL.md and its folder, Atmos Container needs the command-line tools its instructions call (docker). Our summary lists: Docker.
Does Atmos Container access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Atmos Container 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 Container use?
Atmos Container 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 Container use?
About 1.3k tokens (SKILL.md is roughly 5.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 Container?
Skills that share tags, products or a category with Atmos Container: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Atmos Container?
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.