glab-duo — Claude Code skill: GitLab Duo CLI
The glab-duo Claude Code skill installs and runs GitLab Duo CLI through glab. It activates for terminal access to GitLab Duo Agent Platform, interactive sessions, or a bounded headless task.
MIT 116 installs ★ 51 updated 2026-10-20
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a claude-codeWhat glab-duo does
The skill covers glab duo cli installation, updates, and interactive or headless runs. A single bounded task uses glab duo cli run --goal; provide stop conditions and have the resulting changes reviewed independently.
First authenticate with glab auth login; glab then handles authentication for Duo CLI. The GA path requires GitLab 19.2 or later and the GitLab Duo Agent Platform prerequisites. Self-Managed and Dedicated instances must allow Duo CLI access. GitLab 18.11 through 19.1 require beta and experimental features to be enabled.
Install with glab duo cli --install and update with glab duo cli update. The --yes flag skips confirmation prompts for that invocation, but does not grant approval to download or run executable code. Current glab hides and deprecates glab duo ask; use glab duo cli --help to inspect the wrapper’s commands.
What it helps with
- install GitLab Duo CLI through
glab - start Duo CLI in an interactive session
- send the agent a bounded task with
--goal - update the managed Duo CLI version
Example prompts for the agent
- Install GitLab Duo CLI through
glaband explain how to update it. - Start GitLab Duo CLI in an interactive terminal session.
- Ask it to fix failing tests with
glab duo cli run --goaland define stop conditions.
How to install glab-duo
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a claude-code2Manually: put the files in place
~/.claude/skills/glab-duo/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glab-duo/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a codex2Manually: put the files in place
.agents/skills/glab-duo/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a cursor2Manually: put the files in place
.cursor/skills/glab-duo/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vince-winkintel/gitlab-cli-skills glab-duo2Manually: put the files in place
.github/skills/glab-duo/SKILL.md1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a gemini-cli2Platform CLI
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-duoManually: put the files in place
.devin/skills/glab-duo/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about glab-duo
How do I install glab-duo in Claude Code?
Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-duo -a claude-code. The skill file will be at ~/.claude/skills/glab-duo/SKILL.md.
What does glab-duo do?
It helps install, update, and run GitLab Duo CLI through glab, including interactive sessions and bounded tasks passed with --goal.
What does glab-duo require?
It requires glab authenticated with glab auth login. The GA path needs GitLab 19.2 or later and the GitLab Duo Agent Platform prerequisites; Self-Managed and Dedicated instances must allow Duo CLI access. GitLab 18.11 through 19.1 need beta and experimental features enabled.
Source text
SKILL.md · MIT
--- name: glab-duo description: Install and run GitLab Duo CLI through glab in interactive or headless mode. Use when accessing GitLab Duo Agent Platform from the terminal, running a bounded headless goal, or managing the wrapped Duo CLI binary. Triggers on Duo, GitLab Duo CLI, glab duo cli, AI assistant, headless goal, autonomous coding. --- # glab duo ## Overview `glab duo` is centered on the GitLab Duo Agent Platform. The current visible command surface exposes `glab duo cli`; the legacy `glab duo ask` command is hidden and deprecated. ## Quick start ```bash glab duo --help ``` ## Command surface guidance Upstream `glab` now hides and deprecates `glab duo ask`. Treat `glab duo ask` as legacy guidance only for older installed versions that still expose it in live help. For current forward-looking documentation, prefer: ```bash glab duo cli ``` Use `glab duo cli` for the forward-looking GitLab Duo Agent Platform experience. `glab` handles authentication for the Duo CLI after you authenticate once with `glab auth login`. Prerequisites for the GA path are GitLab 19.2 or later and the GitLab Duo Agent Platform prerequisites. GitLab Self-Managed and Dedicated instances must also allow Duo CLI access. GitLab 18.11 through 19.1 require beta and experimental features to be enabled. ### Installing GitLab Duo CLI `glab duo cli` supports install, update, and non-interactive confirmation flags. Prefer the explicit `update` subcommand; `--update` remains equivalent: ```bash # Install GitLab Duo CLI interactively glab duo cli --install # Install GitLab Duo CLI non-interactively (auto-confirm) glab duo cli --install --yes # Check for and install a compatible Duo CLI update glab duo cli update # Legacy-equivalent flag form glab duo cli --update ``` Use `--install` to download and install the GitLab Duo CLI binaries. Use `--yes` to skip confirmation prompts during installation, which is useful for automation and CI/CD pipelines. The managed updater accepts Duo CLI through major 10; a later major requires a compatible glab update. This compatibility ceiling is not a claim about which Duo binary is installed. The update command does not replace a custom binary configured through `GLAB_DUO_CLI_BINARY_PATH` or `duo_cli_binary_path`. Obtain approval for downloading/installing/updating executable code, changing persistent auto-download/auto-run settings, and running the agent with repository and credential access. `--yes` bypasses wrapper prompts; it does not supply that approval. Wrapper `--help` is sufficient for discovery and does not require a managed download. ### Interactive and headless modes ```bash # Interactive, multi-prompt session with build and plan modes glab duo cli # One bounded prompt for a runner, script, or automated workflow glab duo cli run --goal "Fix the failing tests in this project" # Wrapper help versus the installed Duo CLI's own command surface glab duo cli --help glab duo cli help ``` Use headless `run --goal` only with a bounded task, an isolated working tree, explicit stop conditions, and an independent review of the resulting changes. `glab` passes unknown arguments and flags through to the Duo CLI binary, so verify the installed Duo CLI's own `help` before relying on forwarded options. To persist wrapper prompt behavior, set `duo_cli_auto_download` and `duo_cli_auto_run` with `glab config set ... --global`. `--yes` skips confirmation prompts for the current invocation. ### Important documentation note Guidance that recommends `glab duo update` is stale; the current wrapper form is `glab duo cli update`, with `glab duo cli --update` retained as an equivalent flag form. Rely on live help before using any Duo subcommand that is not documented here. When local CLI help and external documentation diverge during a transition, document the current upstream direction clearly and note compatibility caveats only when they materially affect usage. ## Subcommands See [references/commands.md](references/commands.md) for full `--help` output.
© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills