test display name

Interact with GitHub using the gh CLI to check PR CI status, view workflow runs and logs, and perform advanced API queries with JSON output.

Security Scan

The skill is an instruction-only wrapper for the GitHub CLI (gh) and is internally consistent with that purpose, though it omits a few useful declarations (gh binary and implicit authentication) and has minor metadata inconsistencies you should verify before trusting it.

Purpose & Capability

The SKILL.md describes interacting with GitHub via the gh CLI, which matches the skill name/description. However, the skill does not declare the gh binary as a required dependency even though all commands use it — the binary requirement is implied but not declared.

Instruction Scope

Instructions are limited to running gh commands against repositories, PRs, runs, and the API. They don't instruct reading arbitrary files, scanning unrelated system state, or sending data to external endpoints other than GitHub via gh.

Install Mechanism

No install spec is present (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install pattern and is consistent with the skill's minimal scope.

Credentials

The skill declares no required environment variables or primary credential, but using gh requires the user/agent to be authenticated to GitHub (gh uses stored credentials or GH_TOKEN). The SKILL.md does not explain authentication expectations. This implicit credential requirement is proportional but should be made explicit to users.

Persistence & Privilege

The skill does not request persistent presence (always is false) and contains no code that would modify agent configuration or other skills. Autonomous invocation is allowed by default, which is normal for skills and not a problem here.

Assessment

This skill is basically a set of recipes for using the gh CLI. Before installing/using it: (1) ensure the gh CLI is installed on any agent that will run it; (2) ensure the gh client is authenticated with appropriate GitHub credentials/tokens (use least privilege scopes); (3) verify the skill source/owner (there's a mismatch in the small metadata file vs. registry metadata — confirm the publisher you trust); (4) avoid granting broader tokens than needed since gh api calls can access many repo/org resources; and (5) you can test commands manually on a non-sensitive repo to confirm behavior before enabling autonomous runs.

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'