Skip to main content
skill CX Codex

glab-variable — Claude Code skill: GitLab CI/CD variables

Gives the agent the glab variable subcommands: create a pipeline variable, adjust its flags, move secrets between GitLab projects and groups.

MIT 126 installs ★ 51 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-variable -a claude-code
Open on GitHub

What glab-variable does

The skill maps out glab variable for the agent. Seven subcommands handle listing, reading, creating, updating and deleting, plus export and import. Everything targets the current project unless you pass --group or point -R at another repository.

get KEY --inherited walks up the chain: the project first, then parent groups from nearest outward, then instance-level entries. Permission errors at one level are skipped and other failures come back. update leaves flags you omit alone, so passing --description won't clear masking or protection; an explicit --protected=false belongs in a change that was approved. Skip the empty-stdin call, because the value gets replaced with an empty string.

Import expects the JSON array that export --output json writes, taken from stdin or --input-file. An existing key halts the run until you add --skip-existing. Hidden values never leave the server, so those keys get skipped with a warning and must be set again from an approved secret store. An export file holds real secrets in plain text; keep it out of version control.

What it helps with

  • set a masked deploy token on a subgroup
  • copy CI/CD variables between two groups
  • trace which value a key resolves to across parent groups
  • change a variable's description without touching its value
  • wipe a stale key from project settings

Example prompts for the agent

  • Add DEPLOY_TOKEN to the platform/staging group as a masked, protected variable.
  • Export the variables of platform to JSON and import them into platform/staging.
  • Check where API_URL comes from: project first, then parent groups.

How to install glab-variable

1Skills CLI (Vercel)

npx skills add vince-winkintel/gitlab-cli-skills --skill glab-variable -a claude-code

2Manually: put the files in place

~/.claude/skills/glab-variable/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/glab-variable/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about glab-variable

How do I install glab-variable in Claude Code?

Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-variable -a claude-code. The skill file lands at ~/.claude/skills/glab-variable/SKILL.md.

What does glab-variable do?

It gives the agent the glab variable subcommands for CI/CD variables in a GitLab project or group: create, update, read, delete, export and import.

Why does an import skip some variables?

Hidden values are left out of an export, so those entries are skipped with a warning during import. Set them again with glab variable set --hidden from an approved secret source.

Source text

SKILL.md · MIT
---
name: glab-variable
description: Manage CI/CD variables at project and group level including create, update, import, export, list, and delete operations. Use when setting environment variables for pipelines, managing secrets, migrating variables, or configuring CI/CD variables. Triggers on variable, CI variable, environment variable, secrets, variable import, CI/CD config.
---

# glab variable

## Inherited reads and partial updates

`variable get KEY --inherited` tries the selected project or group, then parent groups closest first, then instance variables. Missing or unreadable levels (404/401/403) are skipped; other failures are returned. `--scope` filters project/group variables, but not instance variables. This is a lookup of stored definitions, not a full simulation of every CI variable precedence rule. Both text and JSON output can expose secret values; send them only to an approved consumer.

`variable update` preserves optional attributes unless supplied. Omitted `--protected`, `--masked`, `--raw`, `--type`, and `--description` retain their existing values. Use an explicit boolean such as `--protected=false` only when that policy change is approved. The value is still supplied positionally, through `--value`, or from stdin; do not invoke this as a metadata-only update with empty stdin, which can replace the value with an empty string. `--scope` retains its existing targeting behavior.

## Overview

```

  Variables store configuration and secrets used by CI/CD pipelines.

  Each subcommand acts on the current project by default. Use
  `--group` to manage a group's variables instead.
         
  USAGE  
         
    glab variable [command] [--flags]  
            
  COMMANDS  
            
    delete <key> [--flags]          Delete a variable for a project or group.
    export [--flags]                Export variables from a project or group.
    get <key> [--flags]             Get a variable for a project or group.
    import [--flags]                Import variables from a JSON file or standard input.
    list [--flags]                  List variables for a project or group.
    set <key> <value> [--flags]     Create a new variable for a project or group.
    update <key> <value> [--flags]  Update an existing variable for a project or group.
         
  FLAGS  
         
    -h --help                       Show help for this command.
    -R --repo                       Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.
```

## Quick start

```bash
glab variable --help
```

## Export and import variables

`glab variable import` consumes the same JSON array shape emitted by `glab variable export --output json`. It reads standard input by default or a file passed with `--input-file` / `-i`.

```bash
# Preview and preserve an export before importing it elsewhere
glab variable export --output json > variables.json
glab variable import --input-file variables.json -R group/target-project

# Pipe between groups
glab variable export --group source-group |
  glab variable import --group target-group

# Continue when target variables already exist
glab variable import --input-file variables.json --skip-existing
```

Import stops when a target variable already exists unless `--skip-existing` is set. Hidden variable values are omitted from exports, so those entries are skipped with a warning during import; recreate their values explicitly with `glab variable set --hidden` from an approved secret source. Treat export files as sensitive, keep them out of version control, and verify the target project or group before importing.

## Masked and hidden group variables

`glab variable set` now sends `--masked` and `--hidden` correctly for group-level variables. Use explicit flags, verify the target group, and never print the value during confirmation:

```bash
glab variable set DEPLOY_TOKEN "$DEPLOY_TOKEN" \
  --group group/subgroup \
  --masked \
  --hidden \
  --protected

# Inspect only approved metadata; the raw JSON includes the value
glab variable get DEPLOY_TOKEN --group group/subgroup --output json \
  --jq '{key, protected, masked, hidden, environment_scope}'
```

Masking and hiding are server-enforced properties, not substitutes for least privilege or rotation. If GitLab rejects a value because it does not satisfy masking rules, do not weaken the setting silently; fix the value format or get explicit operator approval for a different policy.

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills

Similar skills

All skills for DevOps and infrastructure →

From the same set45

The whole set →

Project sponsors

Companies that keep this analytics open