How do I install the Gitlab skill?

Run npx skillmds add openhands/gitlab in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gitlab safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gitlab?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gitlab free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gitlab?

openhands (@openhands) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gitlab by openhands — Agent Skill

Name: Gitlab
Rating: 4.2 (5 reviews)
Author: openhands

File contents

You have access to an environment variable, GITLAB_TOKEN, which allows you to interact with the GitLab API.

If you encounter authentication issues when pushing to GitLab (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: git remote set-url origin https://oauth2:${GITLAB_TOKEN}@gitlab.com/username/repo.git

Here are some instructions for pushing, but ONLY do this if the user asks you to:

NEVER push directly to the main or master branch
Git config (username and email) is pre-set. Do not modify.
You may already be on a branch starting with openhands-workspace. Create a new branch with a better name before pushing.
Use the create_mr tool to create a merge request, if you haven't already
Once you've created your own branch or a merge request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
Use the main branch as the base branch, unless the user requests otherwise
After opening or updating a merge request, send the user a short message with a link to the merge request.
Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:

git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget

On Windows PowerShell, use $env:GITLAB_TOKEN in remote URLs and run the git commands as separate commands if && is not supported by the installed shell.

---name: gitlabdescription: Interact with GitLab repositories, merge requests, and APIs using the GITLAB_TOKEN environment variable. Use when working with code hosted on GitLab or managing GitLab resources.--- You have access to an environment variable, `GITLAB_TOKEN`, which allows you to interact with the GitLab API. <IMPORTANT> You can use `curl` with the `GITLAB_TOKEN` to interact with GitLab's API. ALWAYS use the GitLab API for operations instead of a web browser. ALWAYS use the `create_mr` tool to open a merge request </IMPORTANT> If you encounter authentication issues when pushing to GitLab (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: `git remote set-url origin https://oauth2:${GITLAB_TOKEN}@gitlab.com/username/repo.git` Here are some instructions for pushing, but ONLY do this if the user asks you to: * NEVER push directly to the `main` or `master` branch * Git config (username and email) is pre-set. Do not modify. * You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing. * Use the `create_mr` tool to create a merge request, if you haven't already * Once you've created your own branch or a merge request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name. * Use the main branch as the base branch, unless the user requests otherwise * After opening or updating a merge request, send the user a short message with a link to the merge request. * Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands: ```bash git remote -v && git branch # to find the current org, repo and branch git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget ``` On Windows PowerShell, use `$env:GITLAB_TOKEN` in remote URLs and run the `git` commands as separate commands if `&&` is not supported by the installed shell.

Frequently asked questions