CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

Install with Tessl CLI

npx tessl i github:hashicorp/agent-skills --skill azure-verified-modules
What are skills?

89

1.24x

Quality

70%

Does it follow best practices?

Impact

91%

1.24x

Average score across 10 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./terraform/code-generation/skills/azure-verified-modules/SKILL.md
SKILL.md
Review
Evals

Quality

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 effectively communicates its specialized purpose for AVM-certified Azure Terraform modules with clear 'when to use' guidance. However, it could be strengthened by listing specific concrete actions (what the skill actually does) and including more natural trigger term variations that users might employ.

Suggestions

Add specific concrete actions like 'validate naming conventions, check required tags, verify module structure, ensure documentation compliance'

Expand trigger terms to include variations like 'verified module', 'AVM compliance', 'Azure module standards', 'terraform azure module'

DimensionReasoningScore

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 terms like 'Azure', 'AVM', 'Terraform modules', 'AVM certification', but misses common variations users might say like 'verified module', 'Azure module standards', 'AVM compliance', or 'terraform azure module'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche targeting AVM certification for Azure Terraform modules - unlikely to conflict with general Terraform skills or generic 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 comprehensive AVM requirements reference with strong actionability through concrete HCL examples and specific constraints. The main weaknesses are its length (could be split into focused sub-documents) and lack of explicit development workflow with validation checkpoints. The checklist is useful but duplicates content rather than serving as a quick reference.

Suggestions

Split the document into focused sub-files (e.g., variables.md, outputs.md, testing.md) with SKILL.md serving as a concise overview with links

Add an explicit workflow section showing the sequence: create module → validate with tflint/checkov → test → document → review checklist

Remove the summary statistics section and consolidate the checklist to avoid duplication with the detailed sections above

DimensionReasoningScore

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 concepts Claude would know.

2 / 3

Actionability

Provides concrete, executable HCL code examples throughout, specific version constraints, exact file names, and copy-paste ready patterns. The examples are complete and directly usable.

3 / 3

Workflow Clarity

The content is well-organized with clear sections and a table of contents, but lacks explicit workflow sequences for module development. The checklist at the end provides validation steps but doesn't include feedback loops or error recovery guidance for the development process.

2 / 3

Progressive Disclosure

Good table of contents and section organization, but the document is monolithic at ~400 lines. External references are provided at the top but detailed content that could be split (e.g., the full checklist, testing requirements) remains inline. Could benefit from splitting into separate files for different requirement categories.

2 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (614 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata' field is not a dictionary

Warning

license_field

'license' field is missing

Warning

Total

13

/

16

Passed

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.