Skip to main content
skill CX Codex

glab-securefile — Claude Code skill for GitLab CI/CD files

The glab-securefile Claude Code skill manages GitLab secure files used by CI/CD pipelines. It activates for tasks involving pipeline secrets, certificates, or protected configuration files.

MIT 112 installs ★ 51 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-securefile -a claude-code
Open on GitHub

What glab-securefile does

The skill uses glab securefile to upload, replace, download, inspect, list, and delete a project’s secure files. They stay outside the repository and can hold text or binary content under 5 MB. A project can store up to 100 files.

Bulk downloads can traverse every API page. Deletion and replacement prompt for confirmation; non-interactive runs need --yes or -y for either operation. Replacing a file changes its ID, so a previously saved ID is stale after a successful update. The get command requires GitLab 18.0 or later.

What it helps with

  • upload a configuration file to a GitLab project
  • download secure files for a CI/CD pipeline
  • find a file by name or ID
  • replace a project certificate
  • remove a secret file from a project

Example prompts for the agent

  • Upload ./config.json to the secure files in group/project.
  • Download every secure file from group/project into ./secure-files.
  • Replace signing-certificate.p12 in group/project with ./replacement.p12.

How to install glab-securefile

1Skills CLI (Vercel)

npx skills add vince-winkintel/gitlab-cli-skills --skill glab-securefile -a claude-code

2Manually: put the files in place

~/.claude/skills/glab-securefile/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/glab-securefile/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about glab-securefile

How do I install glab-securefile in Claude Code?

Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-securefile -a claude-code. The skill file is placed at ~/.claude/skills/glab-securefile/SKILL.md.

What does glab-securefile do?

It manages GitLab secure files for CI/CD, with commands to upload, download, update, inspect, list, and remove them.

Which GitLab versions support the file details command?

glab securefile get requires GitLab 18.0 or later. On older instances, files can still be listed or downloaded by ID or name.

Source text

SKILL.md · MIT
---
name: glab-securefile
description: Manage secure files for CI/CD including upload, update, download, list, and delete operations. Use when storing or replacing sensitive files for pipelines, managing certificates, or handling secure configuration files. Triggers on secure file, CI secrets, certificates, overwrite secure file, secure config.
---

# glab securefile

## Overview

```

  Store up to 100 files for secure use in CI/CD pipelines. Secure files are                                             
  stored outside of your project's repository, not in version control.                                                  
  It is safe to store sensitive information in these files. Both plain text                                             
  and binary files are supported, but they must be smaller than 5 MB.                                                   
                                                                                                                        
         
  USAGE  
         
    glab securefile <command> [command] [--flags]  
            
  COMMANDS  
            
    create <name> <path>                                   Upload a new secure file to a project.
    download [<id> | --id <id> | --name <name>] [--flags]  Download one or more secure files from a project.
    get <id> [--flags]                                     Get details of a secure file by ID.
    list [--flags]                                         List secure files in a project.
    remove [<id> | --id <id> | --name <name>] [--flags]    Remove a secure file from a project.
    update <name> <path> [--flags]                         Update a secure file in a project.
         
  FLAGS  
         
    -h --help                          Show help for this command.
    -R --repo                          Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.
```

## Quick start

```bash
glab securefile --help
```

`glab securefile get` requires GitLab 18.0 or later. On older GitLab instances, list or download by ID/name instead of expecting the details endpoint to work.

## Downloading secure files

Use `--all` to download every secure file across all API pages; it is not limited to the first 100 results. Keep checksum verification enabled unless the user explicitly accepts the risk of `--no-verify` or `--force-download`.

```bash
# Download every secure file to a controlled directory
glab securefile download --all --output-dir ./secure-files -R group/project

# Download one file to an absolute path; glab creates missing parents
glab securefile download 1 --path /tmp/secure/file.txt -R group/project

# Download all files to an absolute directory
glab securefile download --all --output-dir /tmp/secure-files -R group/project
```

Treat the destination as sensitive, keep it outside version control, and verify the target project before downloading. Absolute `--path` and `--output-dir` destinations are supported. For `--all`, glab rejects server-provided names that could escape the selected output directory.

## Removing secure files

Secure-file deletion accepts a positional numeric ID, `--id`, or an exact file name via `--name`:

```bash
# Interactive confirmation
glab securefile remove 1
glab securefile remove --id 1
glab securefile remove --name signing-certificate.p12

# Approved non-interactive deletion
glab securefile remove --name signing-certificate.p12 --yes
```

Deletion is permanent. In non-interactive environments, `--yes` / `-y` is required. Resolve and verify the intended project with `-R/--repo` before deleting, and prefer an ID when duplicate or ambiguous naming is possible.

Choose exactly one selector for removal: a positional ID, `--id`, or `--name`. Combining selectors is a hard error, so resolve the intended file first and pass only the one selector you want to use.

## Updating secure files

Update a secure file by its exact stored name and a local replacement path. The command asks for confirmation unless `--yes` / `-y` is set; `overwrite` is an alias.

```bash
# Interactive update
glab securefile update signing-certificate.p12 ./replacement.p12

# Approved non-interactive update in an explicit project
glab securefile update signing-certificate.p12 ./replacement.p12 \
  -R group/project --yes
```

No update occurs when the content is unchanged. A successful update changes the secure file's ID, so subsequent workflows should resolve/download it by `--name` or refresh the ID instead of reusing a stale ID. Confirm the target project, file name, and replacement path before bypassing the prompt.

## Subcommands

See [references/commands.md](references/commands.md) for full `--help` output.

© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills

Similar skills

All skills for Security →

From the same set45

The whole set →
glab-snippet The glab-snippet Claude Code skill creates GitLab snippets from files or stdin text. It activates when a request is to share code or text as a new snippet. CX Codex +1 115installs glab-todo The glab-todo Claude Code skill manages GitLab to-dos through the CLI. It lists assigned or mentioned work and marks selected items as done. CX Codex +1 115installs glab-milestone The glab-milestone Claude Code skill manages GitLab milestones, from creating and editing them to listing, viewing, and deleting them. It activates for release planning and milestone progress tasks. CX Codex +1 114installs glab-iteration glab-iteration — a skill for Claude Code and Codex that manages GitLab iterations. It activates for sprint planning, issue assignment, and progress checks. CX Codex +1 114installs glab-cluster The glab-cluster Claude Code skill manages GitLab Kubernetes clusters and their agents. It activates for cluster connections and Kubernetes integration tasks. CX Codex +1 113installs glab-runner-controller The glab-runner-controller Claude Code skill manages GitLab Runner controllers and their tokens. It activates for requests about controller setup, scopes, or token changes. CX Codex +1 113installs glab-attestation The glab-attestation Claude Code skill works with GitLab attestations and checks software artifact provenance. It activates for requests about artifact verification or supply chain security. CX Codex +1 113installs glab-whatsnew This Claude Code skill displays GitLab CLI release notes through glab whatsnew. It activates for questions about new releases, changes after an upgrade, or notes from a chosen version. CX Codex +1 112installs

Project sponsors

Companies that keep this analytics open