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 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', and '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 and highly actionable reference for AVM Terraform module development, with excellent concrete examples and a useful compliance checklist. Its main weaknesses are its length (could benefit from splitting into overview + reference files) and the lack of an explicit development workflow with validation checkpoints. The content is well-organized within its monolithic structure but would benefit from progressive disclosure to reduce token consumption.
Suggestions
Split the detailed requirements (variables, outputs, code style) into separate reference files and keep SKILL.md as a concise overview with links, reducing token consumption significantly.
Add an explicit step-by-step workflow section (e.g., 'Creating an AVM Module') with validation checkpoints like running tflint, checkov, and terraform validate at specific stages.
Remove the summary statistics section and introductory sentences that don't add actionable value (e.g., 'This guide covers the mandatory requirements...' and 'These requirements ensure consistency...').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400 lines) and includes some redundancy and explanatory text that Claude doesn't need (e.g., explaining what snake_casing is, the summary statistics section). However, most content is specification-driven and reasonably dense with actual requirements rather than fluff. | 2 / 3 |
Actionability | The skill provides concrete, executable HCL code examples for nearly every requirement, with clear good/bad patterns, specific version constraints, and a comprehensive compliance checklist. The examples are copy-paste ready and directly usable. | 3 / 3 |
Workflow Clarity | The compliance checklist at the end provides a clear sequence for review, but the overall document is more of a reference specification than a workflow. There are no explicit validation checkpoints or feedback loops for the module development process (e.g., validate -> fix -> retry cycles when building a module). | 2 / 3 |
Progressive Disclosure | The document has a table of contents and clear section headers, but it's a monolithic ~400-line file with no references to supporting bundle files. Content like the full breaking changes list, detailed variable requirements, and the compliance checklist could be split into separate reference files to keep the main skill leaner. | 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
339a113
- 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.