gitlab-fetch

Retrieve GitLab wiki, issues, merge requests, and raw files via glab CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill gitlab-fetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-fetch
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/git/skills/gitlab-fetch
Command: npx skills add https://github.com/taptap/agents-plugins --skill gitlab-fetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts and returns readable content from GitLab URLs when direct web fetching is blocked by login gates or access restrictions, avoiding failed web requests and partial renders.

Core Features & Use Cases

  • Parses GitLab URLs to identify hostname, project path, and content type (wiki, issue, merge request, raw file).
  • Uses the glab CLI to retrieve wiki pages, issue descriptions, merge request details, and raw file contents with correct project path encoding.
  • Handles in-repo and cross-repo contexts by adding hostname and repo flags when needed, and surfaces authentication suggestions and API errors for troubleshooting.

Quick Start

Use gitlab-fetch to fetch the content at the provided GitLab URL and return the markdown or raw file contents using the glab CLI.

Frequently Asked Questions about gitlab-fetch

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

FAQPage Schema
How do I read GitLab wiki and merge request content behind a login wall?

To read GitLab content behind a login wall, the Skill parses the provided URL for the hostname and project path, then uses the glab CLI to retrieve wiki pages, merge requests, and issues, returning readable markdown instead of partial web renders.

Can I fetch raw repository files from a self-hosted GitLab instance?

Yes, you can fetch raw repository files from a self-hosted GitLab instance. The Skill parses GitLab URLs to identify the hostname and uses the glab CLI with appropriate flags to retrieve raw file contents across same-repo or cross-repo contexts.

What is the best way to extract GitLab issue descriptions without web scraping?

The best way to extract GitLab issue descriptions without web scraping is using the glab CLI. The Skill identifies the project path from the URL and executes CLI retrieval commands to fetch issue details directly, avoiding failed web requests and login gates.

Why does fetching GitLab content fail when running outside the target repository?

Fetching GitLab content fails outside the target repository because the glab CLI lacks the repository context. The Skill resolves this by parsing the URL and adding the correct hostname and repo flags to the CLI command for cross-repo retrieval.

Do I need the glab CLI installed to fetch GitLab wiki pages and raw files?

Yes, you need the glab CLI installed in your execution environment to fetch GitLab wiki pages and raw files. The Skill relies entirely on the glab CLI for content retrieval rather than direct web scraping or API calls.