skills.rest
CommunityToolkit
CommunityToolkitOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gh-auth-isolation

Manage GitHub authentication for multi-account workflows with secure context switching.

619|188|Updated Jul 4, 2024
Search Tags:#authentication#GitHub#account management#credential isolation#multi-account workflow
One-click install
npx skills add https://github.com/CommunityToolkit/Aspire --skill gh-auth-isolation-communitytoolkit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-auth-isolation
Source: https://github.com/CommunityToolkit/Aspire/tree/main/examples/squad/CommunityToolkit.Aspire.Hosting.Squad.AppHost/dev-squad/.squad/templates/skills/gh-auth-isolation
Command: npx skills add https://github.com/CommunityToolkit/Aspire --skill gh-auth-isolation-communitytoolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of GitHub identity management in workflows, ensuring that multiple accounts, especially Enterprise Managed Users (EMU) and personal accounts, can operate safely and separately without credential leakage or permissions conflicts.

Core Features & Use Cases

  • Identity Detection: Automatically identify the active GitHub account before operations to prevent credential misuse.
  • Context Switching: Securely switch between GitHub account contexts (EMU, personal, etc.) without credential persistence.
  • Token Extraction: Safely extract tokens for specific accounts without compromising credentials.
  • Push to Personal Repos: Enable pushing to personal repositories while using an EMU account.
  • PR Creation on Forks: Create pull requests on personal forks without interference from EMU accounts.
  • Config Directory Isolation: Use separate configuration directories for each account to maintain strict separation of environments.
  • Shell Aliases: Provide quick switching between accounts with shell aliases for convenience.
  • Use Case: In a scenario where AI agents are used across multiple GitHub accounts for work and open-source projects, this skill ensures secure, conflict-free interactions and seamless operation across all accounts.

Quick Start

Use the gh-auth-isolation skill to switch to your personal GitHub account and push changes to a repository using a specific token.

Frequently Asked Questions about gh-auth-isolation

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

FAQPage Schema
How do I switch between GitHub EMU and personal accounts in automated workflows?▼

You can switch between GitHub EMU and personal accounts in automated workflows using secure context switching. This mechanism isolates credentials and prevents leakage by using separate configuration directories for each account.

How do I push to personal GitHub repositories while using an EMU account?▼

You can push to personal repositories while using an EMU account by leveraging safe token extraction. The workflow isolates the specific account token needed, ensuring your personal push operations execute without EMU credential interference.

Can AI agents manage multi-account GitHub workflows without credential conflicts?▼

Yes, AI agents can manage multi-account GitHub workflows without credential conflicts. The system automatically detects the active GitHub account before operations, maintaining strict separation between Enterprise Managed Users and personal accounts.

What is the best way to create pull requests on personal forks without EMU interference?▼

The best way to create pull requests on personal forks without EMU interference is to use isolated config directories. This approach safely extracts the correct personal account token, preventing Enterprise Managed User permissions from blocking fork operations.

Does GitHub credential isolation require manual token extraction for each account switch?▼

No, GitHub credential isolation does not require manual token extraction for each switch. The workflow safely extracts tokens automatically and provides shell aliases for quick, convenient switching between accounts without credential persistence.

Why do my GitHub permissions conflict when running scripts across different accounts?▼

GitHub permissions conflict when running scripts across different accounts because of credential persistence and shared configurations. Isolating configuration directories for each account prevents this overlap, ensuring strict separation of environments.

Related Skills

Explore More Software Engineering Skills→
math-incmath-inc
1.2k

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Official
Intermediate
jasonkneenjasonkneen
471

openclicky-repo-operator

Automate GitHub repository management with Git commands and the GitHub API.

Community
Advanced
yuhle-qugyuhle-qug

github-actions-expert

Optimize GitHub Actions workflows with security hardening and automation patterns.

Community
Advanced
ma08ma08
28

gws-account-switch

Switch Google Workspace accounts for gws CLI by selecting credential files and setting environment variables.

Community
Intermediate