INFRASTRUCTURE DEVELOPMENT / HashiCorp
Push to HCP Packer registry
Pins HashiCorp's Packer skill for pushing build metadata to an HCP Packer bucket, including the environment variables the build expects.
“Push Packer build metadata to HCP Packer registry for tracking and managing image lifecycle. …”
01 / THE REASONING
Why this made the selection.
- The catalogue has HashiCorp's aws-ami-builder Packer skill and not this HCP Packer registry skill.
- The file is explicit that the registry push records metadata rather than uploading the image bytes, and that a failed metadata push fails the Packer build.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- plugins/packer/skills/push-to-registry/SKILL.md
- README.md
- LICENSE
Our findings
- The skill says builds push metadata only, not the image, and that Packer fails immediately if it cannot push that metadata.
- It requires HCP_CLIENT_ID, HCP_CLIENT_SECRET, HCP_ORGANIZATION_ID, and HCP_PROJECT_ID, and it tells the reader to grant the service principal Contributor on the project.
- The GitHub Actions example uses hashicorp/setup-packer@main, so the action tracks a branch rather than a commit, and it passes a git_commit variable the shown template does not declare.
- The registry configuration distinguishes bucket labels updated on each build from build labels that become immutable when the build finishes.
Not established by this review
- The resource was not executed and its tools were not called.
- Packer was not run.
- No HCP API call was made.
- The HCP Packer documentation links were not opened.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
claude plugin install packer@hashicorp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- The README's Claude Code section installs the Packer plugin with the command above after claude plugin marketplace add hashicorp/agent-skills.
- That bundle is the Packer plugin, not a one-skill flag for push-to-registry.
- The README says every supported path is listed in SKILLS.md, which this review did not open.
Before you start
- A host that can install the HashiCorp Packer plugin or copy the skill directory
- Packer, if the template is built
- HCP service-principal credentials, which this review did not create
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- push-to-registry SKILL.md ↗Checked
https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/packer/skills/push-to-registry/SKILL.md
Supports: metadata-only push, required HCP variables, and the git_commit snippet
- Repository README ↗Checked
https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md
Supports: Packer plugin install line and MPL-2.0 statement
- Repository LICENSE ↗Checked
https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE
Supports: Mozilla Public License Version 2.0
https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/packer/skills/push-to-registry/SKILL.md
Supports: review.findings, bestFor, upstreamDescription