gh

Configure GitHub CLI authentication and automate repository operations via GraphQL or REST.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill gh-vh2224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/github-workflows/references/gh
Command: npx skills add https://github.com/vh2224/forge-executor --skill gh-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer, PyGithub, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the friction of setting up and operating GitHub CLI-based workflows in agent environments, especially when repositories use local proxy remotes and GitHub tooling is not preconfigured.

Core Features & Use Cases

  • GitHub CLI setup and auth: Installs or uses gh, verifies authentication, and falls back safely when needed.
  • Repository-aware GitHub operations: Handles issues, pull requests, releases, workflow runs, labels, milestones, and Projects V2 with the correct repository targeting.
  • Workflow automation: Supports scripted project setup, milestone transitions, issue lifecycle management, and cleanup of experiment-created resources.
  • Use Case: An agent needs to create labels, open issues, move milestones forward, and update project status without failing in a proxy-based GitHub environment.

Quick Start

Ask the agent to install and configure gh for this repository, then create the required labels, milestone, or issue workflow you want to manage.

Frequently Asked Questions about gh

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

FAQPage Schema
How do I automate GitHub CLI operations in proxy-based repository environments?

Automate GitHub CLI operations by configuring gh access with GITHUB_TOKEN authentication and applying -R repository targeting to manage issues, pull requests, and milestones in proxy-based environments.

Why does remote detection fail when running GitHub workflow automation in agent environments?

Remote detection fails in agent environments when gh is missing or local proxy remotes are used. This Skill installs gh, verifies authentication, and applies explicit -R repository targeting to resolve detection failures.

How do I manage GitHub Projects V2 and milestones using CLI commands?

Manage GitHub Projects V2 and milestones using gh CLI by executing GraphQL or REST API calls with GITHUB_TOKEN authentication and -R repository targeting to update project status and move milestone transitions forward.

Do I need GITHUB_TOKEN and gh installed to manage issues and labels via GitHub automation?

Yes, GITHUB_TOKEN authentication and the gh CLI are required to manage issues, labels, releases, and workflow runs. This Skill installs or uses gh and verifies authentication before applying repository-aware operations.

What's the best way to clean up experiment-created GitHub resources like labels and issues?

Clean up experiment-created GitHub resources by running scripted project setup and issue lifecycle management through gh CLI automation, ensuring correct repository targeting with -R flags to remove unwanted labels and issues safely.

Can I use GitHub CLI to automate workflow runs and releases in proxy-based repositories?

Yes, you can automate workflow runs and releases in proxy-based repositories by using gh CLI with GITHUB_TOKEN authentication and -R repository targeting, which ensures commands execute against the correct remote repository.