glab-securefile

Upload, list, download, and delete CI/CD project secure files via glab securefile commands.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill glab-securefile-haomingz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glab-securefile
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/gitlab-cli-guide/glab-securefile
Command: npx skills add https://github.com/haomingz/kimi-skills --skill glab-securefile-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CI/CD workflows expose sensitive credentials and configuration when stored in code or environment leaks. This Skill provides a secure file storage interface to upload, list, download, and delete files used by pipelines, keeping sensitive data out of the repository.

Core Features & Use Cases

  • Secure storage: Upload and store project-scoped secure files (certificates, keys, tokens) outside the repository.
  • Controlled access: List and download files with repository-scoped permissions to support pipelines and agents.
  • Lifecycle management: Remove outdated or compromised files and audit file listings as part of CI hygiene.
  • Use Case: A CI workflow uses a TLS certificate stored as a secure file to authenticate deployment to a staging environment without exposing the private key in code.

Quick Start

Upload a new secure file to the project and verify it appears in the list.

Frequently Asked Questions about glab-securefile

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

FAQPage Schema
How do I manage CI/CD secure files in GitLab without exposing credentials in my repository?

To manage CI/CD secure files outside your repository, you can upload, list, download, and delete sensitive credentials using glab securefile commands with repository scope controlled by --repo and -R.

What is the file size limit and maximum count for uploading GitLab CI/CD secure files?

GitLab CI/CD secure files have a limit of 100 files per project, and each uploaded secure file must be under 5 MB in size to support pipeline authentication workflows.

How do I download a TLS certificate stored as a secure file for a staging deployment pipeline?

To download a TLS certificate stored as a secure file for staging deployment, use the glab securefile download command with the appropriate repository scope flags to access the sensitive data.

How do I remove outdated or compromised secret files from a GitLab project?

To remove compromised secret files from a GitLab project for CI hygiene, use the glab securefile delete command to safely revoke and delete the outdated sensitive configuration.

Can I use glab to store deployment tokens outside my GitLab repository?

Yes, you can use glab to store deployment tokens as secure files outside your GitLab repository, keeping sensitive credentials and configuration data separated from your codebase.

What is the best way to audit which secure files are available in a GitLab CI/CD project?

The best way to audit available secure files in a GitLab CI/CD project is to use the glab securefile list command, which displays all stored credentials and configurations for pipeline access.