agentleFS
Sign inStart free
OpenHandsOpenHands/extensions/skills/gitlab/SKILL.md

gitlab

Skill167 starsChanged 16 days agoMITView on GitHub

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.

  • Commits and pushes

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    ALWAYS use the GitLab API for operations instead of a web browser.

    line 17
  2. Very specific:

    ALWAYS use the create_mr tool to open a merge request </IMPORTANT>

    line 18
  3. Distinctive:

    If you encounter authentication issues when pushing to GitLab (such as password prompts or permission errors), the old token may have …

    line 21
  4. Distinctive:

    NEVER push directly to the main or master branch

    line 24
  5. Very specific:

    Use the create_mr tool to create a merge request, if you haven't already

    line 27
  6. Distinctive:

    Use the main branch as the base branch, unless the user requests otherwise

    line 29
  7. Distinctive:

    After opening or updating a merge request, send the user a short message with a link to the merge request.

    line 30
  8. Distinctive:

    Do all of the above in as few steps as possible.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

Connection selection

Use authenticated GitLab MCP tools first when they are available in the agent's environment. Detect this by tool availability, without depending on a particular MCP server name. Use the token and direct API instructions below only when GitLab MCP tools are unavailable or when raw API or curl access is explicitly needed.

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:
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.

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.

Reviews can't be read right now.

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