gh-auth-isolation

Name: gh-auth-isolation
Availability: InStock
Author: acmeleme

Detect GitHub identities and switch gh config contexts per operation.

Updated Nov 11, 2025

Search Tags:#automation #security #github #credentials #multi-account #gh-authentication #identity-isolation

Ready to run

npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill gh-auth-isolation-acmeleme

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-auth-isolation
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/gh-auth-isolation
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill gh-auth-isolation-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely manage multiple GitHub identities (EMU + personal) in agent workflows to prevent cross-account misuse and credential leakage.

Core Features & Use Cases

Detect active GitHub identity (EMU vs personal) in shell/agents.
Route operations to appropriate token contexts without mixing identities.
Use-case: Push to a personal fork from an EMU session without credential leakage.

Quick Start

Switch the active gh config context to the target account before performing any GitHub operation.

Frequently Asked Questions about gh-auth-isolation

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

FAQPage Schema

How do I isolate multiple GitHub identities in automated agent workflows?▼

To isolate multiple GitHub identities, you switch the active gh config context to the target account before performing any GitHub operation. This routes operations to appropriate token contexts without mixing identities.

How does identity detection work for EMU and personal GitHub accounts?▼

Identity detection works by identifying whether the active GitHub identity is an EMU or personal account within shell or agent environments. It implements per-operation context switching to separate these accounts safely.

Can I push to a personal fork from an EMU session without credential leakage?▼

Yes, you can push to a personal fork from an EMU session without credential leakage. The system uses multiple-gh configuration isolation via gh config directories and tokens to prevent cross-account misuse.

What is the best way to manage multiple gh configuration directories for safe token switching?▼

The best way to manage multiple gh configuration directories is by applying per-operation context switching. This isolates tokens for different accounts, ensuring safe token switching across EMU and personal identities.

Why does cross-account credential misuse happen in GitHub automation?▼

Cross-account credential misuse happens when automated agents perform GitHub actions across mixed identities without context isolation. Routing operations to appropriate token contexts prevents this credential leakage.