HashiCorp ships official Terraform Skills for Claude Code and Kiro

a computer screen with a bunch of code on it

HashiCorp published hashicorp/agent-skills, an MPL-2.0 repo of SKILL.md files covering Terraform and Packer conventions. The skills are written by the team that owns the actual HashiCorp style guide, not a third-party paraphrase of the docs.

️ What It Covers

The repo is organized by product and task type. Terraform skills span code generation (style guide, terraform test, Azure Verified Modules, search/import), module generation (refactoring, Terraform Stacks), provider development (scaffolding, resources, acceptance tests), and policy (tfpolicy authoring, Sentinel to tfpolicy conversion). Packer skills cover AWS, Azure, and Windows image builds plus HCP Packer registry integration.

Each skill is a single SKILL.md file loaded on demand. The agent reads only a short frontmatter description at session start and pulls the full file into context only when the current task matches. A prompt like write a Terraform module for an S3 bucket triggers the style guide skill. A prompt like explain what Terraform is does not.

Install for Claude Code and Kiro

For Claude Code, install the full Terraform bundle via the plugin marketplace:

claude plugin install terraform@hashicorp

Or install individual skills to keep context lean:

npx skills add hashicorp/agent-skills/terraform/code-generation/skills/terraform-style-guide
npx skills add hashicorp/agent-skills/terraform/policy/skills/terraform-policy

Kiro added native Skills support in version 1.24.0 and uses the same npx skills add command. The installer detects roughly 28 agents including Claude Code, Copilot, Cursor, Goose, and Kilo Code, then asks whether to install everywhere or let you pick. Run the install from inside the project directory in both cases. Skills are workspace-scoped, so a skill installed from a different directory won’t show up in the repo where you actually need it.

⚠️ Two Things to Know Before You Deploy

First, the repo is mid-migration on plugin IDs. Both the older per-category IDs (terraform-code-generation, terraform-module-generation) and the newer consolidated bundles (terraform@hashicorp, packer@hashicorp) exist depending on which commit you’re reading. If a command 404s, check the current README before assuming you did something wrong.

Second, a third-party audit of the style-guide skill noted it doesn’t build in an explicit validate-and-fix loop. It generates clean code most of the time but won’t catch its own syntax errors unless you separately run terraform fmt and terraform validate. Treat it as a strong prior, not a replacement for terraform plan and a review pass. If you’re installing skills automatically in CI, pin to a commit or tag rather than tracking main.

Stay on top of AI & Automation with BizStack Newsletter
BizStack  —  Entrepreneur’s Business Stack
Logo