azure-verified-modules
Azure Verified Modules (AVM) requirements and best practices for developing certified Azure Terraform modules. Use when creating or reviewing Azure modules that need AVM certification.
89
70%
Does it follow best practices?
Impact
91%
1.24xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/code-generation/skills/azure-verified-modules/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is well-structured with a clear 'Use when' clause and targets a distinct niche (AVM-certified Terraform modules). Its main weakness is the lack of specific concrete actions—it says 'requirements and best practices' without enumerating what those entail. Trigger terms are adequate but could benefit from additional natural variations users might employ.
Suggestions
Add specific concrete actions such as 'validate naming conventions, enforce required tags, check module structure, verify documentation standards' to improve specificity.
Include additional trigger term variations like 'azurerm', 'verified module', 'AVM standards', 'module compliance', or 'terraform azure module' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Verified Modules, Terraform) and mentions 'requirements and best practices' but doesn't list specific concrete actions like 'validate naming conventions, enforce resource tagging, check module structure'. | 2 / 3 |
Completeness | Clearly answers both 'what' (AVM requirements and best practices for developing certified Azure Terraform modules) and 'when' (Use when creating or reviewing Azure modules that need AVM certification) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'AVM', 'Azure', 'Terraform modules', 'AVM certification', but misses common variations users might say such as 'azurerm', 'module compliance', 'AVM standards', 'verified module', or 'terraform azure module'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Azure Verified Modules', 'AVM certification', and 'Terraform' creates a very specific niche that is unlikely to conflict with general Terraform skills or general Azure skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive reference document for AVM Terraform module certification with strong actionability through concrete HCL examples and a useful compliance checklist. Its main weaknesses are its monolithic length (could benefit from splitting detailed sections into separate files) and the lack of a clear development workflow with validation checkpoints. The content is well-organized within sections but tries to serve as both a quick reference and exhaustive specification.
Suggestions
Add a 'Getting Started' workflow section at the top that sequences the key steps for creating an AVM-compliant module (scaffold → implement → validate → test → document) with explicit validation checkpoints between steps.
Split the detailed reference content (code style standards, variable requirements, breaking changes) into separate linked files, keeping SKILL.md as a concise overview with the most critical requirements and the compliance checklist.
Remove the summary statistics section at the end - it adds no actionable value for Claude when developing or reviewing modules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly well-organized but quite lengthy (~400+ lines). Some sections could be tightened - e.g., the severity/requirement tags are repetitive, and the summary statistics at the end add little value. However, most content is genuinely informative and not explaining things Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable HCL code examples throughout (provider configuration, dynamic blocks, feature toggles, variable definitions, output patterns). The compliance checklist at the end is directly actionable for reviewing modules. | 3 / 3 |
Workflow Clarity | The content is structured as a reference guide rather than a workflow. While the compliance checklist provides a review sequence, there's no clear step-by-step workflow for creating an AVM module from scratch, and no validation/feedback loops (e.g., run tflint, fix issues, re-run). For a certification process, missing validation checkpoints is a notable gap. | 2 / 3 |
Progressive Disclosure | The table of contents and section headers provide good navigation, and external references are linked at the top. However, the content is monolithic - at 400+ lines, sections like the detailed breaking changes list, code style standards, and the full compliance checklist could be split into separate reference files. The skill tries to be both overview and complete reference in one file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (614 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- hashicorp/agent-skills
- Commit
de4323a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.