glab-ssh-key

Manage GitLab SSH keys with add, list, and delete subcommands via glab CLI.

1|Updated Apr 18, 2026

Search Tags:#security #authentication #cli #gitlab #ssh #ssh-key

One-click install

npx skills add https://github.com/a-ng-d/claude-ui-color-palette --skill glab-ssh-key-a-ng-d

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-ssh-key
Source: https://github.com/a-ng-d/claude-ui-color-palette/tree/main/skills/gitlab-cli-skills/glab-ssh-key
Command: npx skills add https://github.com/a-ng-d/claude-ui-color-palette --skill glab-ssh-key-a-ng-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SSH keys are essential for authenticating GitLab interactions over SSH, and users often struggle to keep keys organized. This skill centralizes the management of those keys by enabling adding, listing, and removing keys associated with the account.

Core Features & Use Cases

Add new SSH keys to the GitLab account to enable SSH-based operations.
List all SSH keys for the authenticated user to review and audit access.
Delete unused or compromised keys to maintain secure access control.
Use Case: A developer adds their workstation public key, lists keys to verify, and removes old keys when changing devices.

Quick Start

Add a public SSH key to your GitLab account by running glab ssh-key add ~/.ssh/id_ed25519.pub -t 'Work Laptop'.

Frequently Asked Questions about glab-ssh-key

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

FAQPage Schema

How do I add an SSH key to my GitLab account using the CLI?▼

To add an SSH key to your GitLab account, run glab ssh-key add followed by the path to your public key file and a title, enabling SSH-based Git operations from that workstation.

Can I list and audit all SSH keys associated with my GitLab user?▼

Yes, you can list all SSH keys associated with your GitLab user by running glab ssh-key list, allowing you to audit access and verify which workstations or CI environments have authentication configured.

What is the best way to remove old or compromised GitLab SSH keys?▼

The best way to remove compromised GitLab SSH keys is using the glab ssh-key delete command, which helps maintain secure access control by revoking unused or outdated authentication credentials.

Does managing GitLab SSH keys with glab require any specific public-key format?▼

Yes, managing GitLab SSH keys with glab enforces public-key requirements, requiring you to provide a valid public key file like id_ed25519.pub to successfully configure authentication.

Can I use glab to manage SSH keys across different workstations and CI environments?▼

Yes, you can use glab to manage SSH keys across workstations and CI environments, centralizing the configuration and auditing of authentication credentials for your GitLab account.

Why should I use glab to manage GitLab SSH keys instead of the web interface?▼

Using glab to manage GitLab SSH keys centralizes key organization and enables quick add, list, and delete operations directly from the CLI, streamlining secure access control across multiple devices.