Github Issue Query Agent Skill

by github

Query GitHub issues with jq filtering and reusable selectors.

2k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

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-issue-query

What comes with it

4 042 bytes besides the instruction

query-issues.sh

The instruction itself

11 sections, as written by the author

GitHub Issue Query Skill

Query GitHub issues efficiently with built-in jq filtering.

Important: jq Parameter is Optional

The --jq parameter is optional. Without --jq, this skill returns schema and data size information instead of full data.

Use this to avoid oversized responses and inspect structure before targeted queries.

Use --jq '.' to get all data, or use a more specific filter for targeted results.

Usage

Use this skill to query issues from the current repository or any specified repository.

Basic Query (Returns Schema Only)

To list issues from the current repository:

./query-issues.sh
# Returns schema and data size, not full data

Get All Data

To get all issue data:

./query-issues.sh --jq '.'

With Repository

To query a specific repository:

./query-issues.sh --repo owner/repo

With jq Filtering

Use the --jq argument to filter and transform the output:

# Get only open issues
./query-issues.sh --jq '.[] | select(.state == "OPEN")'

# Get issue numbers and titles
./query-issues.sh --jq '.[] | {number, title}'

# Get issues by a specific author
./query-issues.sh --jq '.[] | select(.author.login == "username")'

# Get issues with specific label
./query-issues.sh --jq '.[] | select(.labels | map(.name) | index("bug"))'

# Count issues by state
./query-issues.sh --jq 'group_by(.state) | map({state: .[0].state, count: length})'

Common Options

--state: Filter by state (open, closed, all). Default: open
--limit: Maximum number of issues to fetch. Default: 30
--repo: Repository in owner/repo format. Default: current repo
--jq: (Optional) jq expression for filtering/transforming output. If omitted, returns schema info

Example Queries

Find issues with many comments:

./query-issues.sh --jq '.[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}'

Get issues assigned to someone:

./query-issues.sh --jq '.[] | select(.assignees | length > 0) | {number, title, assignees: [.assignees[].login]}'

List issues with their labels:

./query-issues.sh --jq '.[] | {number, title, labels: [.labels[].name]}'

Get project board assignments:

./query-issues.sh --jq '.[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}'

Find old issues (created over 30 days ago):

./query-issues.sh --jq '.[] | select(.createdAt < (now - 2592000 | strftime("%Y-%m-%dT%H:%M:%SZ")))'

Output Format

The script outputs JSON by default, making it easy to pipe through jq for additional processing.

Requirements

GitHub CLI (gh) authenticated
jq for filtering (installed by default on most systems)

Other skills for the same job

different authors, same section of the catalogue

Bioservices

by christophacham

×3

Unified Python interface to 40+ bioinformatics services. Use when querying multiple databases (UniProt, KEGG, ChEMBL, Reactome) in a single workflow with consistent API. Best for cross-database analysis, ID mapping across services. For quick single-database lookups use gget; for sequence/file manipulation use biopython.

Python library for working with geospatial vector data including shapefiles, GeoJSON, and GeoPackage files. Use when working with geographic data for spatial analysis, geometric operations, coordinate transformations, spatial joins, overlay operations, choropleth mapping, or any task involving reading/writing/analyzing vector geographic data. Supports PostGIS databases, interactive maps, and integration with matplotlib/folium/cartopy. Use for tasks like buffer analysis, spatial joins between datasets, dissolving boundaries, clipping data, calculating areas/distances, reprojecting coordinate systems, creating maps, or converting between spatial file formats.

Fast CLI/Python queries to 20+ bioinformatics databases. Use for quick lookups: gene info, BLAST searches, AlphaFold structures, enrichment analysis. Best for interactive exploration, simple queries. For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices.

Direct REST API access to UniProt. Protein searches, FASTA retrieval, ID mapping, Swiss-Prot/TrEMBL. For Python workflows with multiple databases, prefer bioservices (unified interface to 40+ services). Use this for direct HTTP/REST work or UniProt-specific control.

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

2k tokens

Moodle External API Development

by ComeOnOliver

×2

Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.

How to use it

Copy the folder

Take github/github-issue-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.