agentleFS
Sign inStart free
bordenetbordenet/superpowers-plus/skills/engineering/gitlab-cli/skill.md

gitlab-cli

Skill8 starsChanged 6 months agoMITView on GitHub

Use glab for GitLab merge requests, CI/CD, variables, issues, and raw API calls on gitlab.com or any self-hosted GitLab instance. Includes macOS/Windows install and auth walkthrough. Triggers on glab, GitLab CLI, GitLab MR, pipeline status, install/setup glab, or GitLab-specific repo operations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When glab is missing or auth fails, walk the user through these steps in order.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

GitLab CLI (glab)

Announce at start: "I'm using the gitlab-cli skill for GitLab / glab operations."

Do not use for: GitHub (gh), Azure DevOps, or Bitbucket workflows.

Agent setup walkthrough

When glab is missing or auth fails, walk the user through these steps in order. Ask which OS they use (macOS vs Windows) before giving install commands. Run checks yourself when you have shell access (with network enabled).

StepCheck / actionSuccess signal
1glab versionPrints a version (e.g. glab 1.x.x)
2Install glab if step 1 failsSee Install glab for their OS
3git --versionGit installed (needed for clone context and glab auth login remote detection)
4Ask GitLab hostnamegitlab.com or their self-hosted host (no https://)
5glab config set host <hostname> --globalOnly if not gitlab.com or host not already set
6Create PAT or OAuthSee Authenticate
7glab auth status (add --hostname <host> if self-managed)Shows logged in as their user
8cd into a GitLab clone; glab repo viewResolves project from origin
9Smoke test: glab mr list or glab api userAPI works end-to-end

For install, auth, MR, CI, variables, issues, API, and repo command reference, see reference.md.

Failure Modes

FailureFix
403 after valid glab auth statusSAML SSO: authorize the PAT at https://<host>/-/user_settings/personal_access_tokens then retry
SSL/TLS error on self-hosted instanceInstall internal CA cert, or use GITLAB_SSL_VERIFY=false for dev only
glab variable set overwrites a live secretAlways glab variable get <key> first; set has no confirmation prompt
API returns partial results from large orgAdd --paginate to glab api calls; default per_page=20 silently truncates
glab ci trace hangs on long-running jobUse Ctrl-C to interrupt; trace resumes from the current position on next run
CI_JOB_TOKEN in GitLab CI pipeline returns 403CI_JOB_TOKEN has restricted scope — cannot manage variables or most project API endpoints; use a PAT stored as a masked CI variable instead
Project access token vs. PAT confusionProject access tokens are scoped to one project, created under Settings > Access Tokens (not user settings); PATs work across projects. glab auth login supports both, but project access tokens cannot be used for user-level API calls like glab api user.

Reference

Version notice: This reference was verified against glab 1.105.0. Flags such as --device (auth), --use-keyring, and pipeline input flags (-i) were added in recent releases. On older glab versions, run glab <command> --help to confirm flag availability before use. glab version shows your installed version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free