azure-image-builder

Build Azure managed images and Azure Compute Gallery images with Packer. Use when creating custom images for Azure VMs.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/packer/skills/azure-image-builder/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, code-first skill with executable examples, a sensible build workflow, and useful troubleshooting guidance. Main gaps are mild duplication of auth env vars, a truncated Gallery example, and no progressive-disclosure split of the longer code templates.

Suggestions

Deduplicate the ARM_CLIENT_ID/ARM_CLIENT_SECRET/ARM_SUBSCRIPTION_ID/ARM_TENANT_ID export blocks — keep them in one place and reference that from the build commands.

Complete the Azure Compute Gallery example with its build block and provisioner so it is copy-paste runnable on its own, and add a post-build verification step (e.g., `az image show` or `az sig image-version list`) to close the workflow loop.

Move the full managed-image HCL template into a references/ file and keep a minimal quick-start snippet in SKILL.md to reduce the always-loaded token footprint.

Dimension	Reasoning	Score
Conciseness	The body is lean, code-first, and free of concept explanations Claude already knows, but the ARM_CLIENT_* export block in "Build Commands" duplicates the one under "Service Principal". Minor trimming possible, so anchor 4 rather than 5.	4 / 5
Actionability	The basic managed-image HCL, `az ad sp create-for-rbac`, and `packer init/validate/build` commands are copy-paste ready. Not a 5: the Compute Gallery example omits the `build`/provisioner block, and Managed Identity uses "# ... rest of configuration".	4 / 5
Workflow Clarity	A clear ordered sequence exists (auth -> `packer init` -> `packer validate` -> `packer build`) with a pre-build validation checkpoint and a "Common Issues" section for error recovery. Not a 5 because there is no post-build verification step (e.g., confirming the image exists via `az image show`).	4 / 5
Progressive Disclosure	Sections are well organized with clear one-level external links (Packer ARM builder, Azure Compute Gallery docs), and no bundle files exist so nothing is misfiled. Not a 5 because all ~185 lines are inlined in SKILL.md; the full HCL template could be split into a references file to keep the overview lighter.	4 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description with concrete actions, an explicit 'Use when' clause, and highly distinctive trigger terms. Its only weakness is limited trigger variability — a single when-phrase and few synonyms.

Dimension	Reasoning	Score
Specificity	"Build Azure managed images and Azure Compute Gallery images with Packer" names concrete deliverables and the tool, covering the skill's scope with only minor gaps. Not a 3 because the actions named are specific rather than generic; not a 5 because only two actions are listed rather than the multiple comprehensive actions of the top anchor.	4 / 5
Completeness	Both parts are explicit: what ("Build Azure managed images and Azure Compute Gallery images with Packer") and when ("Use when creating custom images for Azure VMs"). Not a 5 because the when-clause offers a single trigger rather than a set of concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural user phrases are present: "Packer", "custom images", "Azure VMs", "Azure Compute Gallery". Not a 5 because common synonyms like "golden image" or "VM image" are missing.	4 / 5
Distinctiveness Conflict Risk	"Azure" + "Packer" + "Azure Compute Gallery" is a clear niche with distinct triggers; minimal risk of firing for an unrelated skill.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: hashicorp/agent-skills
Path: plugins/packer/skills/azure-image-builder/SKILL.md
Commit: 516354c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.