gitlab-cli-skills

gitlab-cli-skills is a comprehensive GitLab CLI (glab) command reference and workflow hub that routes to specialized sub-skills for authentication, CI/CD, merge requests, issues, releases, repositories, milestones, labels, packages, and 30+ other glab domains. It solves the problem of driving nearly all GitLab operations from the terminal — creating MRs, managing issues, viewing pipelines, handling releases, and Artifact Registry token exchange — with consistent, safe patterns and a set of helper scripts (CI debugging, creating an MR from an issue, posting inline comments, syncing a fork).

Much of the documentation is devoted to identity safety in multi-agent or multi-account setups. It explains that multiple tokens on one GitLab user still act as the same visible identity, recommends per-actor bot/service accounts and per-actor env files kept out of version control with restricted permissions, and treats shell identity as sticky and unsafe by default. It prescribes a required pre-flight (glab auth status and glab api user) before any GitLab write, plus a wrong-identity remediation procedure. Credentials are handled through official glab tooling: a GITLAB_TOKEN with api scope (or fallback to the stored glab config), outbound HTTPS to the GitLab instance with the token never sent over HTTP.

It targets developers and platform teams automating GitLab from the CLI, including agentic contexts. Two things warrant awareness: the skill's own notes disclose that some features access sensitive local files — the SSH private key (~/.ssh/id_rsa for DPoP) and Docker config (~/.docker/config.json for registry auth) — and its scripts can perform state-changing writes on your behalf, such as posting comments, resolving threads, and approving merge requests. Both are legitimate uses of official tooling with defensive guidance and no exfiltration, and the skill itself urges reviewing the auth workflows and scripts before autonomous use.