terraform
Plan, apply, and manage infrastructure with Terraform. Use when tasks mention terraform commands, HCL configuration, provider setup, state management, or workspace operations.
What this skill does
# Terraform ## Intent Router | Request | Reference | Load When | | --- | --- | --- | | Install tool, first-time setup, tfenv | `resources/install-and-setup.md` | User needs to install Terraform or manage versions | | Provider config, variables, backends | `resources/configuration.md` | User needs provider blocks, variable files, or backend setup | | CLI commands, workflows | `resources/command-cookbook.md` | User needs init/plan/apply/destroy patterns or state commands | | State management, remote backends | `resources/state-and-backends.md` | User asks about state files, locking, or remote backends | ## Quick Start ```bash # 1. Initialize working directory (downloads providers) terraform init # 2. Preview changes (always run before apply) terraform plan # 3. Apply changes (requires confirmation) terraform apply # 4. Destroy infrastructure (DANGEROUS — requires confirmation) terraform destroy ``` ## Core Command Tracks - **Initialize:** `terraform init` — downloads providers, sets up backend - **Validate & format:** `terraform validate`, `terraform fmt -recursive` - **Preview:** `terraform plan [-out=tfplan]` — no changes made - **Apply:** `terraform apply [tfplan]` — creates/updates resources - **Inspect state:** `terraform state list`, `terraform state show <resource>` - **Workspaces:** `terraform workspace list`, `terraform workspace select <name>` ## Safety Guardrails - Always run `terraform plan` before `terraform apply` — review the diff carefully. - `terraform destroy` is **irreversible** — confirm resource list before proceeding. - Never commit `terraform.tfstate` or `.tfvars` files containing secrets to version control. - Use `-target` sparingly; it can leave state inconsistent. - Enable state locking on remote backends to prevent concurrent modifications. ```bash # Inspect managed resources in state before making changes terraform state list terraform state show aws_instance.web ``` ## Workflow 1. Write or edit `.tf` configuration files. 2. Run `terraform fmt` to normalize formatting. 3. Run `terraform validate` to catch syntax errors. 4. Run `terraform plan` and review the proposed changes. 5. Run `terraform apply` only after reviewing the plan. 6. Commit updated `terraform.lock.hcl` but never `terraform.tfstate`. ## Related Skills - **pulumi** — IaC using general-purpose languages (TypeScript, Python, Go, C#) - **ansible** — configuration management and agentless automation ## References - `resources/install-and-setup.md` - `resources/configuration.md` - `resources/command-cookbook.md` - `resources/state-and-backends.md` - Official docs: <https://developer.hashicorp.com/terraform/docs> - Provider registry: <https://registry.terraform.io> - Best practices: <https://www.terraform-best-practices.com> - Tutorials: <https://developer.hashicorp.com/terraform/tutorials>
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.