菜单
AWS compliance commands in Atmos: atmos aws compliance report, Security Hub standards, CIS AWS, PCI DSS, SOC2, HIPAA, NIST, report formats, AI summaries
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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-aws-compliance |
| description | AWS compliance commands in Atmos: atmos aws compliance report, Security Hub standards, CIS AWS, PCI DSS, SOC2, HIPAA, NIST, report formats, AI summaries |
| metadata | {"copyright":"Copyright Cloud Posse, LLC 2026","version":"1.0.0"} |
Use this skill for compliance posture reporting through AWS Security Hub. It owns
atmos aws compliance report.
atmos aws compliance report retrieves enabled Security Hub standard controls, maps failing
controls to Atmos stacks/components where possible, and writes reports for humans or automation.
atmos aws compliance report --framework cis-aws --stack prod-us-east-1
atmos aws compliance report --framework pci-dss --format json --file compliance.json
atmos aws compliance report --controls CIS.1.1,CIS.1.2 --format markdown
atmos aws compliance report --ai
Supported report formats are markdown, json, yaml, and csv.
Configure defaults in atmos.yaml under aws.security. Route identity setup to atmos-auth.
aws:
security:
enabled: true
identity: security-readonly
region: us-east-2
frameworks:
- cis-aws
- pci-dss
Use --identity to override the configured identity for a run.
| Framework | Use |
|---|---|
cis-aws | CIS AWS Foundations Benchmark |
pci-dss | Payment Card Industry Data Security Standard |
soc2 | SOC 2 trust service criteria |
hipaa | HIPAA controls for protected health information |
nist | NIST 800-53 controls |
--framework for targeted checks. Omit it only when the user explicitly wants all enabled
frameworks.--stack when the report should map compliance status to a specific Atmos stack.--format json or --format yaml for automation and CI gates; use markdown for human
reports.--file for durable artifacts. Parent directories are created by the command.--ai only when the user asks for AI-generated summary or remediation guidance.atmos-aws-security.| Need | Skill |
|---|---|
| Detailed security finding analysis and remediation format | atmos-aws-security |
| AWS identity/provider setup, SSO, SAML, OIDC, assume role/root | atmos-auth |
AI provider setup for --ai summaries | atmos-ai |
| Stack/component lookup before remediation | atmos-introspection, atmos-components |