Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Wraps the `glab` CLI to interact with GitLab repositories, merge requests, CI/CD pipelines, issues, and releases. Works with gitlab.com and self-hosted instances. Supports direct API access via REST and GraphQL for operations beyond the built-in subcommands.
Combines merge request management, CI/CD inspection, and raw API access in one tool, removing the need to switch between the terminal and the GitLab web UI.
When to use it
- Reviewing and merging open MRs from the terminal
- Checking pipeline status after pushing a branch
- Tracing failed CI job logs in real time
- Creating issues with labels without opening a browser
- Querying GitLab API endpoints with custom field filters
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Why is my pipeline failing on the lint job?
- 1Run `glab ci status` to confirm the pipeline is failing
- 2Run `glab ci view` to inspect individual job statuses
- 3Run `glab ci trace lint` to stream the lint job logs
- 4Identify the error in the log output
- 5Run `glab ci retry` after the fix is pushed
Returns the lint error causing the failure and confirms the pipeline is retried
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.