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

75%

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

76%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 highly actionable, well-structured reference skill carried by complete executable examples. Its main weakness is workflow clarity: the build/push path lacks an explicit validation checkpoint despite being a batch-style registry operation.

Suggestions

Add a short numbered build/push workflow with an explicit validation checkpoint, e.g. run `packer validate .` before `packer build` and confirm the iteration appears in HCP Packer before proceeding.

Frame the 'Build Fails' recovery notes as an inline validate -> fix -> retry loop within the workflow rather than only in Common Issues.

After a successful push, include a one-line verification step (query the channel/iteration via the Terraform data source or `hcp` CLI) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code with brief, focused explanations and tight bullet sections; only minor phrasing (e.g. the free-tier/overhead note) could be trimmed without loss.	4 / 5
Actionability	Provides copy-paste-ready HCL, environment variables, a full GitHub Actions workflow, and a Terraform data-source example covering the common cases end to end.	5 / 5
Workflow Clarity	The configure -> authenticate -> build sequence is inferable from the sections, but the build/push flow has no explicit validation checkpoint; recovery guidance lives in troubleshooting rather than an inline validate -> fix -> retry loop, and registry pushes are a batch-style operation the cap rule flags.	3 / 5
Progressive Disclosure	Well-organized into clear sections with a References list of relevant external docs and no bundle files to split; content is appropriately placed in a single file with minor organization gaps.	4 / 5
	Total	16 / 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 niche, an explicit 'Use when' trigger, and good natural keywords. It is held back from the top tier by abstract purpose language in place of additional concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('HCP Packer registry') and one concrete action ('Push Packer build metadata'), but 'tracking and managing image lifecycle' and 'version control and governance' are abstract benefits rather than concrete actions, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers 'what' (push build metadata to HCP Packer registry) and 'when' ('Use when integrating Packer builds with HCP Packer'), but the 'when' clause leans on broad purposes (version control, governance) rather than sharper trigger phrases.	4 / 5
Trigger Term Quality	Natural trigger terms 'Packer builds', 'HCP Packer', and 'registry' appear in a usable 'Use when...' clause; a few natural synonyms are absent but keyword coverage is good.	4 / 5
Distinctiveness Conflict Risk	'HCP Packer registry' is a clear, narrow niche with distinct triggers, creating minimal overlap risk with other skills.	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: 3268468

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.