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 interface structure, verify documentation standards' to improve specificity.
Include additional trigger term variations like 'azurerm provider', 'module compliance', 'AVM standards', 'verified module pattern' to improve keyword coverage.
| 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 thorough and well-structured reference document for AVM Terraform module certification with strong actionability through concrete HCL examples and a useful compliance checklist. Its main weaknesses are verbosity (the content could be significantly condensed, and the checklist duplicates the body), lack of a clear sequential workflow for module development/review, and being monolithic when it would benefit from progressive disclosure across multiple files.
Suggestions
Add a clear sequential workflow section (e.g., 'Module Development Process') with numbered steps and validation checkpoints, such as: 1) scaffold structure, 2) implement with code style standards, 3) run tflint/checkov, 4) validate with terraform validate, 5) run tests, 6) generate docs.
Split the document into a concise SKILL.md overview (~100 lines) with the most critical requirements and checklist, referencing detailed files like CODE_STYLE.md, VARIABLES.md, BREAKING_CHANGES.md for the full specifications.
Remove the compliance checklist or the detailed body sections—having both is redundant. Keep the checklist in SKILL.md and move detailed explanations to referenced files.
Trim explanatory text that Claude already knows (e.g., what snake_case means, basic Terraform provider concepts) and focus on AVM-specific deviations from standard Terraform practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but quite verbose at ~400+ lines. Many sections restate things Claude would know (e.g., explaining what snake_case is, basic Terraform concepts). The checklist at the end largely duplicates the body content. However, the structured format with tables and examples keeps it from being purely wasteful. | 2 / 3 |
Actionability | The skill provides concrete, executable HCL code examples throughout (provider blocks, dynamic blocks, feature toggles, output patterns, variable definitions). Each requirement is paired with specific do/don't examples that are copy-paste ready. The compliance checklist provides a concrete verification mechanism. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/specification document rather than a workflow guide. While the compliance checklist provides a verification step, there's no clear sequenced workflow for creating or reviewing a module (e.g., start here, validate this, then proceed). For a certification-oriented skill involving potentially breaking changes, explicit validation checkpoints and a step-by-step development workflow are missing. | 2 / 3 |
Progressive Disclosure | The table of contents and section headers provide good internal navigation, and external references to AVM docs are included. However, at 400+ lines this is a monolithic document that would benefit from splitting detailed sections (e.g., breaking changes, code style, variable requirements) into separate referenced files. No bundle files exist to offload content. | 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
43ca9b0
- 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.