New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atmos Introspection

by cloudposse in cloudposse/atmos

Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic scoped CLI help

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos Introspection

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

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

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

At a glance

Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic scoped CLI help

  • Works in 6 steps: Understand the project: atmos describe… → List what exists: atmos list stacks and… → Inspect specific configs: atmos describe… → …
  • DevOps & Cloud work in your project
  • SKILL.md covers Purpose, When to Use Introspection, Describe Commands and List Commands, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atmos Introspection is an agent skill from cloudposse/atmos. Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic scoped CLI help

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

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

  • “/atmos-introspection”

Workflow steps

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

  1. Understand the project: atmos describe config to see atmos.yaml settings
  2. List what exists: atmos list stacks and atmos list components
  3. Inspect specific configs: atmos describe component -s
  4. Check dependencies: atmos describe dependents -s
  5. Trace configuration origins: Add --provenance to any describe command
  6. Validate changes: atmos describe affected to see impact of modifications

What it can do on your machine

Read from SKILL.md and the folder at commit fbae93f. 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 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 Introspection loads about 2.9k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 840 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

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 fbae93f, republished under its Apache-2.0 licence (© cloudposse). 840 words, ~2,890 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-introspection/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
atmos-introspection
description
Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic> scoped CLI help
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0
metadata.category
dev-tooling
references
references/commands-reference.md

Atmos Introspection

Purpose

Atmos provides powerful introspection commands (describe and list) for querying the stack graph, component configurations, dependencies, and change impact. AI agents operating in a terminal should use these commands to understand the user's workspace instead of guessing at configurations.

When to Use Introspection

  • Before generating configuration -- Run atmos describe component to see the current resolved config
  • To find dependencies -- Run atmos describe dependents to see what depends on a component
  • To understand project structure -- Run atmos list stacks and atmos list components
  • For CI/CD -- Run atmos describe affected or atmos list affected to detect changed stacks
  • To debug configuration -- Use --provenance to trace where values originate

Describe Commands

atmos describe component

Display the complete, fully resolved configuration for a specific component in a stack.

bash
atmos describe component vpc -s plat-ue2-prod
atmos describe component vpc -s plat-ue2-prod --format json
atmos describe component vpc -s plat-ue2-prod --provenance
atmos describe component vpc -s plat-ue2-prod -q '.vars.cidr_block'

Key flags:

  • -s, --stack (required) -- Stack name
  • -f, --format -- Output format (yaml, json). Default: yaml
  • --provenance -- Show where each configuration value originated (file:line:column)
  • -q, --query -- Filter output with yq expressions
  • --process-templates / --process-functions -- Enable/disable template and YAML function processing
  • --skip -- Skip specific YAML functions during processing

The output includes all resolved sections: vars, settings, env, backend, metadata, deps, inheritance, and remote_state_backend.

atmos describe stacks

Show fully deep-merged configuration for all stacks and their components.

bash
atmos describe stacks
atmos describe stacks -s plat-ue2-prod
atmos describe stacks --components vpc,eks
atmos describe stacks --component-types terraform
atmos describe stacks --sections vars,settings
atmos describe stacks -q '.[] | select(.vars.environment == "prod")'

Key flags:

  • -s, --stack -- Filter by specific stack
  • --components -- Filter by component names (comma-separated)
  • --component-types -- Filter by type (terraform, helmfile, packer)
  • --sections -- Output specific sections (backend, deps, env, inheritance, metadata, remote_state_backend, settings, vars)
  • --include-empty-stacks -- Include stacks with no components
atmos describe affected

Identify components and stacks affected by Git changes between two refs.

bash
atmos describe affected
atmos describe affected --ref main
atmos describe affected --sha abc123
atmos describe affected --include-dependents
atmos describe affected --format json --file affected.json

Key flags:

  • --ref -- Git reference to compare (default: refs/remotes/origin/HEAD)
  • --sha -- Git commit SHA (takes precedence over --ref)
  • --repo-path -- Path to pre-cloned target repo (fastest, avoids cloning)
  • --clone-target-ref -- Clone the target reference instead of checking out
  • --include-dependents -- Include components that depend on changed components
  • --include-settings -- Include the settings section for each affected component
  • --exclude-locked -- Exclude components marked as locked
  • --upload -- Upload results to an HTTP endpoint (for CI/CD integration)
  • --ssh-key -- Path to PEM-encoded private key for SSH cloning
  • --ssh-key-password -- Encryption password for the PEM-encoded private key
  • --process-templates -- Enable/disable Go template processing (default: true)
  • --process-functions -- Enable/disable YAML functions processing (default: true)
  • --skip -- Skip executing specific YAML functions
atmos describe dependents

List components that depend on a given component.

bash
atmos describe dependents vpc --stack plat-ue2-prod
atmos describe dependents vpc --stack plat-ue2-prod --format json

Key flags:

  • --stack (required) -- Stack name
  • -f, --format -- Output format (json, yaml). Default: json
atmos describe config

Display the final merged CLI configuration (atmos.yaml resolution result).

bash
atmos describe config
atmos describe config --format json
atmos describe config -q '.stacks.name_template'
atmos describe workflows

List all workflows and their associated files.

bash
atmos describe workflows
atmos describe workflows --format json
atmos describe workflows --output map
atmos describe locals

Display locals defined in stack manifests.

bash
atmos describe locals --stack plat-ue2-prod
atmos describe locals vpc --stack plat-ue2-prod

List Commands

atmos list stacks

List all stacks with optional component filtering.

bash
atmos list stacks
atmos list stacks --component vpc
atmos list stacks --format tree --provenance
atmos list stacks --format json

Key flags:

  • --component -- Filter stacks that contain a specific component
  • --provenance -- Show import provenance (tree format only)
  • -f, --format -- Output format (table, json, yaml, csv, tsv, tree)
atmos list components

List all unique component definitions.

bash
atmos list components
atmos list components -s 'plat-*-prod'
atmos list components --type abstract
atmos list components --enabled true
atmos list components --format tree

Key flags:

  • -s, --stack -- Filter by stack pattern (glob supported)
  • --type -- Filter by component type (real, abstract, all). Default: real
  • --abstract -- Include abstract components
  • --enabled -- Filter by enabled status (true/false)
  • --locked -- Filter by locked status (true/false)
Show full SKILL.md (343 more words)Show less
atmos list instances

List all component-stack combinations (instances).

bash
atmos list instances
atmos list instances --stack 'plat-*-prod'
atmos list instances --format json
atmos list instances --columns component,stack,type
atmos list instances --sort 'stack:asc,component:asc'

Key flags:

  • --stack -- Filter by stack pattern
  • --filter -- YQ-based filter expressions
  • --columns -- Custom column selection
  • --sort -- Sort specification (e.g., component:asc,stack:desc)
  • --upload -- Upload instances to Atmos Pro API
atmos list affected

List affected components in table format (tabular version of describe affected).

bash
atmos list affected
atmos list affected --ref main --include-dependents
atmos list affected --format csv

This is an experimental command.

atmos list workflows

List all workflows with file and description information.

bash
atmos list workflows
atmos list workflows --file deploy.yaml
Other List Commands
bash
atmos list values <component>       # Component values across stacks
atmos list vars <component>         # Component variables across stacks
atmos list settings <component>     # Component settings across stacks
atmos list sources <component>      # Component source information
atmos list vendor                   # Vendor configurations
atmos list aliases                  # Command aliases
atmos list themes                   # Available CLI themes
atmos list metadata                 # Metadata information

Common Patterns

Output Format Support
Command TypeFormats
Describe commandsyaml, json
List commandstable (default), json, yaml, csv, tsv, tree
Column Customization (List Commands)
bash
# Simple field names
atmos list instances --columns component,stack,type

# Named columns with templates
atmos list instances --columns "Component={{ .component }},Stack={{ .stack }}"
Sorting (List Commands)
bash
atmos list instances --sort component:asc
atmos list instances --sort "stack:asc,component:desc"
YQ Query Filtering

All commands support -q, --query for filtering with yq expressions:

bash
atmos describe stacks -q '.[] | select(.vars.environment == "prod")'
atmos describe component vpc -s plat-ue2-prod -q '.vars'
atmos list instances --filter '.type == "terraform"'
Provenance Tracking

Use --provenance to trace where configuration values originate:

bash
atmos describe component vpc -s plat-ue2-prod --provenance
atmos list stacks --format tree --provenance

Shows file:line:column details and import hierarchy visualization.

Template and Function Control
bash
# Disable Go template processing
atmos describe component vpc -s prod --process-templates=false

# Disable YAML functions
atmos describe stacks --process-functions=false

# Skip specific YAML functions
atmos describe component vpc -s prod --skip '!terraform.output'
Authentication for Remote Resources
bash
# Use specific identity for YAML function resolution
atmos describe component vpc -s prod -i prod-admin

# Interactive identity selection
atmos describe component vpc -s prod -i

CLI Help: --help=<topic>

Every atmos command supports a scoped --help=<topic> flag so help output doesn't bury the one thing you need. This is the fastest way for an agent to confirm correct command syntax without reading the full flag reference:

bash
atmos terraform plan --help            # Default: description, usage, examples, subcommands,
                                        # command-specific flags, and a hint for expanded help
atmos terraform plan --help=usage      # ONLY the usage line + embedded usage examples --
                                        # the fastest way to see real invocation examples
atmos terraform plan --help=flags      # Command-specific flags only, excludes inherited/global flags
atmos terraform plan --help=all        # Full reference: everything, including inherited/global flags
atmos wrapper --help=hidden            # ONLY wrapper's hidden subcommands (internal: true custom
                                        # commands, or hidden built-ins) -- omitted from every other topic

Prefer --help=usage over the default --help when you just need to confirm how a command is invoked -- it skips straight to worked examples instead of the full flag listing. Reach for --help=all only when you need the complete inherited-flag surface (e.g. global --stack/--format/logging flags shared across commands). Reach for --help=hidden when a command's default action or steps reference a subcommand name that never shows up in --help -- it is almost certainly an internal: true custom command, not a typo.

Introspection Workflow for AI Agents

When assisting a user with Atmos configuration, follow this sequence:

  1. Understand the project: atmos describe config to see atmos.yaml settings
  2. List what exists: atmos list stacks and atmos list components
  3. Inspect specific configs: atmos describe component <name> -s <stack>
  4. Check dependencies: atmos describe dependents <name> -s <stack>
  5. Trace configuration origins: Add --provenance to any describe command
  6. Validate changes: atmos describe affected to see impact of modifications

Never guess at stack names, component names, or configuration values. Always query first.

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

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

Open the folder on GitHubat commit fbae93f

Compare with similar skills

Atmos Introspection 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 Introspection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atmos Introspection this skillcloudposse/atmos1.4k—~2.9kAutomated safety check: PassApache-2.0
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw36k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT

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.

    36k 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 8 repos~4.3k tokens
    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

  • 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

  • Docs Learn PR Preview

    netdata/netdata

    Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.

    81k GitHub stars~2k 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

Categories

Questions about Atmos Introspection

What does Atmos Introspection do?

Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help=<topic scoped CLI help. Atmos Introspection is an agent skill from cloudposse/atmos.

When should I use Atmos Introspection?

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

How do I install Atmos Introspection in Claude Code?

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

How do I install Atmos Introspection in Codex?

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

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

What does Atmos Introspection need to run?

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

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

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

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

What are the alternatives to Atmos Introspection?

Skills that share tags, products or a category with Atmos Introspection: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos Introspection?

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 9, 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.