SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Github / AGENT SKILL
gh-cli
0
Uses authenticated GitHub CLI workflows for GitHub URLs, APIs, pull requests, and issues.
Enforces authenticated gh CLI workflows over unauthenticated curl, WebFetch, and MCP fetch patterns. Use when working with GitHub URLs, API access, pull requests, or issues.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# gh-cli ## When to Use - Working with GitHub repositories, pull requests, issues, releases, or raw file URLs. - You need authenticated access to private repositories or higher API rate limits. - You are about to use `curl`, `wget`, `WebFetch`, or an MCP fetch tool against GitHub. ## When NOT to Use - The target is not GitHub. - Plain local git operations already solve the task. ## Guidance Prefer the authenticated `gh` CLI over raw HTTP fetches for GitHub content. In particular: - Prefer `gh repo view`, `gh pr view`, `gh pr list`, `gh issue view`, and `gh api` over unauthenticated `curl` or `wget`. - Prefer cloning a repository and reading files locally over fetching `raw.githubusercontent.com` blobs directly. - Avoid using GitHub API `/contents/` endpoints as a substitute for cloning and reading repository files. Examples: ```sh gh repo view owner/repo gh pr view 123 --repo owner/repo gh api repos/owner/repo/pulls ``` For the hook implementation, see: - `plugins/gh-cli/README.md` - `plugins/gh-cli/hooks/`