glab-packages — Claude Code skill: GitLab packages via glab
Gives the agent the glab packages command surface: list registry entries, upload a file, fetch a version, remove a package.
MIT 123 installs ★ 51 updated 2026-10-20
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a claude-codeWhat glab-packages does
The skill documents glab packages. Listing is list (alias ls), generic files travel up with upload/ul and back down with download/dl, and registry entries are removed by delete/rm. Name and package-type filters, paging through --page and --per-page, plus --jq output for scripts sit in the same reference.
Every upload becomes a generic package. You need both --name and --version; the stored filename comes from the local basename unless --filename says otherwise. Downloads are generic-only and want name, version and filename together. glab compares the file against registry checksum metadata and will not clobber an existing target, so overwriting takes --force. Skipping the check with --no-verify is for the case where you knowingly accept the integrity risk.
Deletion is permanent and asks for confirmation. A script that omits --yes just hangs at that prompt, so look up the package ID with list first, then pass the flag. Outside the project checkout you must name the repo with -R owner/repo; otherwise glab acts on whatever repository the current directory points at.
What it helps with
- list packages published in a project registry
- upload a build artifact as a generic package version
- pull one package file into a chosen directory
- delete a stale package by name and version
- page through registry results inside a script
Example prompts for the agent
- List the packages in this project registry and filter them to
maven. - Upload
./build/app.zipasmy-packageversion1.0.0. - Download
app.zipfrom version1.0.0into./downloads/without overwriting anything.
How to install glab-packages
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a claude-code2Manually: put the files in place
~/.claude/skills/glab-packages/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glab-packages/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a codex2Manually: put the files in place
.agents/skills/glab-packages/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a cursor2Manually: put the files in place
.cursor/skills/glab-packages/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vince-winkintel/gitlab-cli-skills glab-packages2Manually: put the files in place
.github/skills/glab-packages/SKILL.md1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a gemini-cli2Platform CLI
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-packagesManually: put the files in place
.devin/skills/glab-packages/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about glab-packages
How do I install glab-packages in Claude Code?
Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-packages -a claude-code. The skill lands in ~/.claude/skills/glab-packages/SKILL.md.
What does glab-packages do?
It spells out the glab packages commands for listing a project registry, uploading and downloading generic files, and deleting entries. The agent gets flags and step order instead of guessing.
Why does a download fail when the target file already exists?
glab verifies the downloaded file against registry checksum metadata and refuses to overwrite by default. Add --force to replace the file, and keep --no-verify for the rare case where you accept skipping the checksum.
Source text
SKILL.md · MIT
--- name: glab-packages description: List, upload, download, and delete GitLab project package registry packages with glab. Use when inspecting packages, filtering GitLab package registry entries by package name/type, paginating package registry results, uploading or downloading generic package files, deleting packages, or using glab packages commands. Triggers on GitLab packages, package registry, glab packages, npm packages in GitLab, Maven packages in GitLab, generic package upload, generic package download, delete package. --- # glab packages List packages in a GitLab project's package registry, upload/download generic package files, and delete package registry entries by numeric ID or by `--name`/`--version`. `glab packages list` / `ls` lists project package registries. The current command surface also includes `upload` / `ul` for generic package uploads, `download` / `dl` for generic package downloads, and `delete` / `rm` for package deletion by numeric ID or by `--name`/`--version`. ## Delete by name and version `glab packages delete --name example-generic --version 1.0.0` resolves the package in the selected project; `--package-type` defaults to `generic`. Supply the type explicitly for another ecosystem. `--name` and `--version` are required together. A positional numeric ID, `--id`, and `--name` are alternative selectors; do not combine them. The `rm` alias accepts the same options. Preview the exact project, package name, version, type, and resolved ID before approving deletion. Deletion is permanent and prompts interactively; non-interactive use requires `--yes`, which must only follow explicit approval. ## Quick start ```bash # List all packages in the current project glab packages list # Alias glab packages ls # List packages from another project glab packages list -R owner/repo # Upload a file as a generic package version glab packages upload ./build/app.zip --name my-package --version 1.0.0 # Download a generic package file glab packages download --name my-package --version 1.0.0 --filename app.zip # Delete a package by numeric ID after listing packages glab packages delete 12345 --yes ``` ## Filtering ```bash # Filter by package name substring glab packages list --name my-package # Filter by package type glab packages list --package-type npm glab packages list --package-type maven glab packages list --package-type generic ``` Supported package types from glab help: ```text composer, conan, debian, generic, golang, helm, maven, npm, nuget, pypi, terraform_module ``` ## Pagination and automation ```bash # Select a page and page size glab packages list --page 2 --per-page 10 # JSON output filtering is available through the global --jq support on this command glab packages list --jq '.[].name' ``` Use `-R/--repo` when running outside the target project's Git checkout. Prefer structured output/`--jq` for scripts rather than parsing text tables. ## Upload generic package files ```bash # Upload a local file under its original filename glab packages upload ./build/app.zip --name my-package --version 1.0.0 # Store the uploaded file under a different package filename glab packages upload ./build/app.zip --name my-package --version 1.0.0 --filename release.zip # Alias and explicit target project glab packages ul ./build/app.zip -n my-package --version 1.0.0 -R owner/repo ``` Upload stores the file as a **generic** package in the target project's package registry. `--name` and `--version` are required; `--filename` defaults to the local file basename. Use `-R/--repo` for uploads outside the target project checkout. ## Download generic package files ```bash # Download a package file to the current directory glab packages download --name my-package --version 1.0.0 --filename app.zip # Download into a directory, keeping the original file name glab packages download -n my-package --version 1.0.0 --filename app.zip --path ./downloads/ # Download to an exact path, renaming the file glab packages download -n my-package --version 1.0.0 --filename app.zip --path ./downloads/renamed.zip # Download to an absolute path (missing parent directories are created) glab packages download -n my-package --version 1.0.0 --filename app.zip --path /tmp/downloads/app.zip # Skip checksum verification only when you intentionally accept the integrity risk glab packages download -n my-package --version 1.0.0 --filename app.zip --no-verify # Alias, overwrite an existing target, and explicit project targeting glab packages dl -n my-package --version 1.0.0 --filename app.zip --force -R owner/repo ``` Download is limited to **generic** package files and requires `--name`, `--version`, and `--filename`. By default glab verifies the downloaded file against registry checksum metadata and fails if the destination already exists. Use `--path` for a relative or absolute directory/exact output filename; glab creates missing parent directories. Use `--force` to overwrite and `--no-verify` only when checksum verification is intentionally bypassed. For downloads with duplicate filenames, checksum verification uses the newest matching package file (the highest file ID). ## Delete packages ```bash # Find the package ID first glab packages list --name my-package # Delete by numeric package ID; prompts for confirmation glab packages delete 12345 # Skip confirmation for automation after independently confirming the ID glab packages delete 12345 --yes # Alias glab packages rm 12345 ``` Delete accepts a numeric ID or the `--name`/`--version` pair described above. Use `glab packages list` (preferably with JSON/`--jq` in scripts) to identify the ID, then pass `--yes` only when the target package has been verified. ## Reference See [references/commands.md](references/commands.md) for command synopsis and flags.
© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills