gitlab · acedatacloud — Claude Code skill: what it does, how to install
Teaches the agent to drive GitLab through the glab CLI: file issues, review merge requests, watch pipelines, search code.
Apache-2.0 215 installs ★ 17 updated 2026-10-25
npx skills add AceDataCloud/Skills --skill gitlab -a claude-codeWhat gitlab does
The skill hands the agent the glab command line as its way into GitLab. It reads and files issues, opens merge requests with their diffs, lists pipelines and streams job logs. Authentication comes from $GITLAB_TOKEN, which glab picks up on its own; GITLAB_ACCESS_TOKEN and OAUTH_TOKEN work too.
There are two calling styles. The native subcommands (glab issue, glab mr, glab ci, glab release, glab variable) print readable text by default and JSON once you add --output json. Anything else goes through glab api, which speaks REST and GraphQL and takes -f / -F fields, --paginate and --hostname for another instance.
A self-hosted instance needs the connection authorised against its own host, set through GITLAB_HOST or a per-command --hostname <host>. A 404 on a project you know exists usually means the request went to gitlab.com instead. Pulling one file out of a repo runs through glab api with a URL-encoded path built by jq, so that recipe fails on a machine without jq.
What it helps with
- list open issues assigned to you in a project
- approve and squash-merge a merge request
- stream the log of a failed CI job
- search a group's issues by keyword
- read a file from main without cloning the repo
Example prompts for the agent
- List open issues in
OWNER/PROJECTassigned to me as JSON - Show merge request 99 in
OWNER/PROJECTwith its diff and pipeline status - Create an issue in
OWNER/PROJECTtitled “Bug: foo” with the bug label
How to install gitlab
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill gitlab -a claude-code2Manually: put the files in place
~/.claude/skills/gitlab/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gitlab/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill gitlab -a codex2Manually: put the files in place
.agents/skills/gitlab/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill gitlab -a cursor2Manually: put the files in place
.cursor/skills/gitlab/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/gitlab2Manually: put the files in place
.github/skills/gitlab/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill gitlab -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/gitlabManually: put the files in place
.devin/skills/gitlab/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill gitlab -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 gitlab
How do I install the gitlab skill in Claude Code?
Run npx skills add AceDataCloud/Skills --skill gitlab -a claude-code. The skill file lands at ~/.claude/skills/gitlab/SKILL.md.
What does the gitlab skill do?
It gives the agent a working glab workflow for issues, merge requests, repositories, CI pipelines and code search, so it can build the right call such as glab ci view --repo OWNER/PROJECT --branch main.
Does it work with a self-hosted GitLab?
Yes. Point GITLAB_HOST at your instance or add --hostname <host> to each command; a 404 on a project that does exist usually means the connection still aims at gitlab.com.
Source text
SKILL.md · Apache-2.0
---
name: gitlab
description: GitLab issues, merge requests, repositories, CI pipelines, and code search via the glab CLI. Use when the user mentions GitLab, an MR/issue number, a project on gitlab.com, or a self-hosted GitLab instance.
when_to_use: |
Trigger when the user wants to read or write something on GitLab —
list / view / create / comment on issues or MRs, browse a project,
view CI pipelines, etc.
connections: [gitlab]
allowed_tools: [Bash]
license: Apache-2.0
metadata:
author: acedatacloud
version: "1.0"
---
Use the `glab` CLI for everything. The user's OAuth access token is
exported as `$GITLAB_TOKEN`; `glab` reads it automatically (the token
is also accepted via `GITLAB_ACCESS_TOKEN` and `OAUTH_TOKEN` for tooling
compatibility). Default host is `gitlab.com` — for self-hosted set
`GITLAB_HOST` or pass `--hostname <host>` per command.
`glab --help` and `glab <subcommand> --help` are always current.
## Two ways to call glab — prefer subcommands
### Style A: First-class subcommands — START HERE
`glab issue`, `glab mr`, `glab repo`, `glab ci`, `glab job`, `glab pipeline`,
`glab release`, `glab snippet`, `glab variable`, `glab label`,
`glab milestone`, `glab schedule`. These print formatted text by default
and JSON via `--output json`.
### Style B: Raw REST / GraphQL via `glab api`
`glab api <path>` for REST, `glab api graphql -f query='…'` for GraphQL.
Notable flags:
- `-X POST|PATCH|PUT|DELETE` — override method (default `GET`, becomes
`POST` when `--field` / `--raw-field` is set).
- `-f key=value` — magic-typed (literals `true` / `false` / `null` /
integers become JSON types, leading `@filename` reads from a file).
- `-F key=value` — same as `-f` but always treats the value as a string.
- `--paginate` — auto-walk `Link: rel="next"`.
- `--hostname <host>` — target a different GitLab host than default.
- Path placeholders: when run inside a git checkout, `:fullpath` /
`:branch` / `:user` are auto-populated from the repo. From a generic
shell, encode the path manually (see recipes).
## Recipes
### List open issues on a project
```sh
glab issue list --repo OWNER/PROJECT --opened --output json
glab issue list --repo OWNER/PROJECT --assignee=@me --output json
```
### View an issue with comments
```sh
glab issue view 42 --repo OWNER/PROJECT --comments
glab issue view 42 --repo OWNER/PROJECT --output json
```
### Create / comment / close an issue
```sh
glab issue create --repo OWNER/PROJECT --title "Bug: foo" --description "Repro steps…" --label bug
glab issue note 42 --repo OWNER/PROJECT --message "Acknowledged."
glab issue close 42 --repo OWNER/PROJECT
```
### List MRs assigned to / authored by me
```sh
glab mr list --repo OWNER/PROJECT --assignee=@me --opened --output json
glab mr list --repo OWNER/PROJECT --author=@me --opened
```
### View an MR with diff and CI pipeline
```sh
glab mr view 99 --repo OWNER/PROJECT
glab mr diff 99 --repo OWNER/PROJECT
glab ci view --repo OWNER/PROJECT --branch <BRANCH>
```
### Approve / merge / leave a note on an MR
```sh
glab mr approve 99 --repo OWNER/PROJECT
glab mr note 99 --repo OWNER/PROJECT --message "Looks good — ready when CI is green."
glab mr merge 99 --repo OWNER/PROJECT --squash --remove-source-branch
```
### Read a file from the default branch (raw bytes)
```sh
# URL-encode the project path AND the file path because both contain '/'.
PROJECT=$(printf '%s' 'OWNER/PROJECT' | jq -sRr @uri)
FILE=$(printf '%s' 'src/main.go' | jq -sRr @uri)
glab api "projects/${PROJECT}/repository/files/${FILE}/raw?ref=main"
```
### List the latest pipelines on a branch
```sh
glab ci list --repo OWNER/PROJECT --status running,success,failed
glab ci view --repo OWNER/PROJECT --branch main
glab ci trace --repo OWNER/PROJECT <JOB_ID> # stream a job log
```
### Search across a group's issues
```sh
glab api "groups/GROUP_PATH_OR_ID/issues?state=opened&search=keyword" \
--paginate \
| jq '.[] | {iid, title, project: .references.full, web_url}'
```
### GraphQL example: project metadata + open MR count
```sh
glab api graphql -f query='
query($path: ID!) {
project(fullPath: $path) {
name webUrl
mergeRequests(state: opened) { count }
}
}' -f path=OWNER/PROJECT
```
## Notes
- `--repo OWNER/PROJECT` accepts `OWNER/PROJECT`, `GROUP/SUBGROUP/PROJECT`,
full HTTPS URL, or git URL. The project path goes verbatim (no URL
encoding) for `--repo`, but does need `jq @uri` encoding when used
inside a `glab api` path.
- For self-hosted GitLab the user must have authorized the connection
with the right `host`. A 404 on a project you know exists usually
means the connection is pointing at gitlab.com when the project lives
elsewhere — surface that hint to the user.
- Many `glab` commands have an `--output` flag that takes `text` (default)
or `json`. `glab issue list` and `glab mr list` additionally have
`--output-format` (`details` / `ids` / `urls`) which is a separate,
list-only formatter. Pass the long flag `--output json` to avoid the
short-flag confusion (`-O` vs `-F`).
© acedatacloud · Apache-2.0 · AceDataCloud/Skills
Similar skills
All skills for Git and GitHub →gitlab by other authors comes first.