Skip to main content
skill CX Codex

glab-schedule — Claude Code skill for GitLab CI/CD schedules

The glab-schedule Claude Code skill manages GitLab CI/CD pipeline schedules. It activates for requests to create, inspect, change, delete, or run a scheduled pipeline.

MIT 117 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-schedule -a claude-code
Open on GitHub

What glab-schedule does

The skill uses glab schedule to create, list, update, delete, and run GitLab CI/CD pipeline schedules. The list command can return JSON for agent workflows.

JSON output contains only the fetched page, even when the list header reports a total across pages. Use --page and --per-page to fetch more. Schedule variable keys are checked before creation, and empty keys are rejected. The GitLab CLI glab is required.

What it helps with

  • create a GitLab CI/CD pipeline schedule
  • retrieve schedules as JSON
  • change or delete a schedule by ID
  • run a scheduled pipeline

Example prompts for the agent

  • Create a GitLab CI/CD pipeline schedule.
  • List pipeline schedules as JSON.
  • Run the schedule with ID 42.

How to install glab-schedule

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

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

Questions about glab-schedule

How do I install glab-schedule in Claude Code?

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

What does glab-schedule do?

It manages GitLab CI/CD pipeline schedules through glab schedule, including creating, listing, updating, deleting, and running them.

What does the JSON schedule list contain?

glab schedule list --output json returns the fetched page only. Use --page and --per-page to retrieve later pages.

Source text

SKILL.md · MIT
---
name: glab-schedule
description: Manage CI/CD pipeline schedules including create, list, update, delete, and run scheduled pipelines. Use when automating pipelines, setting up cron jobs, or managing scheduled builds. Triggers on schedule, scheduled pipeline, cron, pipeline schedule, automated build.
---

# glab schedule

## Overview

```

  Work with GitLab CI/CD schedules.
  USAGE
    glab schedule <command> [command] [--flags]
  COMMANDS
    create [--flags]       Schedule a new pipeline.
    delete <id> [--flags]  Delete the schedule with the specified ID.
    list [--flags]         Get the list of schedules.
    run <id>               Run the specified scheduled pipeline.
    update <id> [--flags]  Update a pipeline schedule.
  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 schedule --help
```

## Structured output

`glab schedule list` supports `--output json` / `-F json` for structured output, which is useful for agent automation.

The human list header uses the API-reported total across pages rather than treating the current page length as the total. JSON still contains only the fetched page of schedules; use `--page` and `--per-page` to inspect subsequent pages. Do not mistake the header's total for a fully fetched inventory, and do not create, update, run, or delete schedules as part of a read-only audit.

```bash
# List schedules with JSON output
glab schedule list --output json
glab schedule list -F json
```

## Schedule variables

Schedule variable keys are validated before schedule creation. Empty keys are rejected, so check generated `--variable <key>:<value>` input before creating schedules.

## 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 Automation and no-code: n8n, Zapier, Make →

From the same set45

The whole set →
glab-label The glab-label Claude Code skill manages GitLab labels at project and group level. It responds to requests to create, inspect, edit, or remove labels for issues and merge requests. CX Codex +1 118installs glab-gpg-key glab-gpg-key — a skill for Claude Code that manages GPG keys on GitLab. Automates adding, listing, and deleting keys when setting up commit signing or verifying commit signatures. CX Codex +1 118installs glab-alias The glab-alias Claude Code skill manages aliases for the GitLab CLI, glab. Ask it to create, show, or remove a shortcut command. CX Codex +1 118installs glab-quick-actions The glab-quick-actions Claude Code skill sends GitLab quick actions through glab. It groups changes to an issue or merge request into a single comment. CX Codex +1 118installs glab-incident The glab-incident Claude Code skill manages GitLab incidents through glab. It activates for requests to create incidents, handle incident response, or connect incidents with issues. CX Codex +1 117installs glab-completion This Claude Code skill generates glab completion scripts for bash, zsh, fish, and PowerShell. It activates when configuring shell command suggestions. CX Codex +1 117installs glab-orbit The glab-orbit Claude Code skill runs Orbit CLI through glab. It activates for remote GitLab graph queries and searches across a local code graph. CX Codex +1 117installs glab-duo The glab-duo Claude Code skill installs and runs GitLab Duo CLI through glab. It activates for terminal access to GitLab Duo Agent Platform, interactive sessions, or a bounded headless task. CX Codex +1 116installs

Project sponsors

Companies that keep this analytics open