gh-cli

Retrieve GitHub repositories, pull requests, issues, and API data using authenticated gh CLI workflows.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill gh-cli-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-cli
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/gh-cli
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill gh-cli-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unreliable, rate-limited, or access-restricted GitHub retrieval workflows caused by using unauthenticated curl/WebFetch patterns instead of GitHub’s authenticated tooling.

Core Features & Use Cases

  • Authenticated GitHub operations: View repositories, pull requests, issues, releases, and query the GitHub API with proper authentication.
  • Reliable GitHub content retrieval: Prefer cloning and local inspection over downloading raw blobs or using the API contents endpoint as a substitute.
  • Clear decision guidance: Helps you choose when to use gh CLI versus when curl/WebFetch or other approaches are inappropriate.

Quick Start

Run the gh-cli skill to switch your workflow from unauthenticated GitHub calls to authenticated gh commands for repos, PRs, issues, or API requests.

Frequently Asked Questions about gh-cli

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

FAQPage Schema
How do I access private GitHub repositories and avoid API rate limits?

Use authenticated GitHub CLI commands instead of unauthenticated HTTP fetching. The gh CLI provides reliable access to private repositories and pull requests while preventing rate-limiting issues.

Why does fetching raw file blobs from GitHub fail for repository inspection?

Fetching raw file blobs is unreliable for repository inspection because it bypasses authentication. Use gh CLI subcommands like repo view or clone repositories locally to ensure consistent access to GitHub content.

What is the best way to query GitHub API endpoints for pull requests and issues?

The best way to query GitHub API endpoints is using the gh api command. This authenticated approach reliably retrieves pull requests and issues without hitting the access restrictions of unauthenticated calls.

Can I use the GitHub API contents endpoint to replace cloning a repository?

No, you should not use the API contents endpoint as a replacement for cloning. Prefer cloning repositories and performing local reads, using gh CLI for viewing releases, issues, and pull requests.

When should I use gh CLI instead of curl or WebFetch for GitHub tasks?

Use gh CLI for any task involving GitHub repository inspection, pull requests, issues, releases, or API access. Avoid curl or WebFetch patterns because they cause unreliable, rate-limited, or access-restricted GitHub retrieval workflows.