Atmos Compositions

DevOps & Security

atmos-compositions

Atmos Compositions is an Agent Skill for devops & security published in the cloudposse/atmos repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Atmos compositions: named service groupings, compositions.<name>.services, components.container[*].composition, composition validate, and service contract checks

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/cloudposse/atmos/blob/HEAD/agent-skills/skills/atmos-compositions/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/atmos-compositions, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Atmos Compositions

Use this skill for compositions: named groupings of component instances that form a system. Compositions define the service contract; components fulfill services by referencing the composition.

Related Skills

Need	Load
Container components that fulfill services	atmos-container
Stack manifest structure	atmos-stacks
Workflow orchestration across services	atmos-workflows

Configuration

Declare composition service contracts at stack scope:

compositions:
  app:
    description: Application runtime
    services:
      - api
      - worker
      - db

components:
  container:
    api:
      composition: app
    worker:
      composition: app

The composition describes expected services. Components declare which composition they fulfill.

Validation

Use atmos composition validate to inspect whether a stack provides all services for a composition.

atmos composition validate app -s plat-ue2-dev

Validation reports fulfilled and not-provided services. Use this before running workflows that assume a complete multi-service system.

Guidance

Use compositions for systems made of multiple stack-scoped services.
Keep service names stable and human-readable.
Do not use composition names as a replacement for Atmos profiles or ATMOS_PROFILE.
Put shared composition definitions in stack mixins/defaults when multiple stacks use the same service contract.
Prefer composition validation over hand-written checks in shell steps.