mcpbeat

Github Labels Query

github/github-labels-query

List GitHub repository labels with per_page pagination support.

953 tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
4864
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/github/gh-aw --skill github-labels-query

What comes with it

2 365 bytes besides the instruction
query-labels.sh

The instruction itself

7 sections, as written by the author

GitHub Labels Query Skill

List GitHub repository labels with efficient pagination using the --per-page flag.

Usage

Use this script to list labels from any repository with controlled page sizes.

Basic Usage

./query-labels.sh --owner github --repo gh-aw
# Returns 10 labels (default per_page=10)

Pagination

# Get the first label only
./query-labels.sh --owner github --repo gh-aw --per-page 1

# Get 25 labels starting from page 2
./query-labels.sh --owner github --repo gh-aw --per-page 25 --page 2

Parameters

| Parameter | Required | Default | Description |

|-----------|----------|---------|-------------|

| --owner | Yes | - | Repository owner (username or organization) |

| --repo | Yes | - | Repository name |

| --per-page | No | 10 | Results per page (1–100) |

| --page | No | 1 | Page number |

Output

Returns JSON with the following fields:

{
  "labels": [
    {
      "id": 12345,
      "node_id": "LA_...",
      "url": "https://api.github.com/repos/owner/repo/labels/bug",
      "name": "bug",
      "color": "d73a4a",
      "default": true,
      "description": "Something isn't working"
    }
  ],
  "item_count": 10,
  "per_page": 10,
  "page": 1
}

Source

Calls the GitHub REST API:

GET /repos/{owner}/{repo}/labels?per_page={n}&page={n}

How to use it

Copy the folder

Take github/github-labels-query from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.