Push Packer build metadata to HCP Packer registry for image lifecycle tracking and governance.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add hashicorp/agent-skills --skill push-to-registryCompatible with
Supported agents
Registers build artifacts in HCP Packer with minimal overhead, storing metadata only (not actual images) and adding less than one minute to build time
Supports bucket-level labels (updated per build) and immutable build-level labels (git SHA, timestamps) for version control and compliance tracking
Integrates with Terraform via hcp_packer_artifact data source to query and deploy images acros
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpush-to-registryExecute the skills CLI command in your project's root directory to begin installation:
epx add hashicorp/agent-skills --skill push-to-registryFetches push-to-registry from hashicorp/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/push-to-registry
Restart Cursor to activate push-to-registry. Access via /push-to-registryin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
powerpoint
igorwarzocha/opencode-workflows · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
alpine-js
mindrally/skills · Productivity · same category
Keeps context tight: push-to-registry is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: push-to-registry is focused, and the summary matches what you get after install.
We added push-to-registry from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
push-to-registry reduced setup friction for our internal harness; good balance of opinion and flexibility.
push-to-registry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
push-to-registry has been reliable in day-to-day use. Documentation quality is above average for community skills.
push-to-registry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added push-to-registry from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: push-to-registry is focused, and the summary matches what you get after install.
I recommend push-to-registry for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 53