glab-runner-controller

Manage GitLab runner controllers and authentication token lifecycles via glab commands.

1|Updated Apr 18, 2026

Search Tags:#gitlab #admin #glab #scopes #token-management #runner-controller

One-click install

npx skills add https://github.com/a-ng-d/claude-ui-color-palette --skill glab-runner-controller-a-ng-d

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-runner-controller
Source: https://github.com/a-ng-d/claude-ui-color-palette/tree/main/skills/gitlab-cli-skills/glab-runner-controller
Command: npx skills add https://github.com/a-ng-d/claude-ui-color-palette --skill glab-runner-controller-a-ng-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitLab administrators face complex tasks managing runner controllers, their connection details, and token lifecycles across multiple projects and groups.

Core Features & Use Cases

Create, inspect, update, and delete runner controllers to manage the lifecycle of runners in an infrastructure.
Manage controller scopes (instance-level or per-runner) to enforce access boundaries.
Generate, rotate, and revoke tokens to maintain secure access and respond to compromises.

Quick Start

Run the glab runner-controller create command to initialize a new runner controller.

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 controllers and their authentication tokens are managed through glab runner-controller commands, which allow administrators to create, inspect, update, and delete controllers, as well as generate, rotate, and revoke tokens across environments.

How do I rotate or revoke GitLab runner tokens after a security compromise?▼

To rotate or revoke GitLab runner tokens after a compromise, administrators use glab runner-controller token management commands to generate, rotate, and revoke access credentials, ensuring secure infrastructure boundaries are restored.

What are GitLab runner controller scopes and how do I enforce access boundaries?▼

GitLab runner controller scopes are access boundaries configured at the instance level or per-runner. Administrators enforce these boundaries by updating controller scopes to restrict runner infrastructure access across projects and groups.

Do I need GitLab admin permissions to use glab runner-controller commands?▼

Yes, GitLab admin permissions are required. The glab runner-controller workflows are admin-only and experimental, necessitating explicit state management and safety reminders to securely handle infrastructure lifecycles and token operations.

What is the best way to create a new GitLab runner controller for my infrastructure?▼

The best way to create a new GitLab runner controller is to run the glab runner-controller create command, which initializes the controller while managing its connection details and access scopes within your infrastructure.

What are the limitations of using experimental glab runner-controller workflows?▼

Limitations of experimental glab runner-controller workflows include the requirement for explicit state management and strict adherence to safety reminders, as these admin-only commands handle complex token lifecycles and controller scopes across environments.