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's instructions match its description (using the gh CLI to interact with GitHub) and it doesn't request unrelated access or install code, though it omits declaring the gh CLI and authentication details.

Purpose & Capability

The name/description (GitHub via gh CLI) align with the runtime instructions. However, the metadata does not declare the gh binary as a required dependency nor does it mention authentication (e.g., GH_TOKEN or gh auth), which is a likely omission rather than a mismatch in purpose.

Instruction Scope

SKILL.md only instructs running gh commands and using gh api/--json/--jq for queries; it does not direct the agent to read unrelated files, send data to third-party endpoints, or access unrelated environment variables.

Install Mechanism

No install spec is provided (instruction-only), which is the lowest-risk pattern — nothing is downloaded or written to disk by the skill itself.

Credentials

The skill declares no required environment variables, but practical use requires GitHub authentication (gh uses local auth or GH_TOKEN). The absence of declared credential requirements is an omission the user should be aware of; the skill will operate with whatever GitHub credentials are available to the environment.

Persistence & Privilege

always is false and the skill is user-invocable/autonomous invocation is allowed (the platform default). The skill does not request persistent system-wide privileges or modify other skills' configs.

Assessment

This skill is an instruction-only wrapper for the gh CLI. Before installing: ensure the machine running the agent has the gh CLI and is authenticated to GitHub (gh auth or GH_TOKEN). If you don't want the agent to access your GitHub account, don't install it or provide credentials. Prefer using a token with minimal scopes (repo/read or narrower) and consider a dedicated account or limited-scope token for automation. Note the skill omitted declaring the gh binary and auth requirements, which is likely an oversight rather than malicious behavior.

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