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.
This description is functional with a clear 'Use when' clause and distinct focus on AVM certification. However, it could be strengthened by listing specific concrete actions (what the skill actually does beyond 'requirements and best practices') and including more natural trigger terms users might use when seeking AVM guidance.
Suggestions
Add specific concrete actions like 'validate module structure, check naming conventions, verify required outputs, ensure documentation compliance'
Expand trigger terms to include variations like 'verified module', 'AVM compliance', 'Azure module standards', 'module certification requirements'
| 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, check resource tagging, verify 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure', 'AVM', 'Terraform modules', 'certification', but misses common variations users might say like 'verified module', 'Azure module standards', 'AVM compliance', or 'module validation'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting AVM certification for Azure Terraform modules - unlikely to conflict with general Terraform skills or other Azure skills due to the specific 'AVM certification' focus. | 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 well-structured reference document with strong actionability through concrete HCL examples and clear good/bad patterns. The main weaknesses are its length (could benefit from splitting into focused sub-documents) and lack of an explicit development workflow with validation checkpoints for achieving AVM certification. The compliance checklist is useful but duplicates content rather than serving as a standalone validation tool.
Suggestions
Add a 'Getting Started' workflow section at the top with numbered steps for developing an AVM-compliant module, including explicit validation checkpoints (e.g., 'Run tflint -> Fix issues -> Run terraform validate -> Run Checkov')
Split detailed requirements into separate files (e.g., VARIABLES.md, OUTPUTS.md, CODE_STYLE.md) and keep SKILL.md as a concise overview with links
Remove the summary statistics section and consolidate the compliance checklist into a separate CHECKLIST.md file that can be used independently
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some redundancy (e.g., repeating severity/requirement IDs throughout, summary statistics at the end). The checklist duplicates information already covered in detail above. However, it avoids explaining basic Terraform concepts Claude already knows. | 2 / 3 |
Actionability | Provides concrete, executable HCL code examples throughout. Each requirement includes specific patterns to follow with copy-paste ready examples (provider blocks, variable definitions, dynamic blocks, output patterns). The good/bad comparisons make correct implementation clear. | 3 / 3 |
Workflow Clarity | This is primarily a reference/standards document rather than a multi-step workflow. The compliance checklist provides a validation mechanism, but there's no explicit workflow for module development with validation checkpoints. For a certification-focused skill, a step-by-step development workflow with validation gates would strengthen this. | 2 / 3 |
Progressive Disclosure | Good table of contents and section organization. However, the document is quite long (~400 lines) and could benefit from splitting detailed requirements into separate files (e.g., variables.md, outputs.md). External references are provided but only to official AVM docs, not to modular internal documentation. | 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
9f2ede9
- 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.