github-issues

Fetch and manage GitHub issues via the GitHub REST API.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/mpelissari/openclaw-backup --skill github-issues-mpelissari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/mpelissari/openclaw-backup/tree/main/skills/skillguard/test-fixtures/legit-api-skill
Command: npx skills add https://github.com/mpelissari/openclaw-backup --skill github-issues-mpelissari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and manage GitHub issues via the GitHub API.

Core Features & Use Cases

  • List and triage issues for a repository.
  • Create new issues with titles, bodies, and labels.
  • Update or close existing issues to reflect status changes.

Quick Start

List open issues for a repository or create a new issue with a title and body.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I automate listing and triaging GitHub issues for a repository?

Automating GitHub issue triage involves using REST API calls to fetch open issues for a repository, enabling automated listing and collaborative tracking without manual web interface interaction.

Can I create new GitHub issues with labels automatically via the API?

Creating GitHub issues via the API supports setting titles, bodies, and labels automatically. This allows DevOps workflows to generate standardized issue tracking entries programmatically.

Do I need a GITHUB_TOKEN to manage issues through REST API calls?

A GITHUB_TOKEN environment variable is required to authenticate REST API calls for managing GitHub issues. This ensures proper access and error handling during listing, creating, and closing operations.

What's the best way to programmatically close or update existing GitHub issues?

Programmatically closing GitHub issues is best handled by sending REST API calls to update issue status. This reflects status changes accurately and automates workflow transitions.

When do I need API automation for GitHub issue tracking and collaboration?

API automation for GitHub issue tracking is needed when DevOps workflows require bulk triage, automated issue creation from system events, or synchronized status updates across multiple repositories.

Why do my automated GitHub issue API calls fail with error handling issues?

GitHub issue API calls fail if the GITHUB_TOKEN is missing or invalid. Proper error handling in REST API requests is required to manage rate limits and authentication failures during automation.