Skip to content
TrustedSkillsbeta
Back to all skills

Gitlab

Checked
openhands·vlatest·backend·MIT

This skill integrates with GitLab for streamlined CI/CD workflows and deployment automation, boosting development efficiency.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add openhands/extensions --skill gitlab -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

openhands

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned openhands/skills at 9c140e285e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 85 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to interact with GitLab, a web-based version control system. It enables agents to perform actions such as creating merge requests, fetching commit history, and managing project repositories. The agent can automate tasks related to software development workflows within the GitLab environment.

When to use it

  • Automating code review processes by creating merge request summaries for team members.
  • Retrieving specific commit information (e.g., author, date, message) from a GitLab repository.
  • Monitoring project activity and generating reports on recent changes or contributions.
  • Creating new branches in a GitLab repository based on specified naming conventions.

Key capabilities

  • Merge request creation
  • Commit history retrieval
  • Project repository management
  • Branch creation

Example prompts

  • "Create a merge request for the 'feature/new-login' branch, targeting the main branch."
  • "What is the most recent commit message in the 'website' repository?"
  • "Generate a report of all commits made to the 'backend' project this week."

Tips & gotchas

Requires appropriate authentication credentials and permissions within your GitLab instance. The agent’s access will be limited by the user account it uses to connect to GitLab.