glab-deploy-key

Manage SSH deploy keys for GitLab projects via the GitLab CLI.

43|5|Updated Jan 30, 2026

Search Tags:#automation #ci/cd #gitlab #deploy key #ssh key #access management

One-click install

npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-deploy-key

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-deploy-key
Source: https://github.com/vince-winkintel/gitlab-cli-skills/tree/main/glab-deploy-key
Command: npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-deploy-key

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of SSH deploy keys for GitLab projects, simplifying the process of granting secure, automated access for CI/CD pipelines and deployments.

Core Features & Use Cases

Add Deploy Keys: Securely add new SSH deploy keys to your GitLab projects, specifying titles and push permissions.
List Deploy Keys: View existing deploy keys for a project to audit access.
Delete Deploy Keys: Remove deploy keys when they are no longer needed, enhancing security.
Use Case: When setting up a new CI/CD pipeline, you can use this skill to add a read-only deploy key to your project, allowing the pipeline to pull code without granting write access.

Quick Start

Add a new deploy key with the title "My CI Key" to the current repository.

Frequently Asked Questions about glab-deploy-key

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

FAQPage Schema

How do I add an SSH deploy key to a GitLab project for CI/CD automation?▼

You can add an SSH deploy key to a GitLab project by using this Skill to securely attach a new public key, specifying a title and push permissions. This allows your CI/CD pipeline to authenticate and pull code without manual intervention.

What is the best way to manage read-only GitLab deploy keys for pipelines?▼

Managing read-only GitLab deploy keys is best handled by adding keys without push permissions, allowing CI/CD pipelines to securely pull code. This Skill automates that exact process by interacting with the GitLab API to configure restricted access for deployments.

Do I need the GitLab CLI installed to list and delete project deploy keys?▼

Yes, you need the GitLab CLI (`glab`) installed and configured to list and delete project deploy keys. This Skill requires `glab` to interact directly with the GitLab API for executing deploy key operations like auditing and removal.

How does automating deploy key management improve GitLab access security?▼

Automating deploy key management improves GitLab access security by enabling rapid addition of keys for new pipelines and immediate deletion when keys are no longer needed. This minimizes stale credentials and restricts deployment access to read-only where possible.

Can I configure push permissions when adding a GitLab deploy key?▼

Yes, you can configure push permissions when adding a GitLab deploy key. The Skill allows you to specify whether a new key has write access during creation, letting you choose between read-only access for pulling code or write access for pushing changes.