Agent skill · DevOps & Cloud

oma-tf-infra

Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.

first-flukegithub.com/first-flukeGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add first-fluke/oh-my-agent --skill oma-tf-infra --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 12 KB
Bundled scripts: none
Path: .agents/skills/oma-tf-infra/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,204
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# TF Infra Agent - Infrastructure-as-Code Specialist ## Scheduling ### Goal Design, implement, review, and document Terraform-based infrastructure across cloud providers with secure state, least privilege, cost awareness, continuity, and policy/testing controls. ### Intent signature - User asks for Terraform, IaC, cloud provisioning, state, IAM/OIDC, networking, storage, compute, databases, CDN, policy-as-code, cost optimization, drift, or terraform plan review. - User needs infrastructure controls for AI systems, continuity, or architecture documentation. ### When to use - Provisioning infrastructure on any cloud provider (AWS, GCP, Azure, OCI) - Creating or modifying Terraform configurations for compute, databases, storage, networking - Configuring CI/CD authentication (OIDC, workload identity, IAM roles) - Setting up CDN, load balancers, object storage, message queues - Reviewing terraform plan output before apply - Troubleshooting Terraform state or resource issues - Migrating from manual console changes to Terraform - Implementing infrastructure controls for AI systems (ISO/IEC 42001) - Designing continuity-oriented infrastructure (ISO 22301) - Producing architecture documenta

What's inside
Steps it walks through
  1. Scheduling
  2. Goal
  3. Intent signature
  4. When to use
  5. When NOT to use
  6. Expected inputs
  7. Expected outputs
  8. Dependencies
  9. Control-flow features
  10. Structural Flow
  11. Entry
  12. Scenes
  13. Transitions
  14. Failure and recovery
Ships with 8 files
  • resources/checklist.md
  • resources/cost-optimization.md
  • resources/error-playbook.md
  • resources/examples.md
  • resources/execution-protocol.md
  • resources/iso-42001-infra.md
  • resources/multi-cloud-examples.md
  • resources/policy-testing-examples.md
Commands it runs
terraform init            # required before validate/plan (-backend=false for static-only checks)
terraform fmt -recursive
terraform validate
terraform plan -out=tfplan
checkov -d .
trivy config .   # tfsec is in maintenance mode; Trivy is its successor
More from oh-my-agent
All skills →
About this skill
What does the oma-tf-infra skill do?

Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.

How do I install it?

Run `npx skills add first-fluke/oh-my-agent --skill oma-tf-infra --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going