gracefullight/pkgs / .agents/skills/oma-tf-infra
oma-tf-infra
VerifiedCreate or review Terraform infrastructure and plans. Use for cloud resources, IAM, networking, state management, and infrastructure changes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| resources/checklist.md | markdown | 2.3 KB |
| resources/cost-optimization.md | markdown | 13.2 KB |
| resources/error-playbook.md | markdown | 2.8 KB |
| resources/examples.md | markdown | 1.5 KB |
| resources/execution-protocol.md | markdown | 6.1 KB |
| resources/iso-42001-infra.md | markdown | 6.8 KB |
| resources/multi-cloud-examples.md | markdown | 6.4 KB |
| resources/policy-testing-examples.md | markdown | 6.8 KB |
resources/checklist.md
View on GitHub# TF Infra Agent: Self-Verification Checklist
## Configuration
- [ ] `terraform validate` passes without errors
- [ ] `terraform fmt` applied (consistent formatting)
- [ ] Provider and module versions pinned in `versions.tf`
- [ ] Remote backend configured with state locking and encryption
## Security
- [ ] No secrets, passwords, or API keys in .tf files
- [ ] Secret values do not persist in state where avoidable: ephemeral resources (TF >= 1.10) / write-only `*_wo` arguments (TF >= 1.11); state treated as sensitive either way
- [ ] `terraform.tfvars` excluded from git
- [ ] IAM policies follow least privilege
- [ ] OIDC/workload identity used for CI/CD (no long-lived credentials)
- [ ] Sensitive outputs marked with `sensitive = true`
- [ ] Encryption at rest enabled for storage and databases
- [ ] Network boundaries defined (security groups, firewall rules)
## Naming & Tags
- [ ] Consistent naming convention using `locals` block
- [ ] All taggable resources include: Environment, Project, Owner, CostCenter
- [ ] Resource names match project patterns
## Resource Design
- [ ] `for_each` used over `count` for resource collections
- [ ] `count` not used with computed values that could cause recreation
- [ ] `depends_on` set for explicit ordering where needed
- [ ] Modules are composable with clear interfaces
- [ ] No monolithic modules doing too many things
- [ ] Environment-based sizing (smaller for dev/staging)
## Operations Safety
- [ ] No `auto-approve` in production environments
- [ ] No `terraform destroy` without explicit backup/confirmation
- [ ] Drift detection not skipped in production
- [ ] Provider deprecation warnings addressed
- [ ] State files not stored locally in team environments
## Cost
- [ ] Cost impact reviewed via `terraform plan`
- [ ] Storage lifecycle rules configured
- [ ] Autoscaling schedules set for off-hours scaling
- [ ] Reserved Instances / Savings Plans considered for production
## Policy & Testing
- [ ] Policy checks (OPA/Sentinel) pass
- [ ] Security scanning (Checkov/Trivy) clean
- [ ] Critical modules have `terraform test` or integration tests
## Compliance (when applicable)
- [ ] AI systems: IAM, logging, encryption, monitoring, retention controls documented
- [ ] Continuity: RTO/RPO, failover, backup, restore assumptions documented
- [ ] Architecture: stakeholders, concerns, views, rationale captured
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |