glab-job

Manage GitLab CI/CD jobs via the glab CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management and debugging of individual GitLab CI/CD jobs, allowing users to quickly view details, retry failures, and access logs or artifacts.

Core Features & Use Cases

  • Job Inspection: View detailed information about specific CI/CD jobs.
  • Log Access: Retrieve and view trace logs for debugging.
  • Job Control: Retry or cancel individual jobs.
  • Artifact Management: Download artifacts generated by jobs.
  • Use Case: When a specific stage in your CI/CD pipeline fails, use this Skill to inspect the failed job, view its logs to identify the error, and then retry only that specific job.

Quick Start

Use the glab-job skill to view the details of job ID 12345.

Frequently Asked Questions about glab-job

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

FAQPage Schema
How do I view logs for a specific GitLab CI/CD job to debug a pipeline failure?

You can debug GitLab CI/CD pipeline failures by retrieving and inspecting the trace logs of specific jobs. This Skill allows you to access detailed execution logs to identify the exact errors causing a stage to fail.

Can I retry or cancel an individual GitLab CI/CD job without running the whole pipeline?

Yes, you can retry or cancel individual GitLab CI/CD jobs without triggering the entire pipeline. This Skill provides job control features to manage specific job executions directly, saving time when isolated stages fail.

How do I download artifacts generated by a GitLab CI/CD job?

You can download artifacts generated by a GitLab CI/CD job using this Skill's artifact management capabilities. It enables you to retrieve and download the output files produced during specific job executions.

Do I need the GitLab CLI installed to manage CI/CD jobs?

Yes, you need the GitLab CLI (`glab`) installed and authenticated to manage CI/CD jobs. This Skill relies on the `glab` CLI to execute commands for viewing details, retrying, and downloading artifacts.

What is the best way to inspect details of a failed GitLab CI/CD job?

The best way to inspect details of a failed GitLab CI/CD job is using this Skill to view specific job information and retrieve trace logs. It isolates the failed job for targeted debugging and analysis.

Why does retrieving job logs fail when using GitLab CLI?

Retrieving GitLab CI/CD job logs fails if the GitLab CLI (`glab`) is not installed or properly authenticated. Ensure your CLI environment is correctly set up with valid credentials before attempting to access job details.