Github Tools

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

Instruction-only wrapper for the GitHub `gh` CLI that is internally consistent with its stated purpose and requests no extra credentials or installs.

Purpose & Capability

The name/description (GitHub `gh` CLI helper) matches the SKILL.md instructions (examples for `gh pr`, `gh run`, `gh api`, etc.). The skill does not request unrelated binaries or credentials.

Instruction Scope

The instructions are limited to invoking `gh` commands with --repo or URLs and using --json/--jq for output. They do not instruct reading arbitrary files, accessing unrelated environment variables, or transmitting data to external endpoints outside of GitHub.

Install Mechanism

No install spec or code is included (instruction-only), so nothing is written to disk by the skill itself. Risk from installation is minimal — the user must have the `gh` CLI available separately.

Credentials

The skill declares no required environment variables or credentials. This is proportionate: `gh` itself requires authentication but that is managed outside the skill (e.g., `gh auth`).

Persistence & Privilege

always:false (not force-included). disable-model-invocation is false (normal), so the agent could call the skill autonomously — expected for skills. There is no request to modify other skills or system-wide config.

Assessment

This skill is a set of `gh` CLI usage examples and is coherent with its stated purpose. Before installing/using it: (1) ensure the `gh` CLI is installed and you understand which GitHub account is authenticated (the skill does not provide or require credentials but will use whatever `gh` is configured with), (2) be aware that if you let the agent invoke the skill autonomously it can run any `gh` command allowed by that account (including reading or modifying repositories), and (3) verify repository names and permissions to avoid accidental changes to sensitive org repos. Note: the registry metadata ownerId differs slightly from the _meta.json ownerId in the package — this is a minor inconsistency to be aware of but does not change the functional assessment.

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