gh-pkg-kit

Manage GitHub Packages assets, migrations, and versions via the gh CLI.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/srz-zumix/gh-pkg-kit --skill gh-pkg-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pkg-kit
Source: https://github.com/srz-zumix/gh-pkg-kit/tree/main/skills/gh-pkg-kit
Command: npx skills add https://github.com/srz-zumix/gh-pkg-kit --skill gh-pkg-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-pkg-kit provides a streamlined way to interact with GitHub Packages from the command line, enabling developers to download assets, migrate packages, and manage versions without switching contexts.

Core Features & Use Cases

  • Package asset download across container, gem, maven, npm, and nuget registries.
  • Migrate packages between owners/registries (including legacy docker to ghcr.io).
  • Manage packages and versions for organizations and users (list, get, delete, restore, and version operations) via gh pkg-kit.

Quick Start

Install gh-pkg-kit and start managing GitHub Packages from the command line.

Frequently Asked Questions about gh-pkg-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage GitHub Packages from the command line?

You can migrate GitHub Packages between owners and registries using gh-pkg-kit, which supports migrating legacy docker packages from docker.pkg.github.com to the GitHub Container Registry at ghcr.io.

Can I download package assets across different registry formats?

Yes, you can download package assets across multiple registry formats including container, gem, maven, npm, and nuget directly through the gh-pkg-kit command line interface.

Do I need the gh CLI configured to access GitHub Packages registries?

Yes, you need a configured gh CLI with authentication and appropriate tokens to access registries like ghcr.io, docker.pkg.github.com, npm, maven, and nuget through gh-pkg-kit.

What is the best way to migrate legacy docker packages to ghcr.io?

The best way to migrate legacy docker packages to ghcr.io is using gh-pkg-kit, which automates package migration between owners and registries directly from the command line.

Why does my package management workflow require switching between different registry interfaces?

Switching interfaces is unnecessary because gh-pkg-kit centralizes package asset downloads, migration, and version management for container, gem, maven, npm, and nuget registries into one command line tool.