GitHub

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

Security Scan

The SKILL.md matches a simple gh-CLI helper, but packaging/metadata mismatches and omission of required binaries/auth declarations are inconsistent and worth verifying before use.

Purpose & Capability

The skill's described purpose (driving GitHub via the gh CLI) matches the instructions. However the skill does not declare required binaries or a primary credential; using gh effectively typically requires the gh binary and GitHub authentication (gh auth / GH_TOKEN). The lack of declared requirements is an inconsistency.

Instruction Scope

SKILL.md only instructs running gh commands and using --repo or URLs. It does not request reading unrelated files, accessing other system paths, or transmitting data to unexpected endpoints. Instruction scope stays within the stated GitHub interactions.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so no downloads or installs are performed by the skill itself (lower surface area).

Credentials

The skill declares no required env vars or credentials, but practical use of gh typically requires authentication (interactive gh auth login or GH_TOKEN) and the gh binary on PATH. The omission could be benign (author assumed environment already prepared) or an oversight; it should be clarified before trusting the skill with authenticated operations.

Persistence & Privilege

The skill does not request always:true, no install, and no modifications to other skills or system-wide config are described.

What to consider before installing

This appears to be a simple helper that tells the agent how to run the gh CLI, but there are a few red flags to check before installing: 1) Verify the skill's source/owner — registry metadata (owner/slug/version) does not match the _meta.json inside the package, which could indicate repackaging or mismatch. 2) Confirm you have the gh CLI and appropriate GitHub credentials available; the skill does not declare these but they are required to perform authenticated actions. 3) Prefer skills that explicitly declare required binaries and primary credentials (e.g., GH_TOKEN or gh auth). 4) Because this skill can run gh commands via the agent, avoid granting high-privilege GitHub tokens; use least privilege (scoped tokens) and consider read-only scopes if appropriate. If you cannot verify the publisher or the metadata discrepancy, treat the skill cautiously or request a corrected package that lists required binaries and credentials.

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)"'