AgentStack
SKILL verified MIT Self-run

Glab Config

skill-vince-winkintel-gitlab-cli-skills-glab-config · by vince-winkintel

Manage glab CLI configuration settings including defaults, preferences, and per-host settings. Use when configuring glab behavior, setting defaults, or viewing current configuration. Triggers on config, configuration, settings, glab settings, set default.

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-vince-winkintel-gitlab-cli-skills-glab-config

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Glab Config? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

glab config

Overview


  Manage key/value strings.
  Current respected settings:
  - browser: If unset, uses the default browser. Override with environment variable $BROWSER.
  - check_update: If true, notifies of new versions of glab. Defaults to true. Override with environment variable
  $GLAB_CHECK_UPDATE.
  - display_hyperlinks: If true, and using a TTY, outputs hyperlinks for issues and merge request lists. Defaults to
  false.
  - editor: If unset, uses the default editor. Override with environment variable $EDITOR.
  - glab_pager: Your desired pager command to use, such as 'less -R'.
  - glamour_style: Your desired Markdown renderer style. Options are dark, light, notty. Custom styles are available
  using [glamour](https://github.com/charmbracelet/glamour#styles).
  - host: If unset, defaults to `https://gitlab.com`.
  - token: Your GitLab access token. Defaults to environment variables.
  - visual: Takes precedence over 'editor'. If unset, uses the default editor. Override with environment variable
  $VISUAL.
  USAGE
    glab config [command] [--flags]
  COMMANDS
    edit [--flags]               Opens the glab configuration file.
    get  [--flags]          Prints the value of a given configuration key.
    set   [--flags]  Updates configuration with the value of a given key.
  FLAGS
    -g --global                  Use global config file.
    -h --help                    Show help for this command.

Quick start

glab config --help

Per-host HTTPS proxy configuration

You can configure an HTTPS proxy on a per-host basis. This is useful when different GitLab instances (for example gitlab.com vs a self-hosted instance) require different proxy settings.

# Set HTTPS proxy for a specific host
glab config set https_proxy "http://proxy.example.com:8080" --host gitlab.mycompany.com

# Set globally (applies to all hosts without a specific override)
glab config set https_proxy "http://proxy.example.com:8080" --global

# Verify
glab config get https_proxy --host gitlab.mycompany.com

Precedence: Per-host config overrides global config. Global config overrides the HTTPS_PROXY / https_proxy environment variables.

Env-first agent pattern

For agentic setups, prefer per-agent env files over one shared shell profile. Example:

# ~/.config/openclaw/env/gitlab-reviewer.env
GITLAB_TOKEN=glpat-...
GITLAB_HOST=gitlab.com

Keep these env files outside version control, restrict their permissions (for example chmod 600), be mindful of backup exposure, and use least-privilege bot/service-account tokens.

Load plain KEY=value env files like this so the variables are exported to glab:

set -a
source ~/.config/openclaw/env/gitlab-.env
set +a

A plain source ~/.config/openclaw/env/gitlab-.env updates the current shell but may leave the values unexported. In that case glab can miss the env overrides and silently reuse stored auth from ~/.config/glab-cli/config.yml.

Use distinct GitLab bot/service accounts when agents need distinct visible identities. Multiple PATs on one GitLab user still act as that same user.

Non-interactive prompts and config validation

Use GLAB_NO_PROMPT=1 for non-interactive automation that must fail instead of prompting. Upstream docs now prefer the GLAB_-prefixed name; older NO_PROMPT is deprecated and should not be used in new scripts.

GLAB_NO_PROMPT=1 glab repo prune --dry-run

glab config set validates keys against the canonical config schema. If a set operation fails, check the spelling and whether the setting is host-scoped (--host) or global (--global) rather than forcing an unknown key into the config file.

Common Settings

# View current config
glab config get --global

# Set default editor
glab config set editor vim --global

# Set pager
glab config set glab_pager "less -R" --global

# Disable update checks
glab config set check_update false --global

# Set default host
glab config set host https://gitlab.mycompany.com --global

Subcommands

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.