windows-builder

Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.

1.47x

Quality

85%

Does it follow best practices?

Impact

100%

1.47x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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

A dense, actionable reference of executable Packer patterns for Windows builds across AWS and Azure. Its main gaps are the absence of explicit validation/verification checkpoints in the build workflow and a dangling reference to a scripts/setup-winrm.ps1 file that is not bundled.

Suggestions

Add an explicit validation checkpoint after provisioning and before image creation (e.g., verify WinRM connectivity, confirm installed features) to lift workflow clarity.

Either provide the referenced scripts/setup-winrm.ps1 as a bundled file or remove the dangling reference so progressive disclosure is consistent.

Consider moving the AWS/Azure full source examples and the WinRM setup script into a bundled reference file to keep SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	Lean reference dominated by executable HCL and PowerShell code with minimal explanatory prose; it avoids re-explaining concepts Claude already knows and every section earns its place.	3 / 3
Actionability	Provides complete, copy-paste-ready HCL source blocks and PowerShell provisioner snippets for AWS and Azure builds, software install, Windows Updates, and cleanup.	3 / 3
Workflow Clarity	Steps follow a logical order (WinRM setup, provisioning, cleanup) but lack explicit validation checkpoints, and a destructive resource-creating build workflow with no verify step is capped at 2 per the rubric.	2 / 3
Progressive Disclosure	Well-sectioned single file, but at ~180 lines it keeps the full WinRM setup script and multi-cloud examples inline, and it references scripts/setup-winrm.ps1 which does not exist as a bundle file.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 well-crafted description that uses third-person voice, names specific tools and target platforms, and includes an explicit 'Use when' trigger clause. It is distinguishable and actionable, with the only weakness being that it describes one build action with mechanisms rather than a breadth of distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and primary action ('Build Windows images with Packer using WinRM communicator and PowerShell provisioners'), but these are mechanisms for a single build action rather than a comprehensive list of multiple distinct concrete actions.	2 / 3
Completeness	Explicitly states what it does ('Build Windows images with Packer...') and when to use it via an explicit 'Use when creating Windows AMIs, Azure images, or VMware templates' clause.	3 / 3
Trigger Term Quality	Includes natural terms users would say when needing this skill: 'Windows images', 'Packer', 'Windows AMIs', 'Azure images', and 'VMware templates'.	3 / 3
Distinctiveness Conflict Risk	Clear niche (Windows image building with Packer via WinRM) with distinct, platform-specific triggers that are unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: hashicorp/agent-skills
Commit: 957d5f9

Reviewed: 4 days 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.