gh-cli

Enforces authenticated gh CLI usage for GitHub API, pull request, and issue workflows.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/IagoPrandi/zeroclaw-plugin --skill gh-cli-iagoprandi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-cli
Source: https://github.com/IagoPrandi/zeroclaw-plugin/tree/main/.claude/skills/solana-dev/ext/trailofbits/.codex/skills/gh-cli
Command: npx skills add https://github.com/IagoPrandi/zeroclaw-plugin --skill gh-cli-iagoprandi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unauthenticated curl or WebFetch calls against GitHub hit low API rate limits, fail on private repositories, and bypass the user's existing credentials. This Skill redirects those patterns to the authenticated gh CLI so GitHub operations work reliably. ## Core Features & Use Cases - Authenticated GitHub Access: Prefers gh commands such as gh repo view, gh pr view, gh issue view, and gh api over raw HTTP fetches. - Local-First File Reading: Recommends cloning a repository and reading files locally instead of fetching raw.githubusercontent.com blobs or using the /contents/ API endpoint. - Use Case: When asked to review a pull request in a private repository, use gh pr view 123 --repo owner/repo to retrieve the PR with full authentication instead of an unauthenticated curl request that would fail. ## Quick Start Use the gh CLI to view pull request 123 in the owner/repo repository and summarize its changes.

Frequently Asked Questions about gh-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I access the GitHub API with authentication from the command line?▼

Use the gh CLI, which authenticates with your GitHub credentials. Commands like gh api repos/owner/repo/pulls, gh pr view, and gh issue view send authenticated requests, avoiding the strict rate limits of unauthenticated curl calls.

What is the best way to read files from a GitHub repository?▼

Clone the repository and read files locally rather than fetching raw.githubusercontent.com blobs or using the GitHub API /contents/ endpoint. Local clones give full context, work with private repositories, and avoid per-file API rate limits.

gh CLI vs curl for GitHub API requests, which should I use?▼

Use gh for GitHub targets because it handles authentication, provides higher rate limits, and offers purpose-built subcommands like gh pr list and gh repo view. Reserve curl or wget for non-GitHub endpoints where gh does not apply.

Why do unauthenticated GitHub API requests fail or get rate limited?▼

GitHub restricts unauthenticated requests to a low hourly rate limit and blocks access to private repositories entirely. Authenticated gh CLI requests use your token, raising the limit and unlocking private resources.

When should I not use the gh CLI?▼

Skip gh when the target is not GitHub, since it only works with GitHub hosts. Plain local git operations like git log or git diff also do not need gh, as they operate on the local clone directly.