glab-token

Create, list, revoke, and rotate GitLab access tokens.

43|5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-token
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glab-token
Source: https://github.com/vince-winkintel/gitlab-cli-skills/tree/main/glab-token
Command: npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-token

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the management of GitLab personal access tokens and project access tokens, streamlining API authentication and access control.

Core Features & Use Cases

  • Token Creation: Generate new user, group, or project access tokens with specified scopes and durations.
  • Token Listing: View existing tokens and their metadata for auditing and management.
  • Token Revocation/Rotation: Securely revoke or rotate access tokens to manage security.
  • Use Case: You need to create a new project access token with read_repository scope for a CI/CD pipeline. This Skill can generate the token with a specific expiration date.

Quick Start

Create a new project access token named 'my-pipeline-token' with developer access level and read repository scope.

Frequently Asked Questions about glab-token

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

FAQPage Schema
How do I create a GitLab project access token for a CI/CD pipeline?

You can generate a GitLab project access token by specifying its name, assigning scopes like read_repository, setting a developer access level, and defining an expiration date to secure CI/CD pipeline authentication.

Can I manage GitLab tokens for both groups and projects?

Yes, GitLab token management supports creating, listing, revoking, and rotating access tokens at the user, group, and project levels for comprehensive API access control across your environments.

What is the best way to rotate or revoke GitLab API tokens?

The best way to manage GitLab API token lifecycles is by using token rotation and revocation features, which securely update or invalidate existing access credentials to maintain strict access control.

Does GitLab token management support setting custom expiration dates and access scopes?

Yes, GitLab token management supports specifying custom access levels, defining API scopes, and setting specific token durations or expiration dates to control exactly how long credentials remain valid.

When do I need to use project access tokens instead of personal access tokens in GitLab?

You need to use project access tokens instead of personal access tokens when you want to bind API authentication and access scopes directly to a specific GitLab project or group rather than an individual user account.