Run any Skill in Manus with one click

glab-deploy-key

Stars2

Forks1

UpdatedApril 7, 2026 at 07:41

Manage GitLab deploy keys using the glab CLI. Use this skill whenever the user wants to add, list, view, or delete deploy keys for a GitLab project. Trigger on phrases like "add a deploy key", "set up read-only SSH access for CI", "list deploy keys", "remove a deploy key", or any GitLab deploy key management task.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

yumeminami

yumeminami/gitlab_cli_skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	glab-deploy-key
description	Manage GitLab deploy keys using the glab CLI. Use this skill whenever the user wants to add, list, view, or delete deploy keys for a GitLab project. Trigger on phrases like "add a deploy key", "set up read-only SSH access for CI", "list deploy keys", "remove a deploy key", or any GitLab deploy key management task.

GitLab Deploy Key Management

Use glab deploy-key to manage project-scoped SSH keys for deployment automation. Deploy keys are project-specific (unlike account SSH keys) and are ideal for CI/CD systems and servers that need repository access.

Add a Deploy Key

glab deploy-key add -t "<title>" <public-key-file>

# Read-only access (default)
glab deploy-key add -t "ci-server" ~/.ssh/deploy_id_ed25519.pub

# Read-write access (allows push)
glab deploy-key add -t "deploy-agent" ~/.ssh/deploy_id_ed25519.pub -c

# With expiry
glab deploy-key add -t "temp-key" ~/.ssh/deploy.pub -e 2025-12-31

Key flags:

-t / --title display name (required)
Positional argument: path to the public key file (.pub)
-c / --can-push allow push access (default: read-only)
-e / --expires-at ISO 8601 expiry date

List Deploy Keys

glab deploy-key list

Get a Deploy Key

glab deploy-key get <id>

Delete a Deploy Key

glab deploy-key delete <id>

Deploy Key vs Account SSH Key

	Deploy Key	Account SSH Key
Scope	Single project	All projects you own
Linked to	Project	User account
Best for	CI/CD servers	Developer machines
Read-write	Optional (`-c`)	Full access

Typical Workflow

# 1. Generate a dedicated key for the deploy target
ssh-keygen -t ed25519 -f ~/.ssh/deploy_project_name -N ""

# 2. Add the public key as a deploy key (read-only)
glab deploy-key add -t "prod-server-2025" ~/.ssh/deploy_project_name.pub

# 3. Configure SSH on the target machine to use this key
# ~/.ssh/config:
# Host gitlab.com
#   IdentityFile ~/.ssh/deploy_project_name

Behavior Guidelines

Dedicated keys: Always generate a separate key pair for each deploy target — never reuse personal SSH keys as deploy keys.
Read-only by default: Only add -c (can-push) if the deployment process needs to push commits or tags back to the repository.
Expiry: Recommend setting expiry dates for deploy keys used in temporary environments.
Key naming: Use descriptive titles like prod-server, ci-runner-01 to track where each key is deployed.

More from this repository

same repository

glab-auth

yumeminami/gitlab_cli_skills

Manage GitLab authentication using the glab CLI. Use this skill whenever the user needs to log in to GitLab, check authentication status, log out, switch GitLab instances, or configure credentials. Trigger on phrases like "login to GitLab", "authenticate glab", "glab auth", "check if I'm logged in", "switch GitLab instance", "set up a personal access token", or any authentication/credential configuration task.

2026-04-072

glab-ci

yumeminami/gitlab_cli_skills

Manage GitLab CI/CD pipelines using the glab CLI. Use this skill whenever the user mentions pipelines, CI jobs, build status, pipeline logs, triggering a pipeline, retrying a failed pipeline, or validating .gitlab-ci.yml. Trigger on phrases like "check pipeline status", "why did the build fail", "trigger a pipeline", "watch CI logs", "lint the CI config", or anything related to GitLab CI/CD.

2026-04-072

glab-config

yumeminami/gitlab_cli_skills

Manage glab CLI configuration using the glab config command. Use this skill whenever the user wants to configure glab settings like the default editor, git protocol, browser, or any glab preference. Trigger on phrases like "configure glab", "set glab editor", "change git protocol to SSH", "edit glab config", "set default browser for glab", or any glab configuration management task.

2026-04-072

glab-issue

yumeminami/gitlab_cli_skills

Manage GitLab Issues using the glab CLI. Use this skill whenever the user mentions creating, listing, viewing, updating, closing, or commenting on GitLab issues. Trigger on phrases like "create an issue", "list issues", "close issue

2026-04-072

glab-job

yumeminami/gitlab_cli_skills

Download CI/CD job artifacts from GitLab pipelines using the glab CLI. Use this skill whenever the user wants to download build artifacts, test reports, compiled binaries, or any files produced by a CI/CD job. Trigger on phrases like "download build artifacts", "get the test report from CI", "download the compiled binary from the pipeline", "fetch job artifacts", or any GitLab CI artifact download task.

2026-04-072

glab-label

yumeminami/gitlab_cli_skills

Manage GitLab project labels using the glab CLI. Use this skill whenever the user wants to create, list, edit, or delete labels in a GitLab project. Trigger on phrases like "create a label", "add a bug label", "list project labels", "change label color", "delete a label", or any GitLab label management task.

2026-04-072

name	glab-deploy-key
description	Manage GitLab deploy keys using the glab CLI. Use this skill whenever the user wants to add, list, view, or delete deploy keys for a GitLab project. Trigger on phrases like "add a deploy key", "set up read-only SSH access for CI", "list deploy keys", "remove a deploy key", or any GitLab deploy key management task.

GitLab Deploy Key Management

Add a Deploy Key

glab deploy-key add -t "<title>" <public-key-file>

# Read-only access (default)
glab deploy-key add -t "ci-server" ~/.ssh/deploy_id_ed25519.pub

# Read-write access (allows push)
glab deploy-key add -t "deploy-agent" ~/.ssh/deploy_id_ed25519.pub -c

# With expiry
glab deploy-key add -t "temp-key" ~/.ssh/deploy.pub -e 2025-12-31

Key flags:

-t / --title display name (required)
Positional argument: path to the public key file (.pub)
-c / --can-push allow push access (default: read-only)
-e / --expires-at ISO 8601 expiry date

List Deploy Keys

glab deploy-key list

Get a Deploy Key

glab deploy-key get <id>

Delete a Deploy Key

glab deploy-key delete <id>

Deploy Key vs Account SSH Key

	Deploy Key	Account SSH Key
Scope	Single project	All projects you own
Linked to	Project	User account
Best for	CI/CD servers	Developer machines
Read-write	Optional (`-c`)	Full access

Typical Workflow

# 1. Generate a dedicated key for the deploy target
ssh-keygen -t ed25519 -f ~/.ssh/deploy_project_name -N ""

# 2. Add the public key as a deploy key (read-only)
glab deploy-key add -t "prod-server-2025" ~/.ssh/deploy_project_name.pub

# 3. Configure SSH on the target machine to use this key
# ~/.ssh/config:
# Host gitlab.com
#   IdentityFile ~/.ssh/deploy_project_name

Behavior Guidelines

Dedicated keys: Always generate a separate key pair for each deploy target — never reuse personal SSH keys as deploy keys.
Read-only by default: Only add -c (can-push) if the deployment process needs to push commits or tags back to the repository.
Expiry: Recommend setting expiry dates for deploy keys used in temporary environments.
Key naming: Use descriptive titles like prod-server, ci-runner-01 to track where each key is deployed.