Verified:GitHub

glab-runner-controller

Manage GitLab runner controllers and their authentication tokens.

Updated Mar 15, 2026

Search Tags:#automation #devops #ci/cd #gitlab #runners #controller management

One-click install

npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-runner-controller-proyectog007

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-runner-controller
Source: https://github.com/ProyectoG007/Skill.bat/tree/main/scripts/05_Dev_Tools/07.%20gitlab-cli-skills-1.11.0/glab-runner-controller
Command: npx skills add https://github.com/ProyectoG007/Skill.bat --skill glab-runner-controller-proyectog007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the management of GitLab runner controllers and their associated authentication tokens, streamlining DevOps operations.

Core Features & Use Cases

Controller Lifecycle Management: Create, list, update, and delete runner controllers.
Token Management: Generate, rotate, and revoke authentication tokens for controllers.
Use Case: An administrator needs to set up a new set of runners for a specific project. They can use this Skill to create a new controller, generate a secure token for it, and then associate the necessary runners.

Quick Start

Use the glab-runner-controller skill to create a new runner controller with the description "Production runners".

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?▼

You can manage GitLab runner controllers by creating, listing, updating, and deleting them, while handling token generation, rotation, and revocation for secure CI/CD runner infrastructure administration.

How do I rotate or revoke authentication tokens for GitLab CI/CD runners?▼

Rotate or revoke authentication tokens for GitLab CI/CD runners through dedicated controller lifecycle management commands, enabling secure administration and rotation of runner orchestration credentials.

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

The best way to set up a new GitLab runner controller is by creating a controller instance and generating a secure authentication token to associate necessary runners for your project.

Can I automate the lifecycle management of GitLab runner controllers?▼

Yes, you can automate the lifecycle management of GitLab runner controllers, enabling administrative control over creation, deletion, updating, and listing of controllers for DevOps operations.

Does GitLab runner controller management support token revocation for CI/CD infrastructure?▼

Yes, GitLab runner controller management supports token revocation, alongside generation and rotation, to address the need for secure and efficient administration of CI/CD runner infrastructure.

Why do I need to generate a specific token when creating a GitLab runner controller?▼

You need to generate a specific token when creating a GitLab runner controller to establish secure authentication, enabling administrative control over the orchestration of associated CI/CD runners.