Menu
Create and review portable Atmos CLI asciicast demos for community-facing documentation, examples, and training materials.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Component architecture: Terraform root modules, remote source provisioning, abstract components, component inheritance, versioning, mixins, catalog patterns
Atmos emulator components: local AWS/GCP/Azure/Kubernetes/Vault/OpenBao/registry emulators, components.emulator, !emulator, identities, persistence, health checks, and emulator commands
YAML functions: !terraform.state, !terraform.output, !store, !store.get, !secret, !emulator, !env, !exec, !include, !template, !append, !unset, !literal, !random, !aws.*, !git.*, !cwd, !repo-root
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations
Run one full merge-readiness pass on the current branch's PR right now: sync with origin/main, check CI, address CodeRabbit threads, lint, and test coverage — fixing what's safely fixable. Mirrors `atmos fix --all` at the CLI, plus the agent-delegated fixing atmos itself can't do. This is exactly what pr-maintenance-loop runs every hour; invoke this directly for an on-demand check without starting a recurring loop. Invoke on explicit requests like "fix all" / "check this PR" / "is this PR merge-ready".
| name | atmos-asciicast |
| description | Create and review portable Atmos CLI asciicast demos for community-facing documentation, examples, and training materials. |
Use this skill when creating or reviewing .cast recordings that demonstrate Atmos CLI usage for a broad community audience.
This is a distributed Agent Skill. Keep it portable and audience-neutral. Do not assume Cloud Posse repository paths, the Atmos documentation website, or internal development fixtures unless the project using the skill explicitly provides those conventions.
For defaults, fixture policy, authoring checklist, and boundaries, read references/atmos-asciicast-authoring.md.
