Terraform Engineer
Terraform infrastructure as code across AWS, Azure, or GCP. Use for module development, state management, provider configuration, multi-environment workflows, infrastructure testing.
Install
$ agentstack add skill-yassimba-loom-terraform-engineer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yassimba-loom-terraform-engineer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Terraform Engineer
Core Workflow
- Analyze infrastructure - Review requirements, existing code, cloud platforms
- Design modules - Create composable, validated modules with clear interfaces
- Implement state - Configure remote backends with locking and encryption
- Secure infrastructure - Apply security policies, least privilege, encryption
- Test and validate - Run terraform plan, policy checks, automated tests
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When | | -------------- | -------------------------------- | ------------------------------------------------ | | Modules | references/module-patterns.md | Creating modules, inputs/outputs, versioning | | State | references/state-management.md | Remote backends, locking, workspaces, migrations | | Providers | references/providers.md | AWS/Azure/GCP configuration, authentication | | Testing | references/testing.md | terraform plan, terratest, policy as code | | Best Practices | references/best-practices.md | DRY patterns, naming, security, cost tracking |
Constraints
- Use semantic versioning for modules
- Enable remote state with locking
- Validate inputs with validation blocks
- Use consistent naming conventions
- Tag all resources for cost tracking
- Document module interfaces
- Pin provider versions
- Run terraform fmt and validate
- Reference secrets via sensitive variables or a secrets manager
- Parameterize environment-specific values through tfvars
- Keep module dependency graphs acyclic
- Add
.terraform/to .gitignore
Output Templates
When implementing Terraform solutions, provide:
- Module structure (main.tf, variables.tf, outputs.tf)
- Backend configuration for state
- Provider configuration with versions
- Example usage with tfvars
- Brief explanation of design decisions
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yassimba
- Source: Yassimba/loom
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.