gh-auth-isolation

Isolate GitHub authentication across multiple user accounts in AI agents.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/barichter/squad --skill gh-auth-isolation-barichter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-auth-isolation
Source: https://github.com/barichter/squad/tree/main/.squad/skills/gh-auth-isolation
Command: npx skills add https://github.com/barichter/squad --skill gh-auth-isolation-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of safely managing multiple GitHub identities in AI agent workflows, preventing credential mix-ups and ensuring secure operations across different accounts.

Core Features & Use Cases

  • Identity Detection: Detects the active GitHub identity and provides context for operations.
  • Token Extraction: Extracts specific account tokens for secure, single-operation access.
  • Remote Push: Enables pushing to personal repositories from an EMU shell.
  • PR Creation: Creates pull requests on personal forks from an EMU context.
  • Config Isolation: Offers directory isolation for complete account separation.
  • Shell Aliases: Provides shell aliases for quick account switching.
  • Use Case: For developers using both a personal and an EMU GitHub account, this Skill helps maintain secure and separated operations.

Quick Start

Use the gh-auth-isolation skill to switch to your personal GitHub account for an 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 manage multiple GitHub accounts in automated agent workflows?

Manage multiple GitHub accounts in automated agent workflows by isolating authentication credentials, extracting specific account tokens, and applying directory isolation to prevent identity mix-ups during secure operations.

How does token extraction work for GitHub identity switching?

Token extraction for GitHub identity switching works by pulling specific account tokens for single-operation access, enabling actions like pushing to personal repositories from an enterprise shell context.

Do I need the GitHub CLI to isolate authentication for AI agents?

Yes, you need the GitHub CLI installed to isolate authentication for AI agents, as this Skill relies on it to handle specific token operations and manage secure account switching.

Can I create pull requests on personal forks from an EMU GitHub context?

Yes, you can create pull requests on personal forks from an EMU GitHub context by applying remote push capabilities and extracting the correct personal account token for the operation.

What is the best way to separate enterprise and personal GitHub credentials?

The best way to separate enterprise and personal GitHub credentials is directory isolation, which achieves complete account separation alongside shell aliases for quick switching in agent workflows.

Why do my GitHub credentials mix up when running automated workflows?

GitHub credentials mix up in automated workflows when multiple identities lack isolated configuration, an issue resolved by applying directory isolation and specific token handling for each operation.