github-api

Route GitHub API operations across REST v3 and GraphQL v4 resource files.

66|20|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/cooker/wxHm --skill github-api-cooker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-api
Source: https://github.com/cooker/wxHm/tree/main/.cursor/skills/github-api
Command: npx skills add https://github.com/cooker/wxHm --skill github-api-cooker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates reliable GitHub API access across REST and GraphQL services, routing operations to specialized resource files for authentication, repositories, issues/PRs, workflows, and security to simplify integrations and automation.

Core Features & Use Cases

  • Intelligent routing: directs API calls to focused resource files based on task (auth, repos, issues/PRs, workflows, security).
  • Multi-protocol support: covers REST API v3 and GraphQL API v4 for comprehensive data access.
  • Use Case: Build GitHub automation tools that authenticate, list repositories, manage issues, and trigger workflows across organizations.

Quick Start

Use the github-api skill to route GitHub API calls through the appropriate resource files (authentication, repositories, issues/PRs, workflows, and security) in your automation.

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 API calls across REST v3 and GraphQL v4?

Routing GitHub API operations to modular resource files enables simultaneous access to REST v3 and GraphQL v4 endpoints for automation. It directs calls to focused modules covering authentication, repositories, issues, workflows, and security.

Can I manage GitHub issues and PRs using GraphQL API v4?

Yes, managing GitHub issues and PRs via GraphQL API v4 is supported through resource-based loading patterns. The system routes operations to specialized resource files ensuring deterministic data access for issues and pull requests.

What is the best way to structure a GitHub integration that handles both repositories and workflows?

Using a resource-based loading pattern is the best way to structure GitHub integrations handling repositories and workflows. It routes operations to modular resource files, enforcing deterministic management across REST and GraphQL endpoints.

Does this GitHub API routing approach support authentication and security operations?

Yes, this GitHub API routing approach supports authentication and security operations. It enforces a resource-based loading pattern with dedicated resource files specifically mapped for both authentication and security tasks.

When do I need resource routing for GitHub API automation?

You need resource routing for GitHub API automation when building integrations requiring deterministic operations across REST v3 and GraphQL v4. It ensures API calls are correctly mapped to authentication, repositories, issues, or workflows.