gitlab-group-exploration

Explore GitLab groups and projects via authenticated glab API requests.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill gitlab-group-exploration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-group-exploration
Source: https://github.com/cajias/claude-skills/tree/main/skills/gitlab-group-exploration
Command: npx skills add https://github.com/cajias/claude-skills --skill gitlab-group-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect private or internal GitLab namespaces when browser-based access or WebFetch fails, so you can still discover projects, subgroups, and group metadata programmatically.

Core Features & Use Cases

  • Project Listing: Retrieve every project under a GitLab group or subgroup path.
  • Group Discovery: Check whether a namespace contains subgroups and inspect group-level details like visibility and description.
  • Enterprise GitLab Support: Work against authenticated, non-gitlab.com instances such as internal company hosts.
  • Use Case: You have a GitLab group URL from an internal instance and need a complete inventory of projects, URLs, and recent activity without using the web UI.

Quick Start

Ask for the GitLab group path you want to explore and have the skill list its projects, subgroups, and key metadata using authenticated glab API calls.

Frequently Asked Questions about gitlab-group-exploration

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

FAQPage Schema
How do I list all projects in a private GitLab group when the web UI is blocked?

To list projects in private GitLab groups when browser access is blocked, use authenticated glab API requests to retrieve project metadata programmatically. This approach queries the API directly with URL-encoded group paths and jq filtering.

Can I discover subgroups and namespace details on an enterprise GitLab instance?

Yes, you can discover subgroups on enterprise GitLab instances by executing glab API calls against custom hostnames. This allows authenticated namespace inspection to retrieve group-level details like visibility and description from internal company hosts.

Does GitLab group exploration work with custom hostnames and authenticated API calls?

GitLab group exploration works with custom hostnames by using authenticated glab API calls. It applies to private, internal, and enterprise instances, requiring URL-encoded group paths to successfully retrieve namespace and project metadata.

What is the best way to get a complete project inventory from a GitLab group URL?

The best way to get a complete project inventory from a GitLab group URL is using glab API requests with jq filtering. This produces structured results containing project URLs and recent activity without needing web UI access.

Why does WebFetch fail on private GitLab namespaces and how do I retrieve metadata anyway?

WebFetch fails on private GitLab namespaces due to authentication requirements and browser access restrictions. You can retrieve metadata anyway by using glab API requests that apply authenticated tokens to query group and project details directly.

Do I need glab installed to inspect GitLab groups without browser access?

Yes, you need glab installed and configured with authentication tokens to inspect GitLab groups without browser access. The Skill relies on glab API requests and jq filtering to produce structured metadata results from private namespaces.