Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Query GitHub issues with jq filtering and reusable selectors.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✗→✓ | ▲ Improved | 385% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 33% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -39% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -6% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -49% | 0% |
Query GitHub issues efficiently with built-in jq filtering.
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.
Use this skill to query issues from the current repository or any specified repository.
To list issues from the current repository:
bash./query-issues.sh # Returns schema and data size, not full data
To get all issue data:
bash./query-issues.sh --jq '.'
To query a specific repository:
bash./query-issues.sh --repo owner/repo
Use the --jq argument to filter and transform the output:
bash# 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})'
--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 infoFind issues with many comments:
bash./query-issues.sh --jq '.[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}'
Get issues assigned to someone:
bash./query-issues.sh --jq '.[] | select(.assignees | length > 0) | {number, title, assignees: [.assignees[].login]}'
List issues with their labels:
bash./query-issues.sh --jq '.[] | {number, title, labels: [.labels[].name]}'
Get project board assignments:
bash./query-issues.sh --jq '.[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}'
Find old issues (created over 30 days ago):
bash./query-issues.sh --jq '.[] | select(.createdAt < (now - 2592000 | strftime("%Y-%m-%dT%H:%M:%SZ")))'
The script outputs JSON by default, making it easy to pipe through jq for additional processing.
gh) authenticatedjq for filtering (installed by default on most systems)Other measured skills in the registry, with their headline benchmark lift.