GitLab

!GitLab

Access GitLab via the GitLab API with OAuth authentication. Manage projects, issues, merge requests, commits, branches, pipelines, and groups.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure GitLab API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   GitLab API     │
│   (User Chat)   │     │   (OAuth)    │     │   (REST)         │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect GitLab    │                       │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │ GitLab   │
   │  File    │           │ Auth     │           │ Projects │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for GitLab again."

Quick Start

# List projects for the authenticated user
clawlink_call_tool --tool "gitlab_get_projects" --params '{}'

# Get a specific project
clawlink_call_tool --tool "gitlab_get_project" --params '{"id": "owner/repo-name"}'

# List project issues
clawlink_call_tool --tool "gitlab_list_project_issues" --params '{"id": "owner/repo-name", "state": "opened"}'

Authentication

All GitLab tool calls are authenticated automatically by ClawLink using the user's connected GitLab account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every GitLab API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=gitlab and connect GitLab.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for gitlab in the list.

Verify Connection

clawlink_list_tools --integration gitlab

Response: Returns the live tool catalog for GitLab.

Reconnect

If GitLab tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=gitlab
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration gitlab

Security & Permissions

• Access is scoped to projects and resources accessible to the connected GitLab account.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (deleting projects, archiving, removing members) are marked as high-impact and must be confirmed.
• CI/CD pipeline operations affect build and deployment systems — confirm before triggering or canceling.

Tool Reference

Projects

Groups

Issues

Merge Requests

Commits & Branches

Members

User Status

Code Examples

List project issues

clawlink_call_tool --tool "gitlab_list_project_issues" \
  --params '{
    "id": "owner/repo-name",
    "state": "opened",
    "per_page": 20
  }'

Create a new issue

clawlink_call_tool --tool "gitlab_create_project_issue" \
  --params '{
    "id": "owner/repo-name",
    "title": "Bug: Login fails on mobile",
    "description": "Steps to reproduce: 1. Go to login 2. Enter credentials 3. Error shown",
    "labels": ["bug", "priority::high"]
  }'

Create a new branch

clawlink_call_tool --tool "gitlab_create_repository_branch" \
  --params '{
    "id": "owner/repo-name",
    "branch": "feature/new-feature",
    "ref": "main"
  }'

List pipeline jobs

clawlink_call_tool --tool "gitlab_list_pipeline_jobs" \
  --params '{
    "id": "owner/repo-name",
    "pipeline_id": 123
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm GitLab is connected.
2. Call clawlink_list_tools --integration gitlab to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration gitlab.
5. If no GitLab tools appear, direct the user to https://claw-link.dev/dashboard?add=gitlab.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List issues → Get issue → Show details            │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Describe tool → Preview issue → User approves     │
│           → Execute create                                   │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• GitLab project IDs can be numeric (12345) or path-based (owner/repo-name).
• GitLab uses scoped labels (bug, priority::high) rather than simple strings.
• Merge request IIDs are different from issue IIDs — they are numbered separately.
• Pipeline status values: pending, running, success, failed, canceled, skipped.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly gitlab.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• GitLab API Documentation
• GitLab REST API
• ClawLink
• ClawLink Docs
• ClawLink Verification

Related Skills

• GitHub Repos — For GitHub repository management
• GitHub Triage — For GitHub issue triage workflows

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo