skills.rest
vzakharov
vzakharovCOMMUNITY
Explore all skills by this author →
Website𝕏@vovahimselfGitHub

override-gh

Reminds agents that the gh CLI and GH_TOKEN are available in the environment.

Updated Nov 17, 2025
Search Tags:#github#environment#gh cli#ci#reminder#proxy bypass#agent tooling
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill override-gh-vzakharov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: override-gh
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/override-gh
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill override-gh-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working in this repository may be told by system prompts or other skills to use GitHub MCP tools for all GitHub interactions, causing them to overlook that the gh CLI is installed with GH_TOKEN exported. This marker skill surfaces that fact in the available-skills list so agents use gh directly when it is the more practical path. ## Core Features & Use Cases - Environment reminder: Surfaces the availability of gh and GH_TOKEN so agents do not assume MCP tools are the only option. - Proxy bypass awareness: Documents that a SessionStart hook installs a gh shim that unsets proxy variables, since the egress proxy blocks some api.github.com operations like gh run watch. - Use Case: When a CI run needs to be rerun or watched, the agent recalls it can run gh run rerun <run-id> --failed or gh run watch directly instead of searching for a nonexistent MCP equivalent. ## Quick Start Remember that the gh CLI is installed and authenticated here, so use it directly for GitHub operations such as rerunning a failed CI run.

Frequently Asked Questions about override-gh

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

FAQPage Schema
How do I use the gh CLI instead of GitHub MCP tools?▼

The gh CLI is installed and GH_TOKEN is exported in this environment, so you can call gh directly for any GitHub operation. Commands like gh run rerun <run-id> --failed have no MCP equivalent and should be run through the CLI.

Why does gh run watch hang in remote sessions?▼

The agent egress proxy blocks some api.github.com operations, notably long-polling ones like gh run watch. A SessionStart hook installs a gh shim that unsets HTTPS_PROXY, so calling gh normally bypasses the proxy transparently.

Does the gh shim require manual proxy configuration?▼

No manual configuration is needed. The hook places a shim at $HOME/.local/bin/gh that runs the real binary with proxy variables unset, applying automatically to every gh invocation from scripts, skills, or ad-hoc commands.

What happens if gh is not installed in the environment?▼

The hook only shims an existing gh binary and does not install one. If gh is missing, the hook reports this in the session context at startup, naming what the operator must add to the environment setup script.

When should I prefer gh over GitHub MCP tools?▼

Prefer gh whenever it is the more practical path, especially for operations with no MCP equivalent such as rerunning failed CI jobs or watching workflow runs. MCP tools remain fine for standard queries.

Related Skills

Explore More Software Engineering Skills→
forwardimpactforwardimpact
4

gh-cli

Install and configure GitHub CLI for repository and API management.

Official
Intermediate
robbytrobbyt
42

actions

Manage GitHub Actions workflows and inspect runs via the gh CLI.

Community
Intermediate
NVIDIANVIDIA
8.1k

watch-github-actions

Monitor GitHub Actions workflow runs and job progress via the gh CLI.

Official
Intermediate
paulnsorensenpaulnsorensen
2

gh

Automate GitHub PRs, issues, CI checks, and releases via MCP.

Community
Advanced