gh-glcp

Standardize GitHub operations for GLCP workflows using the gh CLI.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/ketronkowski/skills --skill gh-glcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-glcp
Source: https://github.com/ketronkowski/skills/tree/main/gh-glcp
Command: npx skills add https://github.com/ketronkowski/skills --skill gh-glcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces access errors for GLCP resources by standardizing GitHub operations through the gh CLI, instead of MCP server tools.

Core Features & Use Cases

  • Guided gh CLI usage for GLCP workflows, PRs, issues, and commits to improve reliability and speed.
  • Best-practice authentication and repository scoping with explicit --repo glcp/<repo> to ensure correct resource access.
  • Use Case: When debugging a failed GLCP workflow, follow gh commands to view runs, logs, and related issues without MCP tooling.

Quick Start

Install and authenticate the gh CLI for GLCP, then run example commands: gh auth login gh run list --repo glcp/<repo> --limit 5

Frequently Asked Questions about gh-glcp

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

FAQPage Schema
How do I view GitHub workflow runs and logs for GLCP without using MCP server tools?

You can view GitHub workflow runs and logs for GLCP by using the gh CLI. Run commands like `gh run list --repo glcp/<repo>` and `gh run view` to inspect execution details and troubleshoot failures directly without relying on MCP server tools.

Why do I get access errors when querying GLCP repositories with GitHub MCP tools?

Access errors often occur because MCP tools lack proper repository scoping. Standardizing GitHub operations through the gh CLI with explicit `--repo glcp/<repo>` flags ensures correct resource access and reduces these authentication and scoping errors.

What is the best way to manage pull requests and issues for GLCP repositories?

The best way to manage pull requests and issues for GLCP is through the gh CLI. Using best-practice flags like `--json` for structured outputs and explicitly scoping commands with `--repo glcp/<repo>` provides reliable and standardized repository management.

Do I need to authenticate the gh CLI separately to interact with GLCP repositories?

Yes, you must authenticate the gh CLI separately before interacting with GLCP repositories. Run `gh auth login` to establish your session, which is a required prerequisite for executing any GitHub operations, workflow checks, or pull request management.

Can I get structured JSON output for GitHub issues and commits in the glcp organization?

Yes, you can get structured JSON output for GitHub issues and commits by using the `--json` flag with your gh CLI commands. This best-practice approach formats repository data reliably for parsing and automation within the glcp organization.

gh CLI not working for GLCP workflows, what are the limitations?

If gh CLI is not working for GLCP workflows, verify the CLI is installed and authenticated, and that all commands include explicit `--repo glcp/<repo>` scoping. Without proper authentication and repository scoping, GitHub operations will fail.