Skip to content
TrustedSkillsbeta
Back to all skills

Terraform Style Guide

Official
hashicorp·vlatest·cloud·MPL-2.0

Enforces HashiCorp's Terraform style guide to ensure consistent, readable, and maintainable infrastructure code.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add hashicorp/agent-skills --skill terraform-style-guide -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hashicorp

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned hashicorp/agent-skills at f706481af9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f706481af9
Manifest
plugins/terraform/skills/terraform-style-guide/SKILL.md
Scanned
2 files, 452 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Terraform Style Guide skill provides standardized formatting and best practices for writing Terraform configuration files. It helps ensure consistency across teams, improves readability, and enforces conventions that align with HashiCorp's official recommendations.

When to use it

  • When multiple developers are working on the same Terraform project and need a shared standard for code style.
  • Before committing Terraform configurations to version control to automatically format them according to best practices.
  • When onboarding new team members who are unfamiliar with Terraform conventions.
  • To maintain clean, readable infrastructure-as-code (IaC) across large or evolving projects.

Key capabilities

  • Enforces consistent formatting of Terraform configuration files.
  • Applies naming conventions for resources and variables.
  • Ensures proper use of comments and documentation within configurations.
  • Aligns with HashiCorp’s official Terraform Style Guide recommendations.

Example prompts

  • "Format my Terraform code according to the HashiCorp style guide."
  • "Check this Terraform configuration for compliance with standard formatting rules."
  • "Apply the Terraform style guide to all modules in this project."

Tips & gotchas

  • Ensure that your environment has the necessary tools (like terraform fmt) installed and configured.
  • This skill works best when used alongside a linter or CI/CD pipeline to enforce style compliance automatically.