gh-cli is a short guidance skill for any task that touches GitHub. It tells the agent to use authenticated gh commands such as gh repo view, gh pr view, gh issue view and gh api when it would otherwise reach for curl, wget, WebFetch or an MCP fetch tool.
Authenticated calls reach private repositories and get higher API rate limits. For reading source, the skill prefers cloning the repository and reading files locally.
What You Get
- A rule to prefer gh repo view, gh pr view, gh pr list, gh issue view and gh api for GitHub content
- A rule to clone a repository and read files locally when contents are needed
- A warning against using the GitHub API contents endpoints as a way to read files
- Example commands to copy
Common Use Cases
- Reading a pull request or issue from a private repository
- Listing pull requests without hitting unauthenticated rate limits
- Inspecting a repository’s files in an agent session
- Keeping an agent from fetching raw.githubusercontent.com blobs one at a time
What Makes It Unique
It is small and single-purpose: one habit, using the authenticated CLI for GitHub, written down for the agent. The plugin pairs it with hooks that redirect fetch attempts, so the guidance in the skill is backed by interception in the same package.
Under The Hood
The skill is a single prose file with no scripts. It leads the agent to run gh commands in the shell, which call the GitHub API with your logged-in credentials, and to clone repositories to disk. The hooks that intercept web fetches live in the plugin folder next to the skill and are not part of what this page measures.