azure-image-builder
Build Azure managed images and Azure Compute Gallery images with Packer. Use when creating custom images for Azure VMs.
80
70%
Does it follow best practices?
Impact
100%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packer/builders/skills/azure-image-builder/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 'what' and 'when' clause, and targets a distinct niche (Packer-based Azure image building). However, it could benefit from listing more specific actions and including additional trigger terms that users might naturally use, such as 'shared image gallery', 'packer build', or 'VM image template'.
Suggestions
Add more specific actions like 'configure provisioners, define build variables, manage image versions, publish to shared image galleries'.
Include additional trigger terms users might naturally say, such as 'shared image gallery', 'packer build', '.pkr.hcl', 'VM image template', or 'golden image'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure images with Packer) and two specific types of outputs (managed images, Compute Gallery images), but doesn't list more granular actions like configuring provisioners, defining build steps, or managing image versions. | 2 / 3 |
Completeness | Clearly answers both 'what' (build Azure managed images and Compute Gallery images with Packer) and 'when' (Use when creating custom images for Azure VMs), with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure', 'Packer', 'managed images', 'Compute Gallery', and 'custom images', but misses common variations users might say such as 'VM image', 'image template', 'HCL', 'packer build', 'shared image gallery' (the older name), or '.pkr.hcl'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Packer + Azure image building is a very specific niche that is unlikely to conflict with other skills. The mention of both 'managed images' and 'Compute Gallery images' further narrows the scope. | 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 solid, actionable skill with complete, executable HCL templates and clear build commands for Azure image building with Packer. Its main weaknesses are some redundancy (authentication env vars shown twice, slightly verbose variable declarations) and a lack of explicit validation/error-recovery workflows for what is a costly, time-consuming operation. The content structure is reasonable but could benefit from tighter organization.
Suggestions
Add explicit pre-build validation steps (e.g., verify resource group exists, check SP permissions) and a feedback loop for build failures to improve workflow clarity.
Remove the duplicate environment variable export section — consolidate authentication setup in one place to improve conciseness.
Consider showing the Compute Gallery config as a delta from the basic template rather than repeating the full source block to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete HCL examples, but includes some unnecessary verbosity like the cost/timing note, redundant authentication sections (env vars are shown twice), and the 'Common Issues' section contains somewhat generic troubleshooting advice that could be tightened. | 2 / 3 |
Actionability | Provides fully executable HCL templates, concrete bash commands for service principal creation, and copy-paste ready build commands. The examples are complete and specific with real Azure image references, VM sizes, and gallery configuration. | 3 / 3 |
Workflow Clarity | The build commands section shows a clear sequence (init → validate → build), but there's no explicit validation checkpoint or feedback loop for handling build failures. For an operation that takes 15-45 minutes and incurs costs, there should be more explicit pre-flight checks and error recovery guidance. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's somewhat monolithic for its length (~150 lines of templates). The basic managed image template could be more concise with the gallery variant shown as a delta. References to external docs are present but minimal. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.