Skills gh-cli
Enforces authenticated gh CLI workflows over unauthenticated curl/WebFetch patterns. Use when working with GitHub URLs, API access, pull requests, or issues.
install
source · Clone the upstream repo
git clone https://github.com/trailofbits/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/trailofbits/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.codex/skills/gh-cli" ~/.claude/skills/trailofbits-skills-gh-cli && rm -rf "$T"
manifest:
.codex/skills/gh-cli/SKILL.mdsource content
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
, or unauthenticated web fetches against GitHub.wget
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
, andgh issue view
over unauthenticatedgh api
orcurl
.wget - Prefer cloning a repository and reading files locally over fetching
blobs directly.raw.githubusercontent.com - Avoid using GitHub API
endpoints as a substitute for cloning and reading repository files./contents/
Examples:
gh repo view owner/repo gh pr view 123 --repo owner/repo gh api repos/owner/repo/pulls
For the original Claude plugin implementation, see:
plugins/gh-cli/README.mdplugins/gh-cli/hooks/