glab-runner-controller

Manage GitLab runner controllers and their authentication tokens via glab CLI.

43|5|Updated Jan 30, 2026

Search Tags:#ci/cd #token management #gitlab #experimental #admin #runner controller

One-click install

npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-runner-controller

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the management of GitLab runner controllers and their associated authentication tokens, streamlining the setup and security of your CI/CD infrastructure.

Core Features & Use Cases

Controller Lifecycle Management: Create, list, update, and delete runner controllers.
Token Management: Generate, list, rotate, and revoke authentication tokens for controllers.
Use Case: As a GitLab administrator, you need to set up a new runner controller for your development team and ensure its token is rotated every 90 days for security compliance.

Quick Start

Use the glab-runner-controller skill to create a new runner controller with the description "Dev Team Runners" and enable it.

Frequently Asked Questions about glab-runner-controller

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

FAQPage Schema

How do I manage GitLab runner controllers and their authentication tokens?▼

GitLab runner controller management handles the creation, listing, updating, and deletion of controllers, alongside token generation, rotation, and revocation for CI/CD infrastructure security.

Can I rotate GitLab runner tokens for security compliance using glab?▼

Yes, token rotation for GitLab runner controllers is supported, allowing administrators to securely generate, list, rotate, and revoke authentication tokens to maintain CI/CD compliance.

Do I need GitLab admin privileges to manage runner controllers?▼

Yes, GitLab admin privileges are required to manage runner controllers and their tokens. You also need the glab CLI version 1.83.0 or later to execute these administrative tasks.

What is the best way to set up a new GitLab runner controller for a development team?▼

The best way to set up a GitLab runner controller is by creating it with a specific description and enabling it, which streamlines the orchestration of CI/CD runners for your development team.

Does this GitLab runner controller skill work without external dependencies?▼

The skill operates without external dependencies, but it requires GitLab admin privileges and the glab CLI version 1.83.0 or later to manage runner controllers and tokens effectively.

What are the limitations of using glab for runner controller lifecycle management?▼

Limitations include the requirement for GitLab admin privileges and glab CLI version 1.83.0 or later, as it is an experimental skill focused on administrative runner controller and token lifecycle tasks.