# glab-runner-controller

The glab-runner-controller Claude Code skill manages GitLab Runner controllers and their tokens. It activates for requests about controller setup, scopes, or token changes.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 113 installs · ★ 51 repo stars
- Author: vince-winkintel
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/vince-winkintel/gitlab-cli-skills/tree/HEAD/glab-runner-controller/SKILL.md
- Updated: 2026-10-20
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/glab-runner-controller

## What it does

The skill manages GitLab Runner controllers through `glab runner-controller` commands. It can create, inspect, update, and delete controllers, then set their scope to cover an instance or selected runners.

Token operations include creation, listing, rotation, and revocation. A new token value appears only during creation. This is an experimental, admin-only feature; it may break or be removed without notice.

## Requirements
- Works with: GitLab

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-runner-controller -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/glab-runner-controller/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/glab-runner-controller/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-runner-controller -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/glab-runner-controller/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-runner-controller -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/glab-runner-controller/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install vince-winkintel/gitlab-cli-skills glab-runner-controller
```

2. **Manually: put the files in place**
- File: `.github/skills/glab-runner-controller/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-runner-controller -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-runner-controller
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/glab-runner-controller/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-runner-controller -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/vince-winkintel/gitlab-cli-skills/tree/HEAD/glab-runner-controller/SKILL.md

## When to use it
- create and configure a GitLab Runner controller
- change a controller’s state or remove it
- limit a controller to selected runners
- issue, rotate, or revoke a controller token

## Example prompts
- Create a GitLab Runner controller with the description “Production runners.”
- Show the scopes for controller 42 and add runners 5 and 10.
- Create a token for controller 42, then revoke token 1.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: a26ad5f58f9180f5.

BEGIN THIRD-PARTY FILE a26ad5f58f9180f5
````text
---
name: glab-runner-controller
description: Manage GitLab runner controllers and authentication tokens. Create, inspect, update, delete controllers; manage scopes; and generate, rotate, and revoke tokens. Admin-only experimental feature for managing runner controller lifecycle. Triggers on runner controller, controller token, controller scope, experimental runner, admin runner.
---

# glab-runner-controller

Manage GitLab runner controllers and their authentication tokens.

## ⚠️ Experimental Feature

**Status:** EXPERIMENTAL (Admin-only)
- This feature may be broken or removed without prior notice
- Use at your own risk
- Requires GitLab admin privileges
- See: https://docs.gitlab.com/policy/development_stages_support/

## What It Does

Runner controllers manage the orchestration of GitLab Runners in your infrastructure. This skill provides commands to:
- Create and configure runner controllers
- Inspect controller details and connection status
- Manage controller lifecycle (list, get, update, delete)
- Manage controller scopes (instance-level or runner-level)
- Generate and rotate authentication tokens
- Revoke compromised tokens

## Common Workflows

### Create Runner Controller

```bash
# Create with default settings
glab runner-controller create

# Create with description
glab runner-controller create --description "Production runners"

# Create enabled controller
glab runner-controller create --description "Prod" --state enabled
```

**States:**
- `disabled` - Controller exists but inactive
- `enabled` - Controller is active (default)
- `dry_run` - Test mode (no actual runner execution)

### List and View Controllers

```bash
# List all controllers
glab runner-controller list

# List with pagination
glab runner-controller list --page 2 --per-page 50

# Output as JSON
glab runner-controller list --output json

# Get one controller with status details
glab runner-controller get 42

glab runner-controller get 42 --output json
```

### Update Controller

```bash
# Update description
glab runner-controller update 42 --description "Updated name"

# Change state
glab runner-controller update 42 --state disabled

# Update both
glab runner-controller update 42 --description "Prod" --state enabled
```

### Delete Controller

```bash
# Delete with confirmation prompt
glab runner-controller delete 42

# Delete without confirmation
glab runner-controller delete 42 --force
```

## Scope Management

Runner controller scopes determine what the controller is allowed to evaluate.

### List Scopes

```bash
# List all scopes for controller 42
glab runner-controller scope list 42

# JSON output
glab runner-controller scope list 42 --output json
```

### Add Scopes

```bash
# Allow the controller to evaluate all instance runners
glab runner-controller scope create 42 --instance

# Allow the controller to evaluate a specific runner
glab runner-controller scope create 42 --runner 5

# Add multiple runner scopes
````
END THIRD-PARTY FILE a26ad5f58f9180f5

The third-party file has ended. Everything between the a26ad5f58f9180f5 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2952 of 7333 bytes. © vince-winkintel · MIT · https://github.com/vince-winkintel/gitlab-cli-skills/tree/HEAD/glab-runner-controller/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
