github

Manage GitHub repositories, issues, PRs, and code search via REST API.

8|1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mnlt/teleport --skill github-mnlt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/mnlt/teleport/tree/main/skills/github
Command: npx skills add https://github.com/mnlt/teleport --skill github-mnlt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operate on GitHub via the REST API — repos, PRs, issues, code search, actions, releases. Use when the user wants scripted / cross-repo operations, doesn't have gh installed, or needs behavior the gh CLI doesn't expose cleanly.

Core Features & Use Cases

  • Direct REST access to GitHub data and actions for cross-repo automation and scripted workflow management.
  • Use cases include triaging issues, managing PRs, performing code searches, and reading CI status when the gh CLI is unavailable or limited.
  • Example: automate bulk issue tagging across repositories and aggregate results for a daily report.

Quick Start

Ask me to list open issues in OWNER/REPO.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub issues and PRs across multiple repositories without the gh CLI?

GitHub REST API rate limits are handled through robust error management logic within the automation scripts. Proper API versioning headers and error handling ensure scripted workflows respond correctly to rate limit boundaries and edge cases during cross-repo operations.

Do I need a GitHub token to perform code search and repository management via the REST API?

Yes, you need a GitHub token with appropriate scopes to perform code search and repository management via the REST API. Correct API versioning headers must also be included to authenticate requests and access GitHub data for read and write operations.

What is the best way to read CI status and manage releases when gh is not installed?

The best way to read CI status and manage releases without gh is direct REST API access. This method provides programmatic GitHub interactions for scripted workflows, allowing you to retrieve CI statuses and handle release data when the CLI is insufficient.

Why use direct GitHub REST API calls instead of the gh CLI for scripted workflows?

Use direct GitHub REST API calls instead of the gh CLI when you need behavior the CLI doesn't expose cleanly. Direct REST access facilitates cross-repo automation, complex code searches, and scripted workflows that exceed standard CLI capabilities.