github_api

Automate GitHub repository, issue, PR, release, and Actions operations via REST v3, GraphQL v4, and gh CLI.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill github-api-antonyfmunoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github_api
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/github_api
Command: npx skills add https://github.com/antonyfmunoz/OS --skill github-api-antonyfmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating GitHub repository, issue, PR, release, and Actions operations across both interactive workflows and agent-driven automation without brittle token handling or ad-hoc API scripting.

Core Features & Use Cases

  • Unified GitHub control surface: use REST v3, GraphQL v4, or the gh CLI via a single skill interface for CRUD and operational tasks.
  • Practical automation patterns: run the daily commit-push-pr motion with gh, perform cross-repo API reads/writes with pagination, and gate CI with gh run watch.
  • Operational correctness: apply built-in guidance for authentication, rate limits, ETag/conditional requests, webhook verification, and common GitHub modeling gotchas (issues vs PRs).

Quick Start

Use the github_api skill to list open issues from a repository by asking: "List the first 50 open issues in OWNER/REPO using GitHub API with jq filtering for number and title."

Frequently Asked Questions about github_api

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

FAQPage Schema
How do I automate GitHub pull request and repository operations using the API?

You can automate GitHub pull request and repository operations using REST v3, GraphQL v4, or the gh CLI. This skill provides a unified interface for scripted CRUD, agent-driven cross-repo automation, and CI gating workflows.

What is the best way to handle GitHub API rate limits and pagination in automation scripts?

Handling GitHub API rate limits and pagination requires built-in guidance for safe request patterns, conditional requests with ETags, and GraphQL cost budgeting. This skill applies these patterns to ensure operational correctness during automated workflows.

How do I verify GitHub webhooks and manage dispatch secrets for Actions?

Verifying GitHub webhooks and managing dispatch secrets for Actions are supported through built-in operational guidance. The skill handles webhook verification and secret management workflows to safely automate GitHub operations.

Can I use the gh CLI alongside REST and GraphQL for cross-repo GitHub automation?

Yes, you can use the gh CLI alongside REST v3 and GraphQL v4 through a single unified control surface. This allows you to perform the daily commit-push-pr motion with gh while executing cross-repo API reads and writes with pagination.

Why does my GitHub API script fail when switching between issues and pull requests?

GitHub API scripts often fail due to common modeling gotchas between issues and pull requests. This skill applies built-in guidance to navigate these modeling distinctions, along with correct token and authentication selection.

Do I need pinned API version headers for GitHub REST and GraphQL automation?

Yes, pinned API version headers are required for stable GitHub REST and GraphQL automation. This skill enforces pinned version headers, correct token auth selection, and rate-limit awareness to maintain safe request patterns.