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/examples.md
View on GitHub# TF Infra Agent: Examples
## Example 1: GCP Cloud Run Service with Cloud SQL
**Input:** "Deploy an API service on Cloud Run and connect it to Cloud SQL PostgreSQL"
**Output:**
- Files created: `compute.tf`, `database.tf`, `networking.tf`, `iam.tf`, `outputs.tf`
- Cloud provider: GCP (detected from existing `provider "google"`)
- Resources: Cloud Run service, Cloud SQL PostgreSQL, VPC connector, service account
- Key decisions:
- VPC connector for private Cloud SQL access
- Dedicated service account with minimal permissions
- Cloud SQL Auth Proxy sidecar for secure connection
- Environment-based sizing: `db-f1-micro` (dev) vs `db-custom-4-16384` (prod)
## Example 2: AWS ECS Fargate with GitHub OIDC
**Input:** "Set up OIDC so GitHub Actions can deploy to ECS Fargate"
**Output:**
- Files created: `cicd-auth.tf`, `iam.tf`
- Cloud provider: AWS (detected from existing `aws_*` resources)
- Resources: OIDC provider, IAM role with trust policy, ECR/ECS permissions
- Key decisions:
- Trust policy scoped to specific repo and branch
- Permissions limited to ECR push + ECS task update only
- No long-lived access keys
## Example 3: Terraform Plan Review
**Input:** "Review this terraform plan output"
**Output:**
- Summary: 3 to add, 1 to change, 1 to destroy
- Risk: HIGH; `aws_db_instance` will be destroyed and recreated (engine version change)
- Recommendation: Use `lifecycle { prevent_destroy = true }` or manual migration
- Checklist: backup verified, maintenance window set, rollback plan documented
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 |