Azure Verified Modules for Terraform

Applies the 37 Azure Verified Modules requirements to Terraform modules: provider versions, sources, naming, variables, outputs, breaking changes and repository rules. Use when writing or reviewing an Azure module meant for AVM certification.

DevOpsPack: HashiCorp skillslinkazure-verified-modules
Author
Source
hashicorp/agent-skills/plugins/terraform/skills/azure-verified-modules @ 5e30fa5
License
MPL-2.0

About this skill

What it does

The skill condenses the Terraform requirements of Azure Verified Modules (AVM), the certification for Azure modules. It lists 37 requirements, each with its ID (TFFR1, TFNFR4 and so on) and severity: 21 MUST, 14 SHOULD, 2 MAY. The main groups:

  • Providers and sources: only azurerm 4.x and azapi 2.x, pinned; no provider blocks except aliases; other AVM modules only from the registry at a pinned version, never from git.
  • Code: snake_case names, a fixed argument order inside blocks, for_each only over a map or set with static keys, dynamic blocks for optional nested blocks.
  • Variables and outputs: no enabled or module_depends_on switches, precise types, no defaults for sensitive inputs, discrete computed outputs instead of whole resource objects.
  • Releases: a resource added in a minor or patch release goes behind an off-by-default toggle, and a list names the changes that break users.
  • Repository: docs from terraform-docs, nine branch-protection settings, and the required tools: terraform validate/fmt/test, terrafmt, Checkov, tflint with the azurerm ruleset.

It ends with a compliance checklist. The folder holds only SKILL.md; the skill runs none of those tools itself.

When to use it, and when not

Use it when writing or reviewing an Azure module meant for AVM certification, or before releasing one.

It is Azure-only and module-only, so root configurations and AWS or GCP modules gain little. It is a summary: the AVM specification it links to remains the authority.

How to run it

We do not copy this skill: its files are under MPL-2.0, a file-level copyleft licence outside the set we copy under. Install it from HashiCorp's repository with the button to the source: one skill via npx skills add hashicorp/agent-skills/plugins/terraform/skills/azure-verified-modules, or the whole terraform plugin via claude plugin marketplace add hashicorp/agent-skills, then claude plugin install terraform@hashicorp. In Codex: codex plugin marketplace add hashicorp/agent-skills, then install terraform from /plugins and start a new session. In Claude Code, the plugin's skill may appear as /terraform:azure-verified-modules.

  • Claude Code: /azure-verified-modules, or ask for the skill by name.
  • Codex: $azure-verified-modules.
  • Cursor: type / in the Agent chat and pick azure-verified-modules.

Example: /azure-verified-modules Review modules/storage-account and list every MUST requirement it fails.

How it differs from similar skills

Terraform style guide applies HashiCorp's general style to any configuration; this skill is narrower and stricter, adding version bounds, source bans and repository rules. Refactor Terraform into modules splits a monolith into modules and moves state with moved blocks, with no certification in view. Terraform tests shows how to write the terraform test suites that AVM only names as required tooling.

Install

This skill is not copied to the catalog: its licence allows a copy only under the same licence, and the catalog does not copy under such licences. Install it from the author's repository.

Open the source

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack HashiCorp skills

Terraform style guide

Applies HashiCorp's Terraform style conventions: standard file split, formatting, naming, typed variables, for_each over count, pinned versions and secrets kept out of state. Use when writing, reviewing or generating Terraform HCL.

Terraform tests

Writes and runs Terraform's native tests in .tftest.hcl files: run blocks, assertions, plan and apply modes, expect_failures, mock providers and CI pipelines. Use when adding tests to a Terraform module or fixing a failing terraform test.

Terraform Stacks

Writes Terraform Stacks configurations for HCP Terraform: components in .tfcomponent.hcl, deployments in .tfdeploy.hcl, OIDC identity tokens, auto-approve rules, linked Stacks and API monitoring. Use when building or debugging a Stack.

Refactor Terraform into modules

Splits a monolithic Terraform configuration into a reusable module with a typed interface, then migrates state with moved blocks or terraform state mv so nothing is recreated. Use when a root config has grown too large or repeats itself.

Terraform search and import

Finds existing cloud resources with Terraform Search queries in .tfquery.hcl, generates resource and import blocks, and falls back to manual import for unsupported types. Use when bringing hand-made infrastructure under Terraform.

Terraform policy files

Writes, converts and tests HCP Terraform policy files (.policy.hcl, .policytest.hcl), including Sentinel-to-tfpolicy conversion with a quality label per policy. Use when writing a new policy, porting Sentinel or debugging a policy test.

Terraform provider resources

Guides writing Terraform provider resources and data sources on the Plugin Framework: schema, CRUD, not-found handling, import, waiters for eventually consistent APIs and minimum tests. Use when adding, changing or reviewing a provider resource.

Terraform provider test patterns

Covers acceptance tests for Terraform providers with terraform-plugin-testing: test steps, state and plan checks, import, disappears and regression tests, sweepers and ephemeral resources. Use when writing, reviewing or debugging provider acceptance tests.

AWS AMIs with Packer

Builds Amazon Machine Images with Packer's amazon-ebs builder from a ready HCL template, with source filters, multi-region copies, credentials and fixes for common build errors. Use when creating a custom AMI for EC2.