push-to-registry

Push Packer build metadata to HCP Packer registry for tracking and managing image lifecycle. Use when integrating Packer builds with HCP Packer for version control and governance.

Quality

78%

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/push-to-registry/SKILL.md

Quality

Content

82%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 strong, highly actionable skill: complete executable examples for the core registry configuration, authentication, CI/CD, and Terraform consumption, plus practical troubleshooting. The only notable improvements are trimming incidental template details and moving secondary use-case sections into separate reference files.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable code with terse, purposeful prose and no over-explanation of concepts Claude already knows. Minor over-inclusion keeps it at anchor 4 rather than 5: the full source block (region, instance type, AMI filter, apt provisioner) is incidental to the registry-push topic and could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: a complete Packer HCL template with the hcp_packer_registry block, exact environment-variable auth commands, a full GitHub Actions workflow, and a Terraform data-source example. The 'Registry Configuration Options' section documents each field with working snippets, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The sequence is clear (configure template → set auth env vars → run packer build) and the 'Common Issues' section provides error-recovery guidance for auth failures, bucket mismatch, and push failures. It falls short of anchor 5 only because there is no explicit post-build verification step (e.g., confirm the bucket and channel appear in HCP before publishing a channel).	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and a References list of official docs; no bundle files exist so all content is inline. Anchor 4 fits: most content is appropriately placed, but the CI/CD and Terraform-querying sections (~25 lines each) are secondary use-cases that could move to reference files to keep SKILL.md as a lean overview.	4 / 5
	Total	17 / 20 Passed

Description

73%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 solid description with a clear what, an explicit 'Use when' clause, and a distinct niche. Its main weakness is specificity — it names only one concrete action and leans on a generic 'image lifecycle' phrase rather than enumerating the registry capabilities the skill actually teaches.

Suggestions

Replace 'tracking and managing image lifecycle' with the concrete capabilities covered, e.g., 'configure bucket names and labels, authenticate with a service principal, and query registry channels from Terraform'.

Make the 'Use when' clause more trigger-phrase oriented, e.g., 'Use when a Packer template needs an hcp_packer_registry block, HCP authentication fails, or Terraform needs to pin AMIs via HCP Packer channels'.

Include common user phrasings like 'HCP Packer registry' or 'publish Packer builds to HCP' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Packer', 'HCP Packer registry') and one concrete action ('Push Packer build metadata'), but the rest ('tracking and managing image lifecycle') is generic. It does not enumerate multiple specific capabilities (labels, channels, bucket configuration, Terraform integration) that the skill actually covers.	3 / 5
Completeness	Both parts are present: a clear 'what' ('Push Packer build metadata to HCP Packer registry') and an explicit 'Use when...' clause. The 'when' could be more concrete — 'integrating Packer builds with HCP Packer for version control and governance' is somewhat abstract compared to listing concrete trigger scenarios, so it matches anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Good natural keyword coverage — 'Packer builds', 'HCP Packer', 'registry', 'version control and governance' are phrases users would naturally say. A few natural variations (e.g., 'HCP Packer registry', 'image registry', 'push images') are missing, keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The description occupies a clear niche (Packer-to-HCP-Packer registry integration) with distinct, specific triggers. There is virtually no overlap risk with unrelated skills, matching anchor 5.	5 / 5
	Total	16 / 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/push-to-registry/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.