Claim this agent
Agent DossierCLAWHUBSafety 84/100

Xpersona Agent

Gitlab Cli Skills

Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Skill: Gitlab Cli Skills Owner: vince-winkintel Summary: Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Tags: latest:1.4.0 Version history: v1.4.0 | 2026-02-25T12:33:39.951Z | user Add inline comment automation for MR code reviews v1.3.0 | 2026-02-15T20:01:50.823Z | user Pipeline best practices guide, pro

OpenClaw · self-declared
2.6K downloadsTrust evidence available
clawhub skill install kn78628x1pqynfnxx2aa9gs4kd805abq:gitlab-cli-skills

Overall rank

#62

Adoption

2.6K downloads

Trust

Unknown

Freshness

Feb 28, 2026

Freshness

Last checked Feb 28, 2026

Best For

Gitlab Cli Skills is best for general automation workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

editorial-content, CLAWHUB, runtime-metrics, public facts pack

Overview

Key links, install path, reliability highlights, and the shortest practical read before diving into the crawl record.

Verifiededitorial-content

Overview

Executive Summary

Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Skill: Gitlab Cli Skills Owner: vince-winkintel Summary: Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Tags: latest:1.4.0 Version history: v1.4.0 | 2026-02-25T12:33:39.951Z | user Add inline comment automation for MR code reviews v1.3.0 | 2026-02-15T20:01:50.823Z | user Pipeline best practices guide, pro Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 4/15/2026.

No verified compatibility signals2.6K downloads

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Feb 28, 2026

Vendor

Clawhub

Artifacts

0

Benchmarks

0

Last release

1.4.0

Install & run

Setup Snapshot

clawhub skill install kn78628x1pqynfnxx2aa9gs4kd805abq:gitlab-cli-skills
  1. 1

    Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.

  2. 2

    Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Evidence & Timeline

Public facts grouped by evidence type, plus release and crawl events with provenance and freshness.

Verifiededitorial-content

Public facts

Evidence Ledger

Vendor (1)

Vendor

Clawhub

profilemedium
Observed Apr 15, 2026Source linkProvenance
Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium
Observed Apr 15, 2026Source linkProvenance
Release (1)

Latest release

1.4.0

releasemedium
Observed Feb 25, 2026Source linkProvenance
Adoption (1)

Adoption signal

2.6K downloads

profilemedium
Observed Apr 15, 2026Source linkProvenance
Security (1)

Handshake status

UNKNOWN

trustmedium
Observed unknownSource linkProvenance

Artifacts & Docs

Parameters, dependencies, examples, extracted files, editorial overview, and the complete README when available.

Self-declaredCLAWHUB

Captured outputs

Artifacts Archive

Extracted files

5

Examples

6

Snippets

0

Languages

Unknown

Executable Examples

text

Create, list, and delete aliases.                                                                                     
         
  USAGE  
         
    glab alias [command] [--flags]  
            
  COMMANDS  
            
    delete <alias name> [--flags]           Delete an alias.
    list [--flags]                          List the available aliases.
    set <alias name> '<command>' [--flags]  Set an alias for a longer command.
         
  FLAGS  
         
    -h --help                               Show help for this command.

bash

glab alias --help

text

Makes an authenticated HTTP request to the GitLab API, and prints the response.                                       
  The endpoint argument should either be a path of a GitLab API v4 endpoint, or                                         
  `graphql` to access the GitLab GraphQL API.                                                                           
                                                                                                                        
  - [GitLab REST API documentation](https://docs.gitlab.com/api/)                                                       
  - [GitLab GraphQL documentation](https://docs.gitlab.com/api/graphql/)                                                
                                                                                                                        
  If the current directory is a Git directory, uses the GitLab authenticated host in the current                        
  directory. Otherwise, `gitlab.com` will be used.                                                                      
  To override the GitLab hostname, use `--hostname`.                                                                    
                                                                                                                        
  These placeholder values, when used in the endpoint argument, are                                                     
  replaced with values from the repository of the current directory:                                                    
                                                                                                                        
  - `:branch`                                                                                                           
  - `:fullpath`                                                                                                         
  - `:group`                                                      

bash

glab api --help

text

Manage software attestations. (EXPERIMENTAL)                                                                          
         
  USAGE  
         
    glab attestation <command> [command] [--flags]                                    
            
  EXAMPLES  
            
    # Verify attestation for the filename.txt file in the gitlab-org/gitlab project.  
    $ glab attestation verify gitlab-org/gitlab filename.txt                          
                                                                                      
    # Verify attestation for the filename.txt file in the project with ID 123.        
    $ glab attestation verify 123 filename.txt                                        
            
  COMMANDS  
            
    verify <project_id> <artifact_path>  Verify the provenance of a specific artifact or file. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.

bash

glab attestation --help
Extracted Files

glab-alias/SKILL.md

---
name: glab-alias
description: Create, list, and delete GitLab CLI command aliases and shortcuts. Use when creating custom glab commands, managing CLI shortcuts, or viewing existing aliases. Triggers on alias, shortcut, custom command, CLI alias.
---

# glab alias

## Overview

```

  Create, list, and delete aliases.                                                                                     
         
  USAGE  
         
    glab alias [command] [--flags]  
            
  COMMANDS  
            
    delete <alias name> [--flags]           Delete an alias.
    list [--flags]                          List the available aliases.
    set <alias name> '<command>' [--flags]  Set an alias for a longer command.
         
  FLAGS  
         
    -h --help                               Show help for this command.
```

## Quick start

```bash
glab alias --help
```

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

glab-api/SKILL.md

---
name: glab-api
description: Make direct GitLab REST API calls for advanced queries and operations not covered by other glab commands. Use when accessing GitLab API endpoints directly, making custom API requests, or fetching data in JSON format. Triggers on API call, REST API, GitLab API, JSON query, advanced query.
---

# glab api

## Overview

```

  Makes an authenticated HTTP request to the GitLab API, and prints the response.                                       
  The endpoint argument should either be a path of a GitLab API v4 endpoint, or                                         
  `graphql` to access the GitLab GraphQL API.                                                                           
                                                                                                                        
  - [GitLab REST API documentation](https://docs.gitlab.com/api/)                                                       
  - [GitLab GraphQL documentation](https://docs.gitlab.com/api/graphql/)                                                
                                                                                                                        
  If the current directory is a Git directory, uses the GitLab authenticated host in the current                        
  directory. Otherwise, `gitlab.com` will be used.                                                                      
  To override the GitLab hostname, use `--hostname`.                                                                    
                                                                                                                        
  These placeholder values, when used in the endpoint argument, are                                                     
  replaced with values from the repository of the current directory:                                                    
                                                                                                                        
  - `:branch`                                                                                                           
  - `:fullpath`                                                                                                         
  - `:group`                                                                                                            
  - `:id`                                                                                                               
  - `:namespace`                                                                                                        
  - `:repo`                                                                                                             
  - `:user`                                                                                                             
  - `:username`                                                                                        

glab-attestation/SKILL.md

---
name: glab-attestation
description: Work with GitLab attestations for software supply chain security including artifact verification and provenance. Use when verifying software artifacts, managing attestations, or working with supply chain security. Triggers on attestation, verify artifact, provenance, supply chain security.
---

# glab attestation

## Overview

```

  Manage software attestations. (EXPERIMENTAL)                                                                          
         
  USAGE  
         
    glab attestation <command> [command] [--flags]                                    
            
  EXAMPLES  
            
    # Verify attestation for the filename.txt file in the gitlab-org/gitlab project.  
    $ glab attestation verify gitlab-org/gitlab filename.txt                          
                                                                                      
    # Verify attestation for the filename.txt file in the project with ID 123.        
    $ glab attestation verify 123 filename.txt                                        
            
  COMMANDS  
            
    verify <project_id> <artifact_path>  Verify the provenance of a specific artifact or file. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.
```

## Quick start

```bash
glab attestation --help
```

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

glab-auth/SKILL.md

---
name: glab-auth
description: Manage GitLab CLI authentication including login/logout, check auth status, switch accounts, and configure Docker registry access. Use when setting up glab for first time, troubleshooting auth issues, switching GitLab instances/accounts, or configuring Docker to pull from GitLab registry. Triggers on auth, login, logout, authentication, credentials, token, Docker registry.
---

# glab auth

Manage GitLab CLI authentication.

## Quick start

```bash
# Interactive login
glab auth login

# Check current auth status
glab auth status

# Login to different instance
glab auth login --hostname gitlab.company.com

# Logout
glab auth logout
```

## Workflows

### First-time setup

1. Run `glab auth login`
2. Choose authentication method (token or browser)
3. Follow prompts for your GitLab instance
4. Verify with `glab auth status`

### Switching accounts/instances

1. **Logout from current:**
   ```bash
   glab auth logout
   ```

2. **Login to new instance:**
   ```bash
   glab auth login --hostname gitlab.company.com
   ```

3. **Verify:**
   ```bash
   glab auth status
   ```

### Docker registry access

1. **Configure Docker helper:**
   ```bash
   glab auth configure-docker
   ```

2. **Verify Docker can authenticate:**
   ```bash
   docker login registry.gitlab.com
   ```

3. **Pull private images:**
   ```bash
   docker pull registry.gitlab.com/group/project/image:tag
   ```

## Troubleshooting

**"401 Unauthorized" errors:**
- Check status: `glab auth status`
- Verify token hasn't expired (check GitLab settings)
- Re-authenticate: `glab auth login`

**Multiple instances:**
- Use `--hostname` flag to specify instance
- Each instance maintains separate auth

**Docker authentication fails:**
- Re-run: `glab auth configure-docker`
- Check Docker config: `cat ~/.docker/config.json`
- Verify helper is set: `"credHelpers": { "registry.gitlab.com": "glab-cli" }`

## Subcommands

See [references/commands.md](references/commands.md) for detailed flag documentation:
- `login` - Authenticate with GitLab instance
- `logout` - Log out of GitLab instance
- `status` - View authentication status
- `configure-docker` - Configure Docker to use GitLab registry
- `docker-helper` - Docker credential helper
- `dpop-gen` - Generate DPoP token

## Related Skills

**Initial setup:**
- After authentication, see `glab-config` to set CLI defaults
- See `glab-ssh-key` for SSH key management
- See `glab-gpg-key` for commit signing setup

**Repository operations:**
- See `glab-repo` for cloning repositories
- Authentication required before first clone/push

glab-changelog/SKILL.md

---
name: glab-changelog
description: Generate changelogs from GitLab releases, tags, and commits. Use when creating release notes, generating changelog files, or documenting version history. Triggers on changelog, release notes, version history, generate changelog.
---

# glab changelog

## Overview

```

  Interact with the changelog API.                                                                                      
         
  USAGE  
         
    glab changelog <command> [command] [--flags]  
            
  COMMANDS  
            
    generate [--flags]  Generate a changelog for the repository or project.
         
  FLAGS  
         
    -h --help           Show help for this command.
```

## Quick start

```bash
glab changelog --help
```

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

Editorial read

Docs & README

Docs source

CLAWHUB

Editorial quality

ready

Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Skill: Gitlab Cli Skills Owner: vince-winkintel Summary: Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git... Tags: latest:1.4.0 Version history: v1.4.0 | 2026-02-25T12:33:39.951Z | user Add inline comment automation for MR code reviews v1.3.0 | 2026-02-15T20:01:50.823Z | user Pipeline best practices guide, pro

Full README

Skill: Gitlab Cli Skills

Owner: vince-winkintel

Summary: Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, Git...

Tags: latest:1.4.0

Version history:

v1.4.0 | 2026-02-25T12:33:39.951Z | user

Add inline comment automation for MR code reviews

v1.3.0 | 2026-02-15T20:01:50.823Z | user

Pipeline best practices guide, production-ready templates (nodejs-basic, nodejs-multistage, docker-build), enhanced troubleshooting with config-specific issues and performance optimization workflow. Comprehensive 12KB best practices covering caching, multi-stage patterns, coverage, security, performance. Templates README with usage, customization, troubleshooting. Expanded SKILL.md with Pipeline Configuration section and cross-links. 6 files, 1,428 lines added. Score: 9.8/10. Inspired by ClawHub competitive analysis.

v1.2.2 | 2026-02-13T14:33:13.673Z | user

Fixed glab-mcp description: 'Managed Cluster Platform' → 'Model Context Protocol' (AI assistant integration server). Updated help output to match glab 1.85.0.

v1.2.1 | 2026-02-13T05:45:26.781Z | user

Fixed ClawHub security flag by adding requirements metadata (glab binary, auth requirements, sensitive file access notes)

v1.2.0 | 2026-02-12T17:11:36.952Z | user

Added glab-runner-controller sub-skill for glab v1.83.0: 8 commands for managing runner controllers and tokens (EXPERIMENTAL, admin-only feature)

v1.1.0 | 2026-02-12T05:26:15.313Z | auto

Major update: Expanded documentation, workflows, and scripts for GitLab CLI (glab) usage.

  • SKILL.md now offers detailed usage examples, decision trees, workflow guides, and clarifies when to use glab versus the web UI.
  • New utility scripts added for common automation tasks: batch labeling issues, CI/CD debugging, MR/issue workflow automation, MR review, and fork syncing.
  • Improved documentation and references for all glab sub-skills; clearer descriptions of when each is applicable.
  • Removed outdated notes and best practice files.
  • Enhanced onboarding section for quick CLI start and practical daily development flows.

v1.0.4 | 2026-02-10T04:14:49.114Z | user

Fixed GraphQL formatting in glab-api examples (republish)

v1.0.3 | 2026-02-10T04:10:07.429Z | user

Fixed GraphQL formatting in glab-api examples

v1.0.2 | 2026-02-01T22:25:27.873Z | auto

  • Added a new SKILL.md file describing gitlab-cli-skills and the available glab-* sub-skills.
  • Clearly listed all supported GitLab CLI capabilities routed through this skill.
  • Improved documentation for easier understanding and navigation.

Archive index:

Archive v1.4.0: 81 files, 111939 bytes

Files: glab-alias/references/commands.md (5208b), glab-alias/SKILL.md (975b), glab-api/SKILL.md (10118b), glab-attestation/references/commands.md (3321b), glab-attestation/SKILL.md (1487b), glab-auth/references/commands.md (5460b), glab-auth/SKILL.md (2603b), glab-changelog/references/commands.md (1756b), glab-changelog/SKILL.md (858b), glab-check-update/SKILL.md (1618b), glab-ci/references/commands.md (28770b), glab-ci/references/pipeline-best-practices.md (12712b), glab-ci/SKILL.md (7057b), glab-ci/templates/docker-build.yml (2891b), glab-ci/templates/nodejs-basic.yml (1417b), glab-ci/templates/nodejs-multistage.yml (2613b), glab-ci/templates/README.md (6494b), glab-cluster/references/commands.md (2298b), glab-cluster/SKILL.md (1159b), glab-completion/SKILL.md (11172b), glab-config/references/commands.md (6538b), glab-config/SKILL.md (3144b), glab-deploy-key/references/commands.md (4496b), glab-deploy-key/SKILL.md (1289b), glab-duo/references/commands.md (4181b), glab-duo/SKILL.md (1447b), glab-gpg-key/references/commands.md (3362b), glab-gpg-key/SKILL.md (1193b), glab-help/SKILL.md (743b), glab-incident/references/commands.md (8321b), glab-incident/SKILL.md (1513b), glab-issue/references/commands.md (13958b), glab-issue/SKILL.md (3515b), glab-iteration/references/commands.md (1469b), glab-iteration/SKILL.md (963b), glab-job/references/commands.md (1467b), glab-job/SKILL.md (3012b), glab-label/references/commands.md (4618b), glab-label/SKILL.md (3142b), glab-mcp/references/commands.md (5743b), glab-mcp/SKILL.md (2256b), glab-milestone/references/commands.md (8441b), glab-milestone/SKILL.md (1277b), glab-mr/references/commands.md (30273b), glab-mr/SKILL.md (3780b), glab-opentofu/references/commands.md (3179b), glab-opentofu/SKILL.md (1129b), glab-release/references/commands.md (18509b), glab-release/SKILL.md (1557b), glab-repo/references/commands.md (31299b), glab-repo/SKILL.md (5059b), glab-runner-controller/references/commands.md (6888b), glab-runner-controller/SKILL.md (6036b), glab-schedule/references/commands.md (5683b), glab-schedule/SKILL.md (1266b), glab-securefile/references/commands.md (9622b), glab-securefile/SKILL.md (1866b), glab-snippet/references/commands.md (3696b), glab-snippet/SKILL.md (1437b), glab-ssh-key/references/commands.md (5062b), glab-ssh-key/SKILL.md (1252b), glab-stack/references/commands.md (20092b), glab-stack/SKILL.md (3049b), glab-token/references/commands.md (15910b), glab-token/SKILL.md (1281b), glab-user/references/commands.md (923b), glab-user/SKILL.md (799b), glab-variable/references/commands.md (8450b), glab-variable/SKILL.md (1475b), glab-version/SKILL.md (630b), README.md (2239b), scripts/add-inline-comment.sh (4723b), scripts/batch-label-issues.sh (1353b), scripts/ci-debug.sh (2164b), scripts/create-mr-from-issue.sh (1644b), scripts/mr-review-workflow.sh (1037b), scripts/README-inline-comments.md (8045b), scripts/README.md (3853b), scripts/sync-fork.sh (2180b), SKILL.md (7826b)

File v1.4.0:glab-alias/SKILL.md


name: glab-alias description: Create, list, and delete GitLab CLI command aliases and shortcuts. Use when creating custom glab commands, managing CLI shortcuts, or viewing existing aliases. Triggers on alias, shortcut, custom command, CLI alias.

glab alias

Overview


  Create, list, and delete aliases.                                                                                     
         
  USAGE  
         
    glab alias [command] [--flags]  
            
  COMMANDS  
            
    delete <alias name> [--flags]           Delete an alias.
    list [--flags]                          List the available aliases.
    set <alias name> '<command>' [--flags]  Set an alias for a longer command.
         
  FLAGS  
         
    -h --help                               Show help for this command.

Quick start

glab alias --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-api/SKILL.md


name: glab-api description: Make direct GitLab REST API calls for advanced queries and operations not covered by other glab commands. Use when accessing GitLab API endpoints directly, making custom API requests, or fetching data in JSON format. Triggers on API call, REST API, GitLab API, JSON query, advanced query.

glab api

Overview


  Makes an authenticated HTTP request to the GitLab API, and prints the response.                                       
  The endpoint argument should either be a path of a GitLab API v4 endpoint, or                                         
  `graphql` to access the GitLab GraphQL API.                                                                           
                                                                                                                        
  - [GitLab REST API documentation](https://docs.gitlab.com/api/)                                                       
  - [GitLab GraphQL documentation](https://docs.gitlab.com/api/graphql/)                                                
                                                                                                                        
  If the current directory is a Git directory, uses the GitLab authenticated host in the current                        
  directory. Otherwise, `gitlab.com` will be used.                                                                      
  To override the GitLab hostname, use `--hostname`.                                                                    
                                                                                                                        
  These placeholder values, when used in the endpoint argument, are                                                     
  replaced with values from the repository of the current directory:                                                    
                                                                                                                        
  - `:branch`                                                                                                           
  - `:fullpath`                                                                                                         
  - `:group`                                                                                                            
  - `:id`                                                                                                               
  - `:namespace`                                                                                                        
  - `:repo`                                                                                                             
  - `:user`                                                                                                             
  - `:username`                                                                                                         
                                                                                                                        
  Methods: the default HTTP request method is `GET`, if no parameters are added,                                        
  and `POST` otherwise. Override the method with `--method`.                                                            
                                                                                                                        
  Pass one or more `--raw-field` values in `key=value` format to add                                                    
  JSON-encoded string parameters to the `POST` body.                                                                    
                                                                                                                        
  The `--field` flag behaves like `--raw-field` with magic type conversion based                                        
  on the format of the value:                                                                                           
                                                                                                                        
  - Literal values `true`, `false`, `null`, and integer numbers are converted to                                        
    appropriate JSON types.                                                                                             
  - Placeholder values `:namespace`, `:repo`, and `:branch` are populated with values                                   
    from the repository of the current directory.                                                                       
  - If the value starts with `@`, the rest of the value is interpreted as a                                             
    filename to read the value from. Pass `-` to read from standard input.                                              
                                                                                                                        
  For GraphQL requests, all fields other than `query` and `operationName` are                                           
  interpreted as GraphQL variables.                                                                                     
                                                                                                                        
  Raw request body can be passed from the outside via a file specified by `--input`.                                    
  Pass `-` to read from standard input. In this mode, parameters specified with                                         
  `--field` flags are serialized into URL query parameters.                                                             
                                                                                                                        
  In `--paginate` mode, all pages of results are requested sequentially until                                           
  no more pages of results remain. For GraphQL requests:                                                                
                                                                                                                        
  - The original query must accept an `$endCursor: String` variable.                                                    
  - The query must fetch the `pageInfo{ hasNextPage, endCursor }` set of fields from a collection.                      
                                                                                                                        
  The `--output` flag controls the output format:                                                                       
                                                                                                                        
  - `json` (default): Pretty-printed JSON. Arrays are output as a single JSON array.                                    
  - `ndjson`: Newline-delimited JSON (also known as JSONL or JSON Lines). Each array element                            
    or object is output on a separate line. This format is more memory-efficient for large datasets                     
    and works well with tools like `jq`. See https://github.com/ndjson/ndjson-spec and                                  
    https://jsonlines.org/ for format specifications.                                                                   
                                                                                                                        
         
  USAGE  
         
    glab api <endpoint> [--flags]                                                   
            
  EXAMPLES  
            
    $ glab api projects/:fullpath/releases                                          
    $ glab api projects/gitlab-com%2Fwww-gitlab-com/issues                          
    $ glab api issues --paginate                                                    
    $ glab api issues --paginate --output ndjson                                    
    $ glab api issues --paginate --output ndjson | jq 'select(.state == "opened")'  
    $ glab api graphql -f query="query { currentUser { username } }"                
    $ glab api graphql -f query='
    query {
      project(fullPath: "gitlab-org/gitlab-docs") {
        name
        forksCount
        statistics {
          wikiSize
        }
        issuesEnabled
        boards {
          nodes {
            id
            name
          }
        }
      }
    }
    '                                                                               
                                                                                    
    $ glab api graphql --paginate -f query='
    query($endCursor: String) {
      project(fullPath: "gitlab-org/graphql-sandbox") {
        name
        issues(first: 2, after: $endCursor) {
          edges {
            node {
              title
            }
          }
          pageInfo {
            endCursor
            hasNextPage
          }
        }
      }
    }
    '                                                                              
         
  FLAGS  
         
    -F --field      Add a parameter of inferred type. Changes the default HTTP method to "POST".
    -H --header     Add an additional HTTP request header.
    -h --help       Show help for this command.
    --hostname      The GitLab hostname for the request. Defaults to 'gitlab.com', or the authenticated host in the current Git directory.
    -i --include    Include HTTP response headers in the output.
    --input         The file to use as the body for the HTTP request.
    -X --method     The HTTP method for the request. (GET)
    --output        Format output as: json, ndjson. (json)
    --paginate      Make additional HTTP requests to fetch all pages of results.
    -f --raw-field  Add a string parameter.
    --silent        Do not print the response body.

Quick start

glab api --help

Subcommands

This command has no subcommands.

File v1.4.0:glab-attestation/SKILL.md


name: glab-attestation description: Work with GitLab attestations for software supply chain security including artifact verification and provenance. Use when verifying software artifacts, managing attestations, or working with supply chain security. Triggers on attestation, verify artifact, provenance, supply chain security.

glab attestation

Overview


  Manage software attestations. (EXPERIMENTAL)                                                                          
         
  USAGE  
         
    glab attestation <command> [command] [--flags]                                    
            
  EXAMPLES  
            
    # Verify attestation for the filename.txt file in the gitlab-org/gitlab project.  
    $ glab attestation verify gitlab-org/gitlab filename.txt                          
                                                                                      
    # Verify attestation for the filename.txt file in the project with ID 123.        
    $ glab attestation verify 123 filename.txt                                        
            
  COMMANDS  
            
    verify <project_id> <artifact_path>  Verify the provenance of a specific artifact or file. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.

Quick start

glab attestation --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-auth/SKILL.md


name: glab-auth description: Manage GitLab CLI authentication including login/logout, check auth status, switch accounts, and configure Docker registry access. Use when setting up glab for first time, troubleshooting auth issues, switching GitLab instances/accounts, or configuring Docker to pull from GitLab registry. Triggers on auth, login, logout, authentication, credentials, token, Docker registry.

glab auth

Manage GitLab CLI authentication.

Quick start

# Interactive login
glab auth login

# Check current auth status
glab auth status

# Login to different instance
glab auth login --hostname gitlab.company.com

# Logout
glab auth logout

Workflows

First-time setup

  1. Run glab auth login
  2. Choose authentication method (token or browser)
  3. Follow prompts for your GitLab instance
  4. Verify with glab auth status

Switching accounts/instances

  1. Logout from current:

    glab auth logout
    
  2. Login to new instance:

    glab auth login --hostname gitlab.company.com
    
  3. Verify:

    glab auth status
    

Docker registry access

  1. Configure Docker helper:

    glab auth configure-docker
    
  2. Verify Docker can authenticate:

    docker login registry.gitlab.com
    
  3. Pull private images:

    docker pull registry.gitlab.com/group/project/image:tag
    

Troubleshooting

"401 Unauthorized" errors:

  • Check status: glab auth status
  • Verify token hasn't expired (check GitLab settings)
  • Re-authenticate: glab auth login

Multiple instances:

  • Use --hostname flag to specify instance
  • Each instance maintains separate auth

Docker authentication fails:

  • Re-run: glab auth configure-docker
  • Check Docker config: cat ~/.docker/config.json
  • Verify helper is set: "credHelpers": { "registry.gitlab.com": "glab-cli" }

Subcommands

See references/commands.md for detailed flag documentation:

  • login - Authenticate with GitLab instance
  • logout - Log out of GitLab instance
  • status - View authentication status
  • configure-docker - Configure Docker to use GitLab registry
  • docker-helper - Docker credential helper
  • dpop-gen - Generate DPoP token

Related Skills

Initial setup:

  • After authentication, see glab-config to set CLI defaults
  • See glab-ssh-key for SSH key management
  • See glab-gpg-key for commit signing setup

Repository operations:

  • See glab-repo for cloning repositories
  • Authentication required before first clone/push

File v1.4.0:glab-changelog/SKILL.md


name: glab-changelog description: Generate changelogs from GitLab releases, tags, and commits. Use when creating release notes, generating changelog files, or documenting version history. Triggers on changelog, release notes, version history, generate changelog.

glab changelog

Overview


  Interact with the changelog API.                                                                                      
         
  USAGE  
         
    glab changelog <command> [command] [--flags]  
            
  COMMANDS  
            
    generate [--flags]  Generate a changelog for the repository or project.
         
  FLAGS  
         
    -h --help           Show help for this command.

Quick start

glab changelog --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-check-update/SKILL.md


name: glab-check-update description: Check for glab CLI updates and view latest version information. Use when checking if glab is up to date or finding available updates. Triggers on update glab, check version, glab version, CLI update.

glab check-update

Overview


  Checks for the latest version of glab available on GitLab.com.                                                        
                                                                                                                        
  When run explicitly, this command always checks for updates regardless of when the last check occurred.               
                                                                                                                        
  When run automatically after other glab commands, it checks for updates at most once every 24 hours.                  
                                                                                                                        
  To disable the automatic update check entirely, run 'glab config set check_update false'.                             
  To re-enable the automatic update check, run 'glab config set check_update true'.                                     
                                                                                                                        
         
  USAGE  
         
    glab check-update [--flags]  
         
  FLAGS  
         
    -h --help  Show help for this command.

Quick start

glab check-update --help

Subcommands

This command has no subcommands.

File v1.4.0:glab-ci/SKILL.md


name: glab-ci description: Work with GitLab CI/CD pipelines, jobs, and artifacts. Use when checking pipeline status, viewing job logs, debugging CI failures, triggering manual jobs, downloading artifacts, validating .gitlab-ci.yml, or managing pipeline runs. Triggers on pipeline, CI/CD, job, build, deployment, artifact, pipeline status, failed build, CI logs.

glab ci

Work with GitLab CI/CD pipelines, jobs, and artifacts.

Quick start

# View current pipeline status
glab ci status

# View detailed pipeline info
glab ci view

# Watch job logs in real-time
glab ci trace <job-id>

# Download artifacts
glab ci artifact main build-job

# Validate CI config
glab ci lint

Pipeline Configuration

Getting started with .gitlab-ci.yml

Use ready-made templates:

See templates/ for production-ready pipeline configurations:

  • nodejs-basic.yml - Simple Node.js CI/CD
  • nodejs-multistage.yml - Multi-environment deployments
  • docker-build.yml - Container builds and deployments

Validate templates before using:

glab ci lint --path templates/nodejs-basic.yml

Best practices guide:

For detailed configuration guidance, see references/pipeline-best-practices.md:

  • Caching strategies
  • Multi-stage pipeline patterns
  • Coverage reporting integration
  • Security scanning
  • Performance optimization
  • Environment-specific configurations

Common workflows

Debugging pipeline failures

  1. Check pipeline status:

    glab ci status
    
  2. View failed jobs:

    glab ci view --web  # Opens in browser for visual review
    
  3. Get logs for failed job:

    # Find job ID from ci view output
    glab ci trace 12345678
    
  4. Retry failed job:

    glab ci retry 12345678
    

Automated debugging:

For quick failure diagnosis, use the debug script:

scripts/ci-debug.sh 987654

This automatically: finds all failed jobs → shows logs → suggests next steps.

Working with manual jobs

  1. View pipeline with manual jobs:

    glab ci view
    
  2. Trigger manual job:

    glab ci trigger <job-id>
    

Artifact management

Download build artifacts:

glab ci artifact main build-job

Download from specific pipeline:

glab ci artifact main build-job --pipeline-id 987654

CI configuration

Validate before pushing:

glab ci lint

Validate specific file:

glab ci lint --path .gitlab-ci-custom.yml

Pipeline operations

List recent pipelines:

glab ci list --per-page 20

Run new pipeline:

glab ci run

Run with variables:

glab ci run --variables KEY1=value1 --variables KEY2=value2

Cancel running pipeline:

glab ci cancel <pipeline-id>

Delete old pipeline:

glab ci delete <pipeline-id>

Troubleshooting

Runtime Issues

Pipeline stuck/pending:

  • Check runner availability: View pipeline in web UI
  • Check job logs: glab ci trace <job-id>
  • Cancel and retry: glab ci cancel <id> then glab ci run

Job failures:

  • View logs: glab ci trace <job-id>
  • Check artifact uploads: Verify paths in job output
  • Validate config: glab ci lint

Configuration Issues

Cache not working:

# Verify cache key matches lockfile
cache:
  key:
    files:
      - package-lock.json  # Must match actual file name

# Check cache paths are created by jobs
cache:
  paths:
    - node_modules/  # Verify this directory exists after install

Jobs running in wrong order:

# Add explicit dependencies with 'needs'
build:
  needs: [lint, test]  # Waits for both to complete
  script:
    - npm run build

Slow builds:

  1. Check cache configuration (see pipeline-best-practices.md)
  2. Parallelize independent jobs:
    lint:eslint:
      script: npm run lint:eslint
    lint:prettier:
      script: npm run lint:prettier
    
  3. Use smaller Docker images (node:20-alpine vs node:20)
  4. Optimize artifact sizes (exclude unnecessary files)

Artifacts not available in later stages:

build:
  artifacts:
    paths:
      - dist/
    expire_in: 1 hour  # Extend if later jobs run after expiry

deploy:
  needs:
    - job: build
      artifacts: true  # Explicitly download artifacts

Coverage not showing in MR:

test:
  script:
    - npm test -- --coverage
  coverage: '/Lines\s*:\s*(\d+\.\d+)%/'  # Regex must match output
  artifacts:
    reports:
      coverage_report:
        coverage_format: cobertura
        path: coverage/cobertura-coverage.xml

Performance Optimization Workflow

1. Identify slow pipelines:

glab ci list --per-page 20

2. Analyze job duration:

glab ci view --web  # Visual timeline shows bottlenecks

3. Common optimizations:

  • Parallelize: Run independent jobs simultaneously
  • Cache aggressively: Cache dependencies, build outputs
  • Fail fast: Run quick checks (lint) before slow ones (build)
  • Optimize Docker layers: Use multi-stage builds, smaller base images
  • Reduce artifact size: Exclude source maps, test files

4. Validate improvements:

# Compare pipeline duration before/after
glab ci list --per-page 5

See also: pipeline-best-practices.md for detailed optimization strategies.

Related Skills

Job-specific operations:

  • See glab-job for individual job commands (list, view, retry, cancel)
  • Use glab-ci for pipeline-level, glab-job for job-level

Pipeline triggers and schedules:

  • See glab-schedule for scheduled pipeline automation
  • See glab-variable for managing CI/CD variables

MR integration:

  • See glab-mr for merge operations
  • Use glab mr merge --when-pipeline-succeeds for CI-gated merges

Automation:

  • Script: scripts/ci-debug.sh for quick failure diagnosis

Configuration Resources:

Command reference

For complete command documentation and all flags, see references/commands.md.

Available commands:

  • status - View pipeline status for current branch
  • view - View detailed pipeline info
  • list - List recent pipelines
  • trace - View job logs (real-time or completed)
  • run - Create/run new pipeline
  • retry - Retry failed job
  • cancel - Cancel running pipeline/job
  • delete - Delete pipeline
  • trigger - Trigger manual job
  • artifact - Download job artifacts
  • lint - Validate .gitlab-ci.yml
  • config - Work with CI/CD configuration
  • get - Get JSON of pipeline
  • run-trig - Run pipeline trigger

File v1.4.0:glab-cluster/SKILL.md


name: glab-cluster description: Manage GitLab Kubernetes clusters and agent integrations. Use when connecting clusters, managing cluster agents, or working with Kubernetes integration. Triggers on cluster, Kubernetes, k8s, cluster agent, connect cluster.

glab cluster

Overview


  Manage GitLab Agents for Kubernetes and their clusters.                                                               
         
  USAGE  
         
    glab cluster <command> [command] [--flags]  
            
  COMMANDS  
            
    agent <command> [command] [--flags]  Manage GitLab Agents for Kubernetes.
    graph [--flags]                      Queries the Kubernetes object graph, using the GitLab Agent for Kubernetes. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.
    -R --repo                            Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.

Quick start

glab cluster --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-completion/SKILL.md


name: glab-completion description: Generate shell completion scripts for bash, zsh, fish, or PowerShell. Use when setting up glab autocompletion for your shell. Triggers on completion, autocomplete, shell completion, tab completion.

glab completion

Overview


  This command outputs code meant to be saved to a file, or immediately                                                 
  evaluated by an interactive shell. To load completions:                                                               
                                                                                                                        
  ### Bash                                                                                                              
                                                                                                                        
  To load completions in your current shell session:                                                                    
                                                                                                                        
  ```shell                                                                                                              
  source <(glab completion -s bash)                                                                                     

To load completions for every new session, run this command one time:

Linux

glab completion -s bash > /etc/bash_completion.d/glab                                                                 

macOS

glab completion -s bash > /usr/local/etc/bash_completion.d/glab                                                       

Zsh

If shell completion is not already enabled in your environment you must
enable it. Run this command one time:

echo "autoload -U compinit; compinit" >> ~/.zshrc                                                                     

To load completions in your current shell session:

source <(glab completion -s zsh); compdef _glab glab                                                                  

To load completions for every new session, run this command one time:

Linux

glab completion -s zsh > "${fpath[1]}/_glab"                                                                          

macOS

For older versions of macOS, you might need this command:

glab completion -s zsh > /usr/local/share/zsh/site-functions/_glab                                                    

The Homebrew version of glab should install completions automatically.

fish

To load completions in your current shell session:

glab completion -s fish | source                                                                                      

To load completions for every new session, run this command one time:

glab completion -s fish > ~/.config/fish/completions/glab.fish                                                        

PowerShell

To load completions in your current shell session:

glab completion -s powershell | Out-String | Invoke-Expression                                                        

To load completions for every new session, add the output of the above command
to your PowerShell profile.

When installing glab through a package manager, however, you might not need
more shell configuration to support completions.
For Homebrew, see brew shell completion

USAGE

glab completion [--flags]  
     

FLAGS

-h --help   Show help for this command.
--no-desc   Do not include shell completion description.
-s --shell  Shell type: bash, zsh, fish, powershell. (bash)

## Quick start

```bash
glab completion --help

Subcommands

This command has no subcommands.

File v1.4.0:glab-config/SKILL.md


name: glab-config description: Manage glab CLI configuration settings including defaults, preferences, and per-host settings. Use when configuring glab behavior, setting defaults, or viewing current configuration. Triggers on config, configuration, settings, glab settings, set default.

glab config

Overview


  Manage key/value strings.                                                                                             
                                                                                                                        
  Current respected settings:                                                                                           
                                                                                                                        
  - browser: If unset, uses the default browser. Override with environment variable $BROWSER.                           
  - check_update: If true, notifies of new versions of glab. Defaults to true. Override with environment variable       
  $GLAB_CHECK_UPDATE.                                                                                                   
  - display_hyperlinks: If true, and using a TTY, outputs hyperlinks for issues and merge request lists. Defaults to    
  false.                                                                                                                
  - editor: If unset, uses the default editor. Override with environment variable $EDITOR.                              
  - glab_pager: Your desired pager command to use, such as 'less -R'.                                                   
  - glamour_style: Your desired Markdown renderer style. Options are dark, light, notty. Custom styles are available    
  using [glamour](https://github.com/charmbracelet/glamour#styles).                                                     
  - host: If unset, defaults to `https://gitlab.com`.                                                                   
  - token: Your GitLab access token. Defaults to environment variables.                                                 
  - visual: Takes precedence over 'editor'. If unset, uses the default editor. Override with environment variable       
  $VISUAL.                                                                                                              
                                                                                                                        
         
  USAGE  
         
    glab config [command] [--flags]  
            
  COMMANDS  
            
    edit [--flags]               Opens the glab configuration file.
    get <key> [--flags]          Prints the value of a given configuration key.
    set <key> <value> [--flags]  Updates configuration with the value of a given key.
         
  FLAGS  
         
    -g --global                  Use global config file.
    -h --help                    Show help for this command.

Quick start

glab config --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-deploy-key/SKILL.md


name: glab-deploy-key description: Manage SSH deploy keys for GitLab projects including add, list, and delete operations. Use when setting up deploy keys for CI/CD, managing read-only access, or configuring deployment authentication. Triggers on deploy key, SSH key, deployment key, read-only access.

glab deploy-key

Overview


  Manage deploy keys.                                                                                                   
         
  USAGE  
         
    glab deploy-key <command> [command] [--flags]  
            
  COMMANDS  
            
    add [key-file] [--flags]  Add a deploy key to a GitLab project.
    delete <key-id>           Deletes a single deploy key specified by the ID.
    get <key-id>              Returns a single deploy key specified by the ID.
    list [--flags]            Get a list of deploy keys for the current project.
         
  FLAGS  
         
    -h --help                 Show help for this command.
    -R --repo                 Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.

Quick start

glab deploy-key --help

Subcommands

See references/commands.md for full --help output.

File v1.4.0:glab-duo/SKILL.md


name: glab-duo description: Interact with GitLab Duo AI assistant for code suggestions and chat. Use when accessing AI-powered code assistance, getting code suggestions, or chatting with GitLab Duo. Triggers on Duo, AI assistant, code suggestions, AI chat.

glab duo

Overview


  Work with GitLab Duo, our AI-native assistant for the command line.                                                   
                                                                                                                        
  GitLab Duo for the CLI integrates AI capabilities directly into your terminal                                         
  workflow. It helps you retrieve forgotten Git commands and offers guidance on                                         
  Git operations. You can accomplish specific tasks without switching contexts.                                         
                                                                                                                        
         
  USAGE  
         
    glab duo <command> prompt [command] [--flags]  
            
  COMMANDS  
            
    ask <prompt> [--flags]  Generate Git commands from natural language.
         
  FLAGS  
         
    -h --help               Show help for this command.

Quick start

glab duo --help

Subcommands

See references/commands.md for full --help output.

Archive v1.3.0: 79 files, 105993 bytes

Files: glab-alias/references/commands.md (5208b), glab-alias/SKILL.md (975b), glab-api/SKILL.md (10118b), glab-attestation/references/commands.md (3321b), glab-attestation/SKILL.md (1487b), glab-auth/references/commands.md (5460b), glab-auth/SKILL.md (2603b), glab-changelog/references/commands.md (1756b), glab-changelog/SKILL.md (858b), glab-check-update/SKILL.md (1618b), glab-ci/references/commands.md (28770b), glab-ci/references/pipeline-best-practices.md (12712b), glab-ci/SKILL.md (7057b), glab-ci/templates/docker-build.yml (2891b), glab-ci/templates/nodejs-basic.yml (1417b), glab-ci/templates/nodejs-multistage.yml (2613b), glab-ci/templates/README.md (6494b), glab-cluster/references/commands.md (2298b), glab-cluster/SKILL.md (1159b), glab-completion/SKILL.md (11172b), glab-config/references/commands.md (6538b), glab-config/SKILL.md (3144b), glab-deploy-key/references/commands.md (4496b), glab-deploy-key/SKILL.md (1289b), glab-duo/references/commands.md (4181b), glab-duo/SKILL.md (1447b), glab-gpg-key/references/commands.md (3362b), glab-gpg-key/SKILL.md (1193b), glab-help/SKILL.md (743b), glab-incident/references/commands.md (8321b), glab-incident/SKILL.md (1513b), glab-issue/references/commands.md (13958b), glab-issue/SKILL.md (3515b), glab-iteration/references/commands.md (1469b), glab-iteration/SKILL.md (963b), glab-job/references/commands.md (1467b), glab-job/SKILL.md (3012b), glab-label/references/commands.md (4618b), glab-label/SKILL.md (3142b), glab-mcp/references/commands.md (5743b), glab-mcp/SKILL.md (2256b), glab-milestone/references/commands.md (8441b), glab-milestone/SKILL.md (1277b), glab-mr/references/commands.md (30273b), glab-mr/SKILL.md (3780b), glab-opentofu/references/commands.md (3179b), glab-opentofu/SKILL.md (1129b), glab-release/references/commands.md (18509b), glab-release/SKILL.md (1557b), glab-repo/references/commands.md (31299b), glab-repo/SKILL.md (5059b), glab-runner-controller/references/commands.md (6888b), glab-runner-controller/SKILL.md (6036b), glab-schedule/references/commands.md (5683b), glab-schedule/SKILL.md (1266b), glab-securefile/references/commands.md (9622b), glab-securefile/SKILL.md (1866b), glab-snippet/references/commands.md (3696b), glab-snippet/SKILL.md (1437b), glab-ssh-key/references/commands.md (5062b), glab-ssh-key/SKILL.md (1252b), glab-stack/references/commands.md (20092b), glab-stack/SKILL.md (3049b), glab-token/references/commands.md (15910b), glab-token/SKILL.md (1281b), glab-user/references/commands.md (923b), glab-user/SKILL.md (799b), glab-variable/references/commands.md (8450b), glab-variable/SKILL.md (1475b), glab-version/SKILL.md (630b), README.md (2239b), scripts/batch-label-issues.sh (1353b), scripts/ci-debug.sh (2164b), scripts/create-mr-from-issue.sh (1644b), scripts/mr-review-workflow.sh (1037b), scripts/README.md (3139b), scripts/sync-fork.sh (2180b), SKILL.md (7826b), _meta.json (136b)

File v1.3.0:glab-alias/SKILL.md


name: glab-alias description: Create, list, and delete GitLab CLI command aliases and shortcuts. Use when creating custom glab commands, managing CLI shortcuts, or viewing existing aliases. Triggers on alias, shortcut, custom command, CLI alias.

glab alias

Overview


  Create, list, and delete aliases.                                                                                     
         
  USAGE  
         
    glab alias [command] [--flags]  
            
  COMMANDS  
            
    delete <alias name> [--flags]           Delete an alias.
    list [--flags]                          List the available aliases.
    set <alias name> '<command>' [--flags]  Set an alias for a longer command.
         
  FLAGS  
         
    -h --help                               Show help for this command.

Quick start

glab alias --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-api/SKILL.md


name: glab-api description: Make direct GitLab REST API calls for advanced queries and operations not covered by other glab commands. Use when accessing GitLab API endpoints directly, making custom API requests, or fetching data in JSON format. Triggers on API call, REST API, GitLab API, JSON query, advanced query.

glab api

Overview


  Makes an authenticated HTTP request to the GitLab API, and prints the response.                                       
  The endpoint argument should either be a path of a GitLab API v4 endpoint, or                                         
  `graphql` to access the GitLab GraphQL API.                                                                           
                                                                                                                        
  - [GitLab REST API documentation](https://docs.gitlab.com/api/)                                                       
  - [GitLab GraphQL documentation](https://docs.gitlab.com/api/graphql/)                                                
                                                                                                                        
  If the current directory is a Git directory, uses the GitLab authenticated host in the current                        
  directory. Otherwise, `gitlab.com` will be used.                                                                      
  To override the GitLab hostname, use `--hostname`.                                                                    
                                                                                                                        
  These placeholder values, when used in the endpoint argument, are                                                     
  replaced with values from the repository of the current directory:                                                    
                                                                                                                        
  - `:branch`                                                                                                           
  - `:fullpath`                                                                                                         
  - `:group`                                                                                                            
  - `:id`                                                                                                               
  - `:namespace`                                                                                                        
  - `:repo`                                                                                                             
  - `:user`                                                                                                             
  - `:username`                                                                                                         
                                                                                                                        
  Methods: the default HTTP request method is `GET`, if no parameters are added,                                        
  and `POST` otherwise. Override the method with `--method`.                                                            
                                                                                                                        
  Pass one or more `--raw-field` values in `key=value` format to add                                                    
  JSON-encoded string parameters to the `POST` body.                                                                    
                                                                                                                        
  The `--field` flag behaves like `--raw-field` with magic type conversion based                                        
  on the format of the value:                                                                                           
                                                                                                                        
  - Literal values `true`, `false`, `null`, and integer numbers are converted to                                        
    appropriate JSON types.                                                                                             
  - Placeholder values `:namespace`, `:repo`, and `:branch` are populated with values                                   
    from the repository of the current directory.                                                                       
  - If the value starts with `@`, the rest of the value is interpreted as a                                             
    filename to read the value from. Pass `-` to read from standard input.                                              
                                                                                                                        
  For GraphQL requests, all fields other than `query` and `operationName` are                                           
  interpreted as GraphQL variables.                                                                                     
                                                                                                                        
  Raw request body can be passed from the outside via a file specified by `--input`.                                    
  Pass `-` to read from standard input. In this mode, parameters specified with                                         
  `--field` flags are serialized into URL query parameters.                                                             
                                                                                                                        
  In `--paginate` mode, all pages of results are requested sequentially until                                           
  no more pages of results remain. For GraphQL requests:                                                                
                                                                                                                        
  - The original query must accept an `$endCursor: String` variable.                                                    
  - The query must fetch the `pageInfo{ hasNextPage, endCursor }` set of fields from a collection.                      
                                                                                                                        
  The `--output` flag controls the output format:                                                                       
                                                                                                                        
  - `json` (default): Pretty-printed JSON. Arrays are output as a single JSON array.                                    
  - `ndjson`: Newline-delimited JSON (also known as JSONL or JSON Lines). Each array element                            
    or object is output on a separate line. This format is more memory-efficient for large datasets                     
    and works well with tools like `jq`. See https://github.com/ndjson/ndjson-spec and                                  
    https://jsonlines.org/ for format specifications.                                                                   
                                                                                                                        
         
  USAGE  
         
    glab api <endpoint> [--flags]                                                   
            
  EXAMPLES  
            
    $ glab api projects/:fullpath/releases                                          
    $ glab api projects/gitlab-com%2Fwww-gitlab-com/issues                          
    $ glab api issues --paginate                                                    
    $ glab api issues --paginate --output ndjson                                    
    $ glab api issues --paginate --output ndjson | jq 'select(.state == "opened")'  
    $ glab api graphql -f query="query { currentUser { username } }"                
    $ glab api graphql -f query='
    query {
      project(fullPath: "gitlab-org/gitlab-docs") {
        name
        forksCount
        statistics {
          wikiSize
        }
        issuesEnabled
        boards {
          nodes {
            id
            name
          }
        }
      }
    }
    '                                                                               
                                                                                    
    $ glab api graphql --paginate -f query='
    query($endCursor: String) {
      project(fullPath: "gitlab-org/graphql-sandbox") {
        name
        issues(first: 2, after: $endCursor) {
          edges {
            node {
              title
            }
          }
          pageInfo {
            endCursor
            hasNextPage
          }
        }
      }
    }
    '                                                                              
         
  FLAGS  
         
    -F --field      Add a parameter of inferred type. Changes the default HTTP method to "POST".
    -H --header     Add an additional HTTP request header.
    -h --help       Show help for this command.
    --hostname      The GitLab hostname for the request. Defaults to 'gitlab.com', or the authenticated host in the current Git directory.
    -i --include    Include HTTP response headers in the output.
    --input         The file to use as the body for the HTTP request.
    -X --method     The HTTP method for the request. (GET)
    --output        Format output as: json, ndjson. (json)
    --paginate      Make additional HTTP requests to fetch all pages of results.
    -f --raw-field  Add a string parameter.
    --silent        Do not print the response body.

Quick start

glab api --help

Subcommands

This command has no subcommands.

File v1.3.0:glab-attestation/SKILL.md


name: glab-attestation description: Work with GitLab attestations for software supply chain security including artifact verification and provenance. Use when verifying software artifacts, managing attestations, or working with supply chain security. Triggers on attestation, verify artifact, provenance, supply chain security.

glab attestation

Overview


  Manage software attestations. (EXPERIMENTAL)                                                                          
         
  USAGE  
         
    glab attestation <command> [command] [--flags]                                    
            
  EXAMPLES  
            
    # Verify attestation for the filename.txt file in the gitlab-org/gitlab project.  
    $ glab attestation verify gitlab-org/gitlab filename.txt                          
                                                                                      
    # Verify attestation for the filename.txt file in the project with ID 123.        
    $ glab attestation verify 123 filename.txt                                        
            
  COMMANDS  
            
    verify <project_id> <artifact_path>  Verify the provenance of a specific artifact or file. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.

Quick start

glab attestation --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-auth/SKILL.md


name: glab-auth description: Manage GitLab CLI authentication including login/logout, check auth status, switch accounts, and configure Docker registry access. Use when setting up glab for first time, troubleshooting auth issues, switching GitLab instances/accounts, or configuring Docker to pull from GitLab registry. Triggers on auth, login, logout, authentication, credentials, token, Docker registry.

glab auth

Manage GitLab CLI authentication.

Quick start

# Interactive login
glab auth login

# Check current auth status
glab auth status

# Login to different instance
glab auth login --hostname gitlab.company.com

# Logout
glab auth logout

Workflows

First-time setup

  1. Run glab auth login
  2. Choose authentication method (token or browser)
  3. Follow prompts for your GitLab instance
  4. Verify with glab auth status

Switching accounts/instances

  1. Logout from current:

    glab auth logout
    
  2. Login to new instance:

    glab auth login --hostname gitlab.company.com
    
  3. Verify:

    glab auth status
    

Docker registry access

  1. Configure Docker helper:

    glab auth configure-docker
    
  2. Verify Docker can authenticate:

    docker login registry.gitlab.com
    
  3. Pull private images:

    docker pull registry.gitlab.com/group/project/image:tag
    

Troubleshooting

"401 Unauthorized" errors:

  • Check status: glab auth status
  • Verify token hasn't expired (check GitLab settings)
  • Re-authenticate: glab auth login

Multiple instances:

  • Use --hostname flag to specify instance
  • Each instance maintains separate auth

Docker authentication fails:

  • Re-run: glab auth configure-docker
  • Check Docker config: cat ~/.docker/config.json
  • Verify helper is set: "credHelpers": { "registry.gitlab.com": "glab-cli" }

Subcommands

See references/commands.md for detailed flag documentation:

  • login - Authenticate with GitLab instance
  • logout - Log out of GitLab instance
  • status - View authentication status
  • configure-docker - Configure Docker to use GitLab registry
  • docker-helper - Docker credential helper
  • dpop-gen - Generate DPoP token

Related Skills

Initial setup:

  • After authentication, see glab-config to set CLI defaults
  • See glab-ssh-key for SSH key management
  • See glab-gpg-key for commit signing setup

Repository operations:

  • See glab-repo for cloning repositories
  • Authentication required before first clone/push

File v1.3.0:glab-changelog/SKILL.md


name: glab-changelog description: Generate changelogs from GitLab releases, tags, and commits. Use when creating release notes, generating changelog files, or documenting version history. Triggers on changelog, release notes, version history, generate changelog.

glab changelog

Overview


  Interact with the changelog API.                                                                                      
         
  USAGE  
         
    glab changelog <command> [command] [--flags]  
            
  COMMANDS  
            
    generate [--flags]  Generate a changelog for the repository or project.
         
  FLAGS  
         
    -h --help           Show help for this command.

Quick start

glab changelog --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-check-update/SKILL.md


name: glab-check-update description: Check for glab CLI updates and view latest version information. Use when checking if glab is up to date or finding available updates. Triggers on update glab, check version, glab version, CLI update.

glab check-update

Overview


  Checks for the latest version of glab available on GitLab.com.                                                        
                                                                                                                        
  When run explicitly, this command always checks for updates regardless of when the last check occurred.               
                                                                                                                        
  When run automatically after other glab commands, it checks for updates at most once every 24 hours.                  
                                                                                                                        
  To disable the automatic update check entirely, run 'glab config set check_update false'.                             
  To re-enable the automatic update check, run 'glab config set check_update true'.                                     
                                                                                                                        
         
  USAGE  
         
    glab check-update [--flags]  
         
  FLAGS  
         
    -h --help  Show help for this command.

Quick start

glab check-update --help

Subcommands

This command has no subcommands.

File v1.3.0:glab-ci/SKILL.md


name: glab-ci description: Work with GitLab CI/CD pipelines, jobs, and artifacts. Use when checking pipeline status, viewing job logs, debugging CI failures, triggering manual jobs, downloading artifacts, validating .gitlab-ci.yml, or managing pipeline runs. Triggers on pipeline, CI/CD, job, build, deployment, artifact, pipeline status, failed build, CI logs.

glab ci

Work with GitLab CI/CD pipelines, jobs, and artifacts.

Quick start

# View current pipeline status
glab ci status

# View detailed pipeline info
glab ci view

# Watch job logs in real-time
glab ci trace <job-id>

# Download artifacts
glab ci artifact main build-job

# Validate CI config
glab ci lint

Pipeline Configuration

Getting started with .gitlab-ci.yml

Use ready-made templates:

See templates/ for production-ready pipeline configurations:

  • nodejs-basic.yml - Simple Node.js CI/CD
  • nodejs-multistage.yml - Multi-environment deployments
  • docker-build.yml - Container builds and deployments

Validate templates before using:

glab ci lint --path templates/nodejs-basic.yml

Best practices guide:

For detailed configuration guidance, see references/pipeline-best-practices.md:

  • Caching strategies
  • Multi-stage pipeline patterns
  • Coverage reporting integration
  • Security scanning
  • Performance optimization
  • Environment-specific configurations

Common workflows

Debugging pipeline failures

  1. Check pipeline status:

    glab ci status
    
  2. View failed jobs:

    glab ci view --web  # Opens in browser for visual review
    
  3. Get logs for failed job:

    # Find job ID from ci view output
    glab ci trace 12345678
    
  4. Retry failed job:

    glab ci retry 12345678
    

Automated debugging:

For quick failure diagnosis, use the debug script:

scripts/ci-debug.sh 987654

This automatically: finds all failed jobs → shows logs → suggests next steps.

Working with manual jobs

  1. View pipeline with manual jobs:

    glab ci view
    
  2. Trigger manual job:

    glab ci trigger <job-id>
    

Artifact management

Download build artifacts:

glab ci artifact main build-job

Download from specific pipeline:

glab ci artifact main build-job --pipeline-id 987654

CI configuration

Validate before pushing:

glab ci lint

Validate specific file:

glab ci lint --path .gitlab-ci-custom.yml

Pipeline operations

List recent pipelines:

glab ci list --per-page 20

Run new pipeline:

glab ci run

Run with variables:

glab ci run --variables KEY1=value1 --variables KEY2=value2

Cancel running pipeline:

glab ci cancel <pipeline-id>

Delete old pipeline:

glab ci delete <pipeline-id>

Troubleshooting

Runtime Issues

Pipeline stuck/pending:

  • Check runner availability: View pipeline in web UI
  • Check job logs: glab ci trace <job-id>
  • Cancel and retry: glab ci cancel <id> then glab ci run

Job failures:

  • View logs: glab ci trace <job-id>
  • Check artifact uploads: Verify paths in job output
  • Validate config: glab ci lint

Configuration Issues

Cache not working:

# Verify cache key matches lockfile
cache:
  key:
    files:
      - package-lock.json  # Must match actual file name

# Check cache paths are created by jobs
cache:
  paths:
    - node_modules/  # Verify this directory exists after install

Jobs running in wrong order:

# Add explicit dependencies with 'needs'
build:
  needs: [lint, test]  # Waits for both to complete
  script:
    - npm run build

Slow builds:

  1. Check cache configuration (see pipeline-best-practices.md)
  2. Parallelize independent jobs:
    lint:eslint:
      script: npm run lint:eslint
    lint:prettier:
      script: npm run lint:prettier
    
  3. Use smaller Docker images (node:20-alpine vs node:20)
  4. Optimize artifact sizes (exclude unnecessary files)

Artifacts not available in later stages:

build:
  artifacts:
    paths:
      - dist/
    expire_in: 1 hour  # Extend if later jobs run after expiry

deploy:
  needs:
    - job: build
      artifacts: true  # Explicitly download artifacts

Coverage not showing in MR:

test:
  script:
    - npm test -- --coverage
  coverage: '/Lines\s*:\s*(\d+\.\d+)%/'  # Regex must match output
  artifacts:
    reports:
      coverage_report:
        coverage_format: cobertura
        path: coverage/cobertura-coverage.xml

Performance Optimization Workflow

1. Identify slow pipelines:

glab ci list --per-page 20

2. Analyze job duration:

glab ci view --web  # Visual timeline shows bottlenecks

3. Common optimizations:

  • Parallelize: Run independent jobs simultaneously
  • Cache aggressively: Cache dependencies, build outputs
  • Fail fast: Run quick checks (lint) before slow ones (build)
  • Optimize Docker layers: Use multi-stage builds, smaller base images
  • Reduce artifact size: Exclude source maps, test files

4. Validate improvements:

# Compare pipeline duration before/after
glab ci list --per-page 5

See also: pipeline-best-practices.md for detailed optimization strategies.

Related Skills

Job-specific operations:

  • See glab-job for individual job commands (list, view, retry, cancel)
  • Use glab-ci for pipeline-level, glab-job for job-level

Pipeline triggers and schedules:

  • See glab-schedule for scheduled pipeline automation
  • See glab-variable for managing CI/CD variables

MR integration:

  • See glab-mr for merge operations
  • Use glab mr merge --when-pipeline-succeeds for CI-gated merges

Automation:

  • Script: scripts/ci-debug.sh for quick failure diagnosis

Configuration Resources:

Command reference

For complete command documentation and all flags, see references/commands.md.

Available commands:

  • status - View pipeline status for current branch
  • view - View detailed pipeline info
  • list - List recent pipelines
  • trace - View job logs (real-time or completed)
  • run - Create/run new pipeline
  • retry - Retry failed job
  • cancel - Cancel running pipeline/job
  • delete - Delete pipeline
  • trigger - Trigger manual job
  • artifact - Download job artifacts
  • lint - Validate .gitlab-ci.yml
  • config - Work with CI/CD configuration
  • get - Get JSON of pipeline
  • run-trig - Run pipeline trigger

File v1.3.0:glab-cluster/SKILL.md


name: glab-cluster description: Manage GitLab Kubernetes clusters and agent integrations. Use when connecting clusters, managing cluster agents, or working with Kubernetes integration. Triggers on cluster, Kubernetes, k8s, cluster agent, connect cluster.

glab cluster

Overview


  Manage GitLab Agents for Kubernetes and their clusters.                                                               
         
  USAGE  
         
    glab cluster <command> [command] [--flags]  
            
  COMMANDS  
            
    agent <command> [command] [--flags]  Manage GitLab Agents for Kubernetes.
    graph [--flags]                      Queries the Kubernetes object graph, using the GitLab Agent for Kubernetes. (EXPERIMENTAL)
         
  FLAGS  
         
    -h --help                            Show help for this command.
    -R --repo                            Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.

Quick start

glab cluster --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-completion/SKILL.md


name: glab-completion description: Generate shell completion scripts for bash, zsh, fish, or PowerShell. Use when setting up glab autocompletion for your shell. Triggers on completion, autocomplete, shell completion, tab completion.

glab completion

Overview


  This command outputs code meant to be saved to a file, or immediately                                                 
  evaluated by an interactive shell. To load completions:                                                               
                                                                                                                        
  ### Bash                                                                                                              
                                                                                                                        
  To load completions in your current shell session:                                                                    
                                                                                                                        
  ```shell                                                                                                              
  source <(glab completion -s bash)                                                                                     

To load completions for every new session, run this command one time:

Linux

glab completion -s bash > /etc/bash_completion.d/glab                                                                 

macOS

glab completion -s bash > /usr/local/etc/bash_completion.d/glab                                                       

Zsh

If shell completion is not already enabled in your environment you must
enable it. Run this command one time:

echo "autoload -U compinit; compinit" >> ~/.zshrc                                                                     

To load completions in your current shell session:

source <(glab completion -s zsh); compdef _glab glab                                                                  

To load completions for every new session, run this command one time:

Linux

glab completion -s zsh > "${fpath[1]}/_glab"                                                                          

macOS

For older versions of macOS, you might need this command:

glab completion -s zsh > /usr/local/share/zsh/site-functions/_glab                                                    

The Homebrew version of glab should install completions automatically.

fish

To load completions in your current shell session:

glab completion -s fish | source                                                                                      

To load completions for every new session, run this command one time:

glab completion -s fish > ~/.config/fish/completions/glab.fish                                                        

PowerShell

To load completions in your current shell session:

glab completion -s powershell | Out-String | Invoke-Expression                                                        

To load completions for every new session, add the output of the above command
to your PowerShell profile.

When installing glab through a package manager, however, you might not need
more shell configuration to support completions.
For Homebrew, see brew shell completion

USAGE

glab completion [--flags]  
     

FLAGS

-h --help   Show help for this command.
--no-desc   Do not include shell completion description.
-s --shell  Shell type: bash, zsh, fish, powershell. (bash)

## Quick start

```bash
glab completion --help

Subcommands

This command has no subcommands.

File v1.3.0:glab-config/SKILL.md


name: glab-config description: Manage glab CLI configuration settings including defaults, preferences, and per-host settings. Use when configuring glab behavior, setting defaults, or viewing current configuration. Triggers on config, configuration, settings, glab settings, set default.

glab config

Overview


  Manage key/value strings.                                                                                             
                                                                                                                        
  Current respected settings:                                                                                           
                                                                                                                        
  - browser: If unset, uses the default browser. Override with environment variable $BROWSER.                           
  - check_update: If true, notifies of new versions of glab. Defaults to true. Override with environment variable       
  $GLAB_CHECK_UPDATE.                                                                                                   
  - display_hyperlinks: If true, and using a TTY, outputs hyperlinks for issues and merge request lists. Defaults to    
  false.                                                                                                                
  - editor: If unset, uses the default editor. Override with environment variable $EDITOR.                              
  - glab_pager: Your desired pager command to use, such as 'less -R'.                                                   
  - glamour_style: Your desired Markdown renderer style. Options are dark, light, notty. Custom styles are available    
  using [glamour](https://github.com/charmbracelet/glamour#styles).                                                     
  - host: If unset, defaults to `https://gitlab.com`.                                                                   
  - token: Your GitLab access token. Defaults to environment variables.                                                 
  - visual: Takes precedence over 'editor'. If unset, uses the default editor. Override with environment variable       
  $VISUAL.                                                                                                              
                                                                                                                        
         
  USAGE  
         
    glab config [command] [--flags]  
            
  COMMANDS  
            
    edit [--flags]               Opens the glab configuration file.
    get <key> [--flags]          Prints the value of a given configuration key.
    set <key> <value> [--flags]  Updates configuration with the value of a given key.
         
  FLAGS  
         
    -g --global                  Use global config file.
    -h --help                    Show help for this command.

Quick start

glab config --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-deploy-key/SKILL.md


name: glab-deploy-key description: Manage SSH deploy keys for GitLab projects including add, list, and delete operations. Use when setting up deploy keys for CI/CD, managing read-only access, or configuring deployment authentication. Triggers on deploy key, SSH key, deployment key, read-only access.

glab deploy-key

Overview


  Manage deploy keys.                                                                                                   
         
  USAGE  
         
    glab deploy-key <command> [command] [--flags]  
            
  COMMANDS  
            
    add [key-file] [--flags]  Add a deploy key to a GitLab project.
    delete <key-id>           Deletes a single deploy key specified by the ID.
    get <key-id>              Returns a single deploy key specified by the ID.
    list [--flags]            Get a list of deploy keys for the current project.
         
  FLAGS  
         
    -h --help                 Show help for this command.
    -R --repo                 Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.

Quick start

glab deploy-key --help

Subcommands

See references/commands.md for full --help output.

File v1.3.0:glab-duo/SKILL.md


name: glab-duo description: Interact with GitLab Duo AI assistant for code suggestions and chat. Use when accessing AI-powered code assistance, getting code suggestions, or chatting with GitLab Duo. Triggers on Duo, AI assistant, code suggestions, AI chat.

glab duo

Overview


  Work with GitLab Duo, our AI-native assistant for the command line.                                                   
                                                                                                                        
  GitLab Duo for the CLI integrates AI capabilities directly into your terminal                                         
  workflow. It helps you retrieve forgotten Git commands and offers guidance on                                         
  Git operations. You can accomplish specific tasks without switching contexts.                                         
                                                                                                                        
         
  USAGE  
         
    glab duo <command> prompt [command] [--flags]  
            
  COMMANDS  
            
    ask <prompt> [--flags]  Generate Git commands from natural language.
         
  FLAGS  
         
    -h --help               Show help for this command.

Quick start

glab duo --help

Subcommands

See references/commands.md for full --help output.

API & Reliability

Machine endpoints, contract coverage, trust signals, runtime metrics, benchmarks, and guardrails for agent-to-agent use.

MissingCLAWHUB

Machine interfaces

Contract & API

Contract coverage

Status

missing

Auth

None

Streaming

No

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.
Invocation examples
curl -s "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/snapshot"
curl -s "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/contract"
curl -s "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/trust"

Operational fit

Reliability & Benchmarks

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.
No benchmark suites or observed failure patterns are available.

Machine Appendix

Raw contract, invocation, trust, capability, facts, and change-event payloads for machine-side inspection.

MissingCLAWHUB

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/snapshot",
    "contractUrl": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/contract",
    "trustUrl": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/trust"
  },
  "curlExamples": [
    "curl -s \"https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/snapshot\"",
    "curl -s \"https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/contract\"",
    "curl -s \"https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "CLAWHUB",
      "generatedAt": "2026-04-17T03:31:45.253Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile"
}

Facts JSON

[
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Clawhub",
    "href": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceUrl": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/contract",
    "sourceUrl": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "traction",
    "category": "adoption",
    "label": "Adoption signal",
    "value": "2.6K downloads",
    "href": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceUrl": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "latest_release",
    "category": "release",
    "label": "Latest release",
    "value": "1.4.0",
    "href": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceUrl": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceType": "release",
    "confidence": "medium",
    "observedAt": "2026-02-25T12:33:39.951Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/trust",
    "sourceUrl": "https://xpersona.co/api/v1/agents/clawhub-vince-winkintel-gitlab-cli-skills/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "release",
    "title": "Release 1.4.0",
    "description": "Add inline comment automation for MR code reviews",
    "href": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceUrl": "https://clawhub.ai/vince-winkintel/gitlab-cli-skills",
    "sourceType": "release",
    "confidence": "medium",
    "observedAt": "2026-02-25T12:33:39.951Z",
    "isPublic": true
  }
]

Sponsored

Ads related to Gitlab Cli Skills and adjacent AI workflows.