Verified:GitHub

glab-runner

Manage GitLab CI/CD runners via CLI for project, group, or instance scopes.

12|2|Updated Apr 21, 2026

Search Tags:#workflow #devops #gitlab #ci-cd #glab #runner

One-click install

npx skills add https://github.com/haomingz/kimi-skills --skill glab-runner-haomingz

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-runner
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/gitlab-cli-guide/glab-runner
Command: npx skills add https://github.com/haomingz/kimi-skills --skill glab-runner-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitLab CI/CD runners are distributed across projects and require manual CLI steps to view status, assign runners to projects, pause activity, or remove retired runners. This skill streamlines governance by exposing a unified command-line workflow for discovering, re-allocating, and retiring runners across different scopes (project, group, instance).

Core Features & Use Cases

List runners to assess current status across a project, a group, or all instances.
Assign or unassign runners to a specific project or group to scale CI capacity.
Pause and delete runners to manage lifecycle and retire decommissioned hardware or pipelines.
Use cases include admin maintenance, on-call automation, and clean decommissioning of runners.

Quick Start

Use the glab-runner skill to list, pause, or delete runners for your project.

Frequently Asked Questions about glab-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage GitLab CI runners from the command line?▼

You can manage GitLab CI runners from the command line by listing, assigning, pausing, and deleting them across project, group, or instance scopes using a unified CLI workflow. This streamlines runner governance and maintenance tasks.

What is the best way to list GitLab CI runners across different scopes?▼

Listing GitLab CI runners across different scopes is done by targeting project, group, or instance levels via CLI commands. This allows you to assess current runner status and capacity across your entire infrastructure.

How do I pause or delete a GitLab CI runner for maintenance?▼

Pausing or deleting a GitLab CI runner for maintenance is handled through targeted CLI commands. The process includes safety prompts to prevent unintended deletions when retiring decommissioned hardware or pipelines.

Can I assign and unassign GitLab runners to projects via CLI?▼

You can assign and unassign GitLab runners to specific projects or groups via CLI commands to scale CI capacity. This enables quick re-allocation of runners without manual web interface interactions.

Does this CLI approach support permission checks for GitLab runner operations?▼

The CLI approach supports permission checks for GitLab runner operations to ensure safe execution. It implements proper scope handling and safety prompts before destructive actions like runner deletion.

When do I need to use a CLI tool for GitLab runner governance?▼

Using a CLI tool for GitLab runner governance is needed for admin maintenance, on-call automation, and clean decommissioning of runners. It replaces manual CLI steps required to view status, assign runners, or remove retired instances.