Official agent skill

GitHub Discussion Query

by github in github/gh-aw

Query GitHub discussions with jq filtering and reusable selectors.

OfficialMITAuto-check passed

Install GitHub Discussion Query

skills CLI
$ npx skills add github/gh-aw --skill github-discussion-query -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/gh-aw github-discussion-query --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/gh-aw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/github-discussion-query .claude/skills/github-discussion-query && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-discussion-query
GitHub stars
5.3k
Token cost
~736 tokens
SKILL.md length
204 words
Files
3
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Query GitHub discussions with jq filtering and reusable selectors.

  • SKILL.md covers Important: jq Parameter is…, Usage, Output Format and Requirements
  • Runs Python and Shell scripts from its folder

What it does

GitHub Discussion Query is an agent skill from github/gh-aw, published by the product's own GitHub organization. Query GitHub discussions with jq filtering and reusable selectors.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `query-discussions.py` and `query-discussions.sh`).

It works with GitHub. The repository describes itself as: GitHub Agentic Workflows. The licence is MIT.

Example prompts

  • “/github-discussion-query”

Requirements

  • Python 3
  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit eb63040. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python and Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Discussion Query loads about 736 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 204 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~736

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/gh-aw at commit eb63040, republished under its MIT licence (© github). 204 words, ~736 tokens.

Download SKILL.mdSave it as .claude/skills/github-discussion-query/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
github-discussion-query
description
Query GitHub discussions with jq filtering and reusable selectors.

GitHub Discussion Query Skill

Query GitHub discussions 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 discussions from the current repository or any specified repository.

Basic Query (Returns Schema Only)

To list discussions from the current repository:

bash
./query-discussions.sh
# Returns schema and data size, not full data
Get All Data

To get all discussion data:

bash
./query-discussions.sh --jq '.'
With Repository

To query a specific repository:

bash
./query-discussions.sh --repo owner/repo
With jq Filtering

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

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

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

# Get discussions in a specific category
./query-discussions.sh --jq '.[] | select(.category.name == "Ideas")'

# Get answered discussions
./query-discussions.sh --jq '.[] | select(.answer != null)'

# Count discussions by category
./query-discussions.sh --jq 'group_by(.category.name) | map({category: .[0].category.name, count: length})'
Common Options
  • --limit: Maximum number of discussions 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 discussions with many comments:

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

Get unanswered discussions:

bash
./query-discussions.sh --jq '.[] | select(.answer == null) | {number, title, category: .category.name}'

List discussions with their labels:

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

Find discussions by category:

bash
./query-discussions.sh --jq '.[] | select(.category.name == "Q&A") | {number, title, author: .author.login}'

Get recently updated discussions:

bash
./query-discussions.sh --jq 'sort_by(.updatedAt) | reverse | .[0:10] | .[] | {number, title, updatedAt}'

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)

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .github/skills/github-discussion-query of github/gh-aw.

  • SKILL.md
  • query-discussions.py
  • query-discussions.sh

Open the folder on GitHubat commit eb63040

Compare with similar skills

GitHub Discussion Query next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Discussion Query compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Discussion Query this skillgithub/gh-aw5.3k—~736Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

More from github/gh-aw

All 52 skills in this repo
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Auto-check passed
  • Official

    Designs and verifies a deterministic grader that measures whether a GitHub Agentic Workflow run reached its real-world or repository outcome.

    5.3k GitHub stars~6.8k tokensUpdated today
    Auto-check passed
  • Official

    Scaffolds, edits, reloads and debugs a canvas extension that the GitHub Copilot CLI can open in its side panel.

    5.3k GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Official

    Drives an open pull request to merge-ready from inside a GitHub Copilot cloud agent, resolving review threads and local checks concurrently, without merging or retriggering CI.

    5.3k GitHub stars~3.8k tokensUpdated today
    Auto-check: warnings
  • Official

    Bumps gh-aw's pinned gh-aw-firewall version, rebuilds generated artifacts, and flags upstream spec or schema changes that need follow-up work.

    5.3k GitHub stars~899 tokensUpdated today
    Auto-check passed
  • Official

    Guide to the console struct tag system in gh-aw: headers, titles, number and cost formats, omitempty, and how structs, slices and maps render in the terminal.

    5.3k GitHub stars~736 tokensUpdated today
    Auto-check passed

Works with

Questions about GitHub Discussion Query

What does GitHub Discussion Query do?

Query GitHub discussions with jq filtering and reusable selectors. GitHub Discussion Query is an agent skill from github/gh-aw, published by the product's own GitHub organization. Query GitHub discussions with jq filtering and reusable selectors.

How do I install GitHub Discussion Query in Claude Code?

Run `npx skills add github/gh-aw --skill github-discussion-query -a claude-code`. Or copy the skill folder (.github/skills/github-discussion-query in github/gh-aw) into .claude/skills/github-discussion-query in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Discussion Query in Codex?

Run `npx skills add github/gh-aw --skill github-discussion-query -a codex`. Or copy the skill folder (.github/skills/github-discussion-query in github/gh-aw) into .agents/skills/github-discussion-query in your project. Codex loads it when a task matches its description.

Can I use GitHub Discussion Query in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/gh-aw --skill github-discussion-query -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-discussion-query, .gemini/skills/github-discussion-query, .github/skills/github-discussion-query and .opencode/skills/github-discussion-query in your project.

What does GitHub Discussion Query need to run?

Going by SKILL.md and its folder, GitHub Discussion Query needs Python and a shell for the scripts in its folder. Our summary lists: Python 3; A Bash shell.

Does GitHub Discussion Query access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub Discussion Query safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Discussion Query use?

GitHub Discussion Query is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Discussion Query use?

About 736 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Discussion Query?

Skills that share tags, products or a category with GitHub Discussion Query: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Discussion Query?

github (a GitHub organization, an official publisher) maintains it in github/gh-aw, which has 5,350 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/gh-aw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.