shimmy-tool-gh

Guide GitHub CLI usage and maintenance within Shimmy container wrappers.

2|Updated Feb 14, 2026

Search Tags:#authentication #github cli #tool maintenance #shimmy #container wrappers #environment forwarding

Ready to run

npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shimmy-tool-gh
Source: https://github.com/wadebee/shimmy/tree/main/tools/gh/agent
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you use and maintain the GitHub CLI inside Shimmy’s context-first container wrappers, so GitHub workflows stay consistent with the repository’s runtime and profile rules.

Core Features & Use Cases

GitHub CLI Workflow Guidance: Follow the canonical Shimmy instructions for GitHub CLI usage, including persistent authentication and GH_* environment forwarding.
Context-Aware Maintenance: Work within the tool’s layered context files to preserve the correct runtime behavior and local-image setup.
Use Case: Use this Skill when you need to update, troubleshoot, or operate the GitHub CLI wrapper without breaking Shimmy’s containerized execution model.

Quick Start

Ask for help using or updating the GitHub CLI Shimmy tool while preserving its configuration persistence and local-image behavior.

Frequently Asked Questions about shimmy-tool-gh

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

FAQPage Schema

How do I manage GitHub CLI authentication persistence inside container wrappers?▼

To manage GitHub CLI authentication persistence inside container wrappers, you need to follow Shimmy's context-first instructions for GH_* environment forwarding and read repository context files to preserve configuration persistence.

What is the best way to maintain GitHub CLI configuration in a containerized runtime?▼

The best way to maintain GitHub CLI configuration in a containerized runtime is to work within Shimmy's layered context files, preserving the correct local-image setup and runtime behavior during updates or troubleshooting.

How do I update the GitHub CLI wrapper without breaking containerized execution?▼

To update the GitHub CLI wrapper without breaking containerized execution, you must read the tool's layered context files and apply updates that preserve Shimmy's local-image behavior and configuration persistence rules.

Why does my GitHub CLI environment forwarding fail inside containerized workflows?▼

GitHub CLI environment forwarding fails inside containerized workflows when repository context files are not properly read, preventing Shimmy from applying its context-first rules for persistent authentication and GH_* variable forwarding.

Can I use GitHub CLI workflows with local-image behavior in Shimmy tool wrappers?▼

Yes, you can use GitHub CLI workflows with local-image behavior in Shimmy tool wrappers by following canonical instructions that ensure environment forwarding and GitHub config persistence operate correctly within the container runtime.