opentofu — Claude Code skill for OpenTofu and Pulumi
Get help writing and reviewing OpenTofu configurations and Pulumi programs. Use the skill to manage infrastructure code, state, and environment setups.
MIT 153 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill opentofu -a claude-codeWhat opentofu does
This skill covers OpenTofu with HCL and Pulumi with TypeScript or Python. It addresses providers, resources, modules, remote backends, and infrastructure state. OpenTofu topics include state encryption; Pulumi topics include stacks, secrets, and the Automation API.
Use it to plan infrastructure changes, bring existing resources under OpenTofu management, or organise configuration across environments. The guidance calls out pitfalls such as keeping team state locally and applying changes before reviewing a plan. Run tofu plan before applying: otherwise, infrastructure changes can go through without a prior review.
What it helps with
- write OpenTofu infrastructure configuration in HCL
- bring an existing resource under OpenTofu management
- set up remote state storage with locking
- separate infrastructure configuration by environment
- build a Pulumi program in TypeScript or Python
Example prompts for the agent
- Review this OpenTofu configuration and show what
tofu planwould change. - Explain how to import this existing resource into OpenTofu and update its state.
- Create a Pulumi TypeScript program with separate settings for each environment.
How to install opentofu
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill opentofu -a claude-code2Manually: put the files in place
~/.claude/skills/opentofu/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/opentofu/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill opentofu -a codex2Manually: put the files in place
.agents/skills/opentofu/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill opentofu -a cursor2Manually: put the files in place
.cursor/skills/opentofu/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/opentofu2Manually: put the files in place
.github/skills/opentofu/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill opentofu -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/opentofuManually: put the files in place
.devin/skills/opentofu/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill opentofu -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about opentofu
How do I install opentofu in Claude Code?
Run npx skills add oakoss/agent-skills --skill opentofu -a claude-code. The skill file is at ~/.claude/skills/opentofu/SKILL.md.
What does the opentofu skill do?
It guides infrastructure-as-code work with OpenTofu and Pulumi, including configuration, modules, state, secrets, and environment setups.
Can opentofu help with OpenTofu state encryption?
Yes. It covers the terraform.encryption block for state encryption, a feature specific to OpenTofu.
Source text
SKILL.md · MIT
---
name: opentofu
description: |
Infrastructure as code with OpenTofu (open-source Terraform fork) and Pulumi. Covers OpenTofu HCL syntax, providers, resources, data sources, modules, state management with remote backends, workspaces, importing existing infrastructure, plan/apply workflow, variable management, output values, provisioners, and state encryption (OpenTofu-exclusive). Includes Pulumi TypeScript/Python SDKs, stack management, component resources, config/secrets, state backends, policy as code, and automation API. Common patterns for multi-environment setups, module composition, CI/CD integration, drift detection, and secret management.
Use when writing or reviewing HCL configurations, managing cloud infrastructure state, migrating from Terraform to OpenTofu, building Pulumi programs in TypeScript or Python, setting up multi-environment IaC pipelines, or implementing state encryption.
license: MIT
metadata:
author: oakoss
version: '1.0'
source: 'https://opentofu.org/docs'
user-invocable: false
---
# OpenTofu
## Overview
OpenTofu is an open-source infrastructure as code tool that uses HCL (HashiCorp Configuration Language) to declaratively manage cloud infrastructure. It is a community-driven fork of Terraform, fully compatible with existing Terraform providers and modules, with exclusive features like native state encryption. Pulumi provides an alternative IaC approach using general-purpose languages (TypeScript, Python, Go) instead of HCL.
**When to use:** Managing cloud infrastructure declaratively, provisioning multi-cloud resources, enforcing infrastructure consistency across environments, encrypting state at rest (OpenTofu), using familiar programming languages for IaC (Pulumi).
**When NOT to use:** One-off scripts better suited to CLI tools, application-level configuration management (use Ansible/Chef), container orchestration logic (use Kubernetes manifests), simple static hosting (use platform-native tools).
## Quick Reference
| Pattern | Tool / Command | Key Points |
| ------------------ | -------------------------------------- | ---------------------------------------------- |
| Initialize project | `tofu init` | Downloads providers, initializes backend |
| Preview changes | `tofu plan` | Shows diff without applying |
| Apply changes | `tofu apply` | Provisions/updates resources |
| Destroy resources | `tofu destroy` | Tears down managed infrastructure |
| Import resource | `tofu import <addr> <id>` | Brings existing resource under management |
| State encryption | `terraform.encryption` block | OpenTofu-exclusive, AES-GCM with key providers |
| Remote backend | `backend "s3"` / `backend "gcs"` | Store state in cloud storage with locking |
| Workspaces | `tofu workspace new <name>` | Isolated state per environment |
| Module usage | `module "name" { source = "..." }` | Reusable infrastructure components |
| Output values | `output "name" { value = ... }` | Expose values for other configs or CI |
| Variable files | `terraform.tfvars` / `-var-file` | Environment-specific variable overrides |
| Pulumi new project | `pulumi new typescript` | Scaffold TypeScript IaC project |
| Pulumi preview | `pulumi preview` | Shows planned changes |
| Pulumi deploy | `pulumi up` | Provisions/updates resources |
| Pulumi config | `pulumi config set key value` | Stack-scoped configuration |
| Pulumi secrets | `pulumi config set --secret key val` | Encrypted config values |
| Pulumi stacks | `pulumi stack select <name>` | Switch between environments |
| Automation API | `LocalWorkspace.createOrSelectStack()` | Programmatic stack management |
## Common Mistakes
| Mistake | Correct Pattern |
| ---------------------------------------------------- | ----------------------------------------------------------------- |
| Storing state locally in team environments | Configure remote backend (S3, GCS, Azure Blob) with state locking |
| Hardcoding provider credentials in HCL | Use environment variables or provider-specific auth chains |
| Using `tofu apply` without reviewing plan | Run `tofu plan -out=plan.tfplan` then `tofu apply plan.tfplan` |
| Editing state manually | Use `tofu state mv`, `tofu state rm`, or `tofu import` |
| Ignoring `.terraform.lock.hcl` | Commit lock file for reproducible provider versions |
| Using `count` for complex conditional resources | Prefer `for_each` with maps for stable resource addressing |
| Sharing one workspace for all environments | Use separate workspaces or backend config per environment |
| Putting secrets in `terraform.tfvars` | Use `sensitive = true` variables, vault, or environment variables |
| Pulumi: creating resources outside component classes | Wrap related resources in ComponentResource for reuse |
| Pulumi: not awaiting async operations | Ensure all resource operations complete before stack export |
| Skipping `tofu plan` in CI/CD | Always plan and require approval before apply in pipelines |
| Not using `-target` carefully | Prefer full plans; `-target` can leave state inconsistent |
## Delegation
- **Infrastructure pattern discovery**: Use `Explore` agent
- **IaC code review**: Use `Task` agent
- **Drift detection analysis**: Use `Task` agent
> If the `amazon-web-services` skill is available, delegate AWS resource patterns to it.
> If the `docker` skill is available, delegate container infrastructure patterns to it.
> If the `github-actions` skill is available, delegate CI/CD pipeline patterns to it.
## References
- [HCL syntax, resources, data sources, and providers](references/hcl-fundamentals.md)
- [Modules, composition, and reusable infrastructure](references/modules.md)
- [State management, remote backends, and locking](references/state-management.md)
- [State encryption with OpenTofu-exclusive key providers](references/state-encryption.md)
- [Variables, outputs, and environment configuration](references/variables-outputs.md)
- [Workspaces and multi-environment setups](references/workspaces.md)
- [Import existing infrastructure and migration patterns](references/import-migration.md)
- [Pulumi TypeScript and Python SDK patterns](references/pulumi-sdk.md)
- [Pulumi stacks, config, secrets, and automation API](references/pulumi-stacks.md)
- [CI/CD integration and drift detection](references/cicd-integration.md)
© oakoss · MIT · oakoss/agent-skills