github-issues

Retrieve, create, and close GitHub issues via the REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually checking, creating, and closing GitHub issues by giving you a simple API-driven workflow for issue management.

Core Features & Use Cases

  • List Issues: Retrieve open or closed issues from any repository for triage and reporting.
  • Create Issues: Open new issues with titles, descriptions, and labels directly from an AI workflow.
  • Close Issues: Mark issues as closed when work is complete or no longer relevant.
  • Use Case: A developer lead can quickly review backlog status, file follow-up bugs, and close resolved tickets without leaving the chat environment.

Quick Start

Use the github-issues skill to list open issues for the repository octocat/hello-world.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I manage GitHub issues from an automated workflow?

You can manage GitHub issues through authenticated REST API calls that list, create, and close repository tickets. This workflow requires a valid GITHUB_TOKEN and curl availability to perform requests for developer support and project coordination.

How do I retrieve open issues for repository triage using the API?

Retrieve open issues for repository triage by making authenticated API calls against the GitHub REST API. This process requires setting up a GITHUB_TOKEN and using curl to pull issue data for backlog review and reporting.

What's the best way to automate GitHub issue creation and closure?

Automating GitHub issue creation and closure is best handled through API-driven workflows that open issues with titles and labels, then mark them closed when work is complete. This requires GITHUB_TOKEN authentication and curl for REST API requests.

Do I need a GITHUB_TOKEN to list and close repository issues?

Yes, you need a GITHUB_TOKEN to authenticate requests against the GitHub REST API for listing and closing repository issues. Curl availability is also required to perform the authenticated API calls for these triage workflows.

Can I open new issues with labels directly from an AI environment?

Yes, you can open new issues with titles, descriptions, and labels directly from an AI workflow. This is achieved through authenticated GitHub REST API calls that handle issue creation for project coordination and developer support.

Why does my GitHub issues API workflow require curl availability?

Your GitHub issues API workflow requires curl availability because the Skill performs authenticated requests against the GitHub REST API using this command-line tool. Along with a GITHUB_TOKEN, curl enables the retrieval and management of repository issues.