Verified:GitHub

variables

Name: variables
Availability: InStock
Author: theslashdojo

List, inspect, set, and delete GitLab project-level CI/CD variables.

Updated Apr 10, 2026

Search Tags:#automation #api #secrets #gitlab #ci-cd #variables

Ready to run

npx skills add https://github.com/theslashdojo/dojo --skill variables-theslashdojo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: variables
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/gitlab/variables
Command: npx skills add https://github.com/theslashdojo/dojo --skill variables-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitLab project-level CI/CD variables are often scattered across teams and pipelines. This skill provides centralized tooling to list, inspect, set, and delete those variables, enabling secure secret management and environment-specific configurations without editing repository YAML.

Core Features & Use Cases

List all project variables for a GitLab project.
Retrieve a specific variable with an environment scope.
Create or update a variable with environment_scope, protection, masking, and hidden options.
Delete a scoped variable to rotate secrets or remove outdated configurations.
Use for secrets management, feature flags, and per-environment configuration across pipelines.

Quick Start

Use this skill to list the variables for a project or set a new secret variable for production.

Frequently Asked Questions about variables

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

FAQPage Schema

How do I manage GitLab CI/CD variables across multiple projects without editing repository YAML?▼

You can manage GitLab CI/CD variables securely by listing, inspecting, setting, and deleting project-level variables through the API. This enables centralized secret management and environment-specific configurations without modifying your repository YAML files.

Can I scope GitLab CI/CD variables to specific environments?▼

Yes, GitLab CI/CD variables support environment_scope filtering. You can create or update variables with specific environment scopes, ensuring configurations and secrets apply only to designated pipelines.

What GitLab API token do I need to automate CI/CD variable management?▼

Automating GitLab CI/CD variable management requires authentication via GitLab API tokens. You must provide valid API tokens to list, inspect, set, or delete project-level variables programmatically.

Does GitLab CI/CD variable management support protected and masked secrets?▼

Yes, GitLab CI/CD variables support protected, masked, hidden, and raw expansion options. You can configure these settings when creating or updating variables to ensure secrets are handled securely in pipeline logs.

What is the difference between env_var and file variable types in GitLab CI/CD?▼

GitLab CI/CD variables support two variable types: env_var and file. The env_var type exposes the value as an environment variable, while the file type provides the value as a file path for pipeline consumption.

How do I rotate secrets by deleting outdated GitLab CI/CD variables?▼

You can rotate secrets by deleting scoped GitLab CI/CD variables. This removes outdated configurations from your project, ensuring pipelines consume only the latest updated credentials.