Github Custom

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 a simple gh-CLI helper, but there are inconsistencies (missing declared dependency on the gh CLI, no auth guidance, and mismatched metadata) that reduce confidence in its provenance and configuration.

Purpose & Capability

The skill's name/description and SKILL.md consistently describe a gh CLI wrapper for GitHub operations — that purpose is coherent. However, the skill does not declare the gh CLI as a required binary or any authentication variables, which would normally be expected for a GitHub CLI skill.

Instruction Scope

SKILL.md only contains concrete gh CLI commands (pr/checks, run list/view, gh api usage, --json/--jq examples). It does not instruct reading unrelated files, contacting arbitrary external endpoints, or collecting extra system data.

Install Mechanism

This is instruction-only with no install spec and no code files — low install risk. Nothing will be downloaded or written by an installer.

Credentials

No env vars or primary credential are declared, but the gh CLI typically requires authentication (gh auth) or GITHUB_TOKEN/gh config. The absence of any auth guidance or declared credential is an omission. The skill does not request unrelated secrets.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent/system-wide modifications in its instructions or manifest.

What to consider before installing

This skill appears to be a simple set of instructions for using the gh CLI, but there are some red flags you should consider before installing: - The SKILL.md assumes the gh CLI and authenticated GitHub access, but the skill metadata does not declare gh as a required binary nor does it declare any credential variables. Verify the runtime environment will have gh installed and authenticated (gh auth login or a valid GITHUB_TOKEN) before relying on this skill. - The included _meta.json ownerId and slug differ from the registry metadata shown; this mismatch suggests packaging or provenance issues. Prefer skills with a clear homepage or known publisher; contact the publisher or registry to confirm the origin. - Although the instructions are limited to gh commands, gh api and gh run view could access or transmit repository data; only install this skill if you trust the agent's ability to run commands and the repositories it will access. - If you want to reduce risk, restrict the skill to manual invocation (do not allow autonomous invocation) and confirm which repository names the skill will be allowed to operate on. If you can verify the publisher, ensure gh is installed and authenticated, and you accept that the agent may run gh commands against repositories, this skill is usable; otherwise treat it as untrusted until provenance and auth details are clarified.

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