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.
Install with Tessl CLI
npx tessl i github:hashicorp/agent-skills --skill push-to-registry85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
HCP Packer registry block configuration
hcp_packer_registry block
50%
100%
Required version
100%
100%
Stable bucket name
100%
100%
No timestamp in bucket_name
100%
100%
build_labels for build-specific data
100%
100%
bucket_labels for stable metadata
100%
100%
Meaningful label keys
100%
100%
Auth env vars documented
50%
100%
Contributor role mentioned
100%
100%
bucket_name field present
100%
100%
Without context: $0.1939 · 1m 11s · 12 turns · 15 in / 3,579 out tokens
With context: $0.3543 · 1m 12s · 20 turns · 19 in / 3,983 out tokens
GitHub Actions CI/CD integration
setup-packer action
100%
100%
packer init before build
100%
100%
HCP_CLIENT_ID secret
100%
100%
HCP_CLIENT_SECRET secret
100%
100%
HCP_ORGANIZATION_ID secret
0%
100%
HCP_PROJECT_ID secret
0%
100%
git commit SHA passed
100%
100%
Trigger on main push
100%
100%
Contributor role documented
100%
100%
All four secrets listed
50%
100%
Without context: $0.2702 · 1m 12s · 18 turns · 19 in / 3,655 out tokens
With context: $0.3442 · 57s · 21 turns · 302 in / 3,330 out tokens
Terraform HCP Packer artifact consumption
hcp_packer_artifact data source
100%
100%
bucket_name in data source
100%
100%
channel_name in data source
100%
100%
platform specified
100%
100%
region specified
100%
100%
external_identifier usage
100%
100%
No hardcoded AMI
100%
100%
HCP_CLIENT_ID documented
100%
100%
HCP_CLIENT_SECRET documented
100%
100%
HCP_ORGANIZATION_ID documented
0%
0%
HCP_PROJECT_ID documented
100%
0%
Contributor role documented
0%
100%
bucket_name tag on instance
40%
100%
Without context: $0.2219 · 1m 7s · 14 turns · 15 in / 3,203 out tokens
With context: $0.2283 · 47s · 16 turns · 14 in / 2,916 out tokens
Table of Contents
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.