Agent skill

Atmos Pro

by cloudposse in cloudposse/atmos

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Pro

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

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

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

At a glance

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection

  • Tasks that involve GitOps
  • SKILL.md covers Related Skills, Minimal Setup, Core Commands and Workflow Dispatch, plus 3 more sections
  • Needs GITHUB_TOKEN
  • Tasks that involve OAuth and OpenID Connect

What it does

Atmos Pro is an agent skill from cloudposse/atmos. Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection

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 GitOps and OAuth and OpenID Connect. It works with GitHub, GitHub Actions and Git. 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 GitOps
  • Tasks that involve OAuth and OpenID Connect

Example prompts

  • “Use the atmos-pro skill to atmo Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit…”
  • “/atmos-pro”

Requirements

  • A credential in GITHUB_TOKEN

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 these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN

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

Context cost

Atmos Pro loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 476 words of instructions outside code blocks.

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

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). 476 words, ~1,293 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-pro/SKILL.md (or your agent's skills folder).
name
atmos-pro
description
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
ci-automation

Atmos Pro

Use this skill when configuring or debugging Atmos Pro, including CI uploads, workflow dispatch, stack locking, GitHub App commits, merge queues, and drift detection.

Atmos Pro is the control plane for visibility and coordination. Atmos CLI remains the execution layer for plans, applies, deploys, auth, toolchains, and stack resolution.

NeedLoad
GitHub Actions job structure and Native CIatmos-ci
atmos/pro provider and github/sts integrationatmos-auth
Managed Git repositories and signed/pushed commitsatmos-git
Migrating old drift/action patternsatmos-modernization

Minimal Setup

Configure the workspace ID in atmos.yaml or ATMOS_PRO_WORKSPACE_ID. It is not a secret.

yaml
settings:
  pro:
    workspace_id: "your-workspace-id"

In GitHub Actions, grant OIDC permission. Do not use static API keys for normal GitHub Actions workflows.

yaml
permissions:
  id-token: write
  contents: read

Atmos Pro exchanges the GitHub Actions OIDC token for a short-lived bearer token. The OIDC request URL/token are normally supplied by GitHub automatically.

Core Commands

CommandPurpose
atmos describe affected --uploadUpload affected stacks/components for PR and merge-queue correlation
atmos list instances --uploadUpload full component instance inventory
atmos terraform plan <component> -s <stack> --upload-statusUpload raw plan status for drift detection
atmos pro lock --component <component> --stack <stack>Lock a stack/component before mutation
atmos pro unlock --component <component> --stack <stack>Release a stack/component lock
atmos pro commit -m "<message>" --allCommit CI-generated changes through the Atmos Pro GitHub App

atmos pro commit is for workflows that need committed changes to trigger follow-on CI. Commits created with GITHUB_TOKEN do not trigger subsequent GitHub Actions workflows; commits created by the Atmos Pro GitHub App do.

Workflow Dispatch

Atmos Pro reads settings.pro from uploaded stack/component payloads and dispatches GitHub workflows server-side for matching repository events.

yaml
settings:
  pro:
    enabled: true
    pull_request:
      synchronize:
        workflows:
          atmos-terraform-plan.yaml:
            inputs:
              component: "{{ .atmos_component }}"
              stack: "{{ .atmos_stack }}"
      merged:
        workflows:
          atmos-terraform-apply.yaml:
            inputs:
              component: "{{ .atmos_component }}"
              stack: "{{ .atmos_stack }}"
    merge_group:
      checks_requested:
        workflows:
          atmos-terraform-plan.yaml:
            inputs:
              component: "{{ .atmos_component }}"
              stack: "{{ .atmos_stack }}"

Use pull_request.synchronize for plan-on-change. Use pull_request.merged for the conventional apply workflow. Configure merge_group.checks_requested explicitly for GitHub merge queues rather than relying on fallback inference.

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

Drift Detection

Atmos Pro is the standard product path for drift detection. Do not recommend hand-rolled scheduled GitHub Actions or deprecated drift wrapper actions for new projects.

Enable drift detection per stack/component:

yaml
settings:
  pro:
    enabled: true
    drift_detection:
      enabled: true

Effective drift detection also requires the instance to be Pro-enabled. metadata.enabled: false or settings.pro.enabled: false disables drift dispatch regardless of settings.pro.drift_detection.enabled.

Upload plan status from the workflow that Atmos Pro dispatches:

bash
atmos terraform plan vpc -s prod-use1 --upload-status

Atmos Pro interprets plan/apply status server-side and coordinates drift visibility and remediation.

GitHub STS

For private GitHub modules, vendoring, component source, or remote import, configure the atmos/pro auth provider and github/sts integration in the atmos-auth skill. This lets Atmos Pro mint short-lived GitHub App installation tokens in CI without storing long-lived tokens.

Troubleshooting

  • If uploads fail authentication, verify id-token: write, settings.pro.workspace_id or ATMOS_PRO_WORKSPACE_ID, and that the Atmos Pro GitHub App is installed.
  • If uploads return 403, verify the repository is imported into the Atmos Pro workspace.
  • If merge queue checks do not resolve, verify merge_group.checks_requested and that atmos describe affected --upload runs on merge_group events.
  • If drift is not dispatched, verify settings.pro.enabled, settings.pro.drift_detection.enabled, and that the instance appears in atmos list instances --upload.

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

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos Pro 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 Pro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Pro this skillcloudposse/atmos1.4k—~1.3kAutomated safety check: PassApache-2.0
GitHub Actions Docsdevantler-tech/ksail1652 repos~1.3kAutomated safety check: PassCustom licence
GitHub Actions Genlaolaoshiren/claude-code-skills-zh878—~1.1kAutomated safety check: NotesMIT
Releasing Reactivepropertyrunceel/ReactiveProperty944—~2.7kAutomated safety check: PassMIT
Authoring GitHub Workflowsdotnet/skills5.6k1 repos~2.3kAutomated safety check: PassMIT
OpenWork Release Processdifferent-ai/openwork24k—~2.3kAutomated safety check: PassCustom licence

Similar skills

  • GitHub Actions Docs

    devantler-tech/ksail

    A skill your agent uses when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows…

    165 GitHub starsUsed in 2 repos~1.3k tokens
    DevOps & CloudAuto-check passed
  • GitHub Actions Gen

    laolaoshiren/claude-code-skills-zh

    分析真实项目并生成或修订安全、可验证的 GitHub Actions workflow;当用户要求创建 CI、测试矩阵、构建、Release、部署、缓存、Secrets、OIDC、PR 自动化或排查 workflow 配置时使用

    878 GitHub stars~1.1k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • Releasing Reactiveproperty

    runceel/ReactiveProperty

    Release the ReactiveProperty NuGet package set from this repository.

    944 GitHub stars~2.7k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Official

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.

    5.6k GitHub starsUsed in 1 repo~2.3k tokens
    DevOps & CloudAuto-check passed
  • OpenWork Release Process

    different-ai/openwork

    Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.

    24k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • CI CD

    babarot/gh-infra

    CI/CD integration patterns for gh-infra: auto-apply on merge, scheduled drift detection, self-managed vs central-management layouts, and authentication setup for GitHub Actions workflows.

    136 GitHub stars~482 tokensUpdated 9 days ago
    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

Categories

Questions about Atmos Pro

What does Atmos Pro do?

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection. Atmos Pro is an agent skill from cloudposse/atmos.

When should I use Atmos Pro?

Atmos Pro fits situations like: tasks that involve GitOps; tasks that involve OAuth and OpenID Connect.

How do I install Atmos Pro in Claude Code?

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

How do I install Atmos Pro in Codex?

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

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

What does Atmos Pro need to run?

Going by SKILL.md and its folder, Atmos Pro needs credentials named GITHUB_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.

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

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

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Pro?

Skills that share tags, products or a category with Atmos Pro: GitHub Actions Docs (devantler-tech/ksail, 165 stars), GitHub Actions Gen (laolaoshiren/claude-code-skills-zh, 878 stars), Releasing Reactiveproperty (runceel/ReactiveProperty, 944 stars) and Authoring GitHub Workflows (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Pro?

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.