Agent skill

Atmos Imports

by cloudposse in cloudposse/atmos

Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Imports

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

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

GitHub CLI
$ gh skill install cloudposse/atmos atmos-imports --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-imports .claude/skills/atmos-imports && 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-imports
GitHub stars
1.4k
Token cost
~923 tokens
SKILL.md length
310 words
Files
1
Skills in repo
70
Repo updated
First seen
Licence
Apache-2.0

At a glance

Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts

  • DevOps & Cloud work in your project
  • SKILL.md covers Related Skills, Import Basics, Remote Imports and Import vs Source vs Vendoring, plus 2 more sections
  • Reaches raw.githubusercontent.com and github.com

What it does

Atmos Imports is an agent skill from cloudposse/atmos. Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts

Its SKILL.md is about 920 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. It works with GitHub. 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-imports skill to atmo imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs…”
  • “/atmos-imports”

What it can do on your machine

Read from SKILL.md and the folder at commit 110e139. 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:

    • raw.githubusercontent.com
    • github.com
    • s3.amazonaws.com

    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 Imports loads about 923 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 310 words of instructions outside code blocks.

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

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 110e139, republished under its Apache-2.0 licence (© cloudposse). 310 words, ~923 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-imports/SKILL.md (or your agent's skills folder).
name
atmos-imports
description
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
core-config

Atmos Imports

Use this skill for stack manifest import: behavior, especially remote imports. Imports pull stack configuration, not component source code.

NeedLoad
General stack structure and merge precedenceatmos-stacks
Component source provisioning and vendoringatmos-vendoring
Private GitHub auth with Atmos Pro STSatmos-auth
Migration from old import/name patternsatmos-modernization

Import Basics

yaml
import:
  - catalog/vpc/defaults
  - mixins/region/us-east-2
  - orgs/acme/plat/prod/_defaults

Atmos resolves imports before producing the final stack. Use imports for _defaults.yaml, mixins, catalog defaults, reusable stack fragments, and remote stack configuration.

If both file.yaml and file.yaml.tmpl exist, the template version is preferred. Template imports can receive context and render before merge.

Remote Imports

Remote imports use the same stack import: key:

yaml
import:
  - https://raw.githubusercontent.com/acme/config/main/stacks/catalog/vpc.yaml
  - github://acme/config/main/stacks/catalog/eks.yaml
  - git::https://github.com/acme/config.git//stacks/catalog/db.yaml?ref=v1.2.3
  - s3::https://s3.amazonaws.com/acme-configs/stacks/catalog/vpc.yaml
  - gcs::gs://acme-configs/stacks/catalog/eks.yaml
  - oci://ghcr.io/acme/atmos-config:v1.2.3

Use pinned refs or immutable artifact tags for production imports. Prefer HTTPS/GitHub forms for read-only public config and Git/OCI forms when versioning, auth, or packaged artifacts matter.

Import vs Source vs Vendoring

  • import: pulls stack YAML configuration.
  • Component source: provisions component source code.
  • vendor.yaml plus atmos vendor pull materializes external files into the repository.

Remote imports do not create components/terraform/<name> directories. If a remote imported stack references a component whose source is not local, also configure component source: or vendor the component with atmos vendor pull.

Use atmos vendor pull to cache important remote imports/components locally for offline access, repeatability, and faster CI.

Private GitHub Imports

For private GitHub remote imports in CI, prefer Atmos Pro github/sts:

yaml
auth:
  providers:
    atmos-pro:
      kind: atmos/pro
      spec:
        workspace_id: !env ATMOS_PRO_WORKSPACE_ID
  identities:
    atmos-pro:
      kind: atmos/pro
      via:
        provider: atmos-pro
  integrations:
    github-sts:
      kind: github/sts
      via:
        provider: atmos-pro
      spec:
        auto_provision: true

In CI, github/sts can lazily mint GitHub tokens before the first private remote read, including atmos vendor pull, component source:, remote import:, and private Terraform module fetches.

Debugging

  • Use atmos describe stacks --stack <stack> to verify imported and merged output.
  • Use atmos validate stacks before relying on generated stack names or inherited component config.
  • If a remote import works but Terraform cannot find a component, check component source/vendoring.
  • If a private import fails in CI, check id-token: write, atmos/pro, github/sts, and repository trust policy in Atmos Pro.

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

Open the folder on GitHubat commit 110e139

Compare with similar skills

Atmos Imports 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 Imports compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Imports this skillcloudposse/atmos1.4k—~923Automated safety check: PassApache-2.0
Azure Pipelines Log Downloaderansible/ansible71k—~825Automated safety check: PassGPL-3.0
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Make GitHub Actions Workflowdotnet/efcore15k—~2.1kAutomated safety check: PassMIT
Backport PRrundeck/rundeck6.3k—~3kAutomated safety check: PassApache-2.0
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT

Similar skills

  • Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.

    71k GitHub stars~825 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Official

    Create GitHub Actions workflows for CI, automation, or PR management.

    15k GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Backport PR

    rundeck/rundeck

    Backport commits from an existing GitHub Pull Request to a target branch and open a new backport PR.

    6.3k GitHub stars~3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Megatron-LM CI/CD Guide

    NVIDIA/Megatron-LM

    Official

    Explains Megatron-LM's CI pipeline, PR scope labels, triggering the internal GitLab CI with a dry run first, and investigating CI failures.

    18k GitHub stars~1.8k tokensUpdated today
    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 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 Imports

What does Atmos Imports do?

Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts. Atmos Imports is an agent skill from cloudposse/atmos.

When should I use Atmos Imports?

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

How do I install Atmos Imports in Claude Code?

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

How do I install Atmos Imports in Codex?

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

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

What does Atmos Imports need to run?

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

Does Atmos Imports access the network?

SKILL.md names 3 domains. In commands or code: raw.githubusercontent.com, github.com and s3.amazonaws.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

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

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

About 923 tokens (SKILL.md is roughly 3.7k 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 Imports?

Skills that share tags, products or a category with Atmos Imports: Azure Pipelines Log Downloader (ansible/ansible, 71k stars), Nushell (ccusage/ccusage, 19k stars), Make GitHub Actions Workflow (dotnet/efcore, 15k stars) and Backport PR (rundeck/rundeck, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Imports?

cloudposse (a GitHub organization) maintains it in cloudposse/atmos, which has 1,398 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 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.