switch-google-account

Switch the active Google account in Chrome using google_accounts.json configuration.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/zdpk/skills --skill switch-google-account
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switch-google-account
Source: https://github.com/zdpk/skills/tree/main/dotfiles/skills/custom/util/switch-google-account/switch-google-account
Command: npx skills add https://github.com/zdpk/skills --skill switch-google-account

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switch the active Google account in Chrome when quotas are exhausted or a different account is needed to continue work across Google services.

Core Features & Use Cases

  • Automated account switching: programmatically selects the target account in the Google account switcher.
  • Config-driven: uses a project root google_accounts.json to determine current_active and available accounts.
  • Use Case: seamlessly continue workflows across Google services without manual re-authentication.

Quick Start

Run the switch-google-account skill with an optional target_email to switch to that account.

Frequently Asked Questions about switch-google-account

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

FAQPage Schema
How do I automate switching Google accounts in Chrome when API quota is exhausted?

To switch Google accounts in Chrome via automation, you can use a skill that reads a google_accounts.json configuration file, updates the current active account, and navigates back to the service URL to bypass exhausted quota limits.

Can I specify a target email address when switching Google accounts in Chrome?

Yes, you can switch to a specific Google account in Chrome by providing an optional target email parameter, which the automation uses to select the desired account from your configured list.

Do I need a configuration file to cycle through multiple Google accounts in Chrome?

Yes, cycling through multiple Google accounts requires a project root google_accounts.json file to define available accounts and track the current active account for the automation workflow.

What is the best way to handle cross-project testing with different Google accounts?

The best way to handle cross-project testing with different Google accounts is using config-driven browser automation that programmatically switches the active account, allowing seamless continuation across Google services.

How does automated Google account switching return to the original service URL?

Automated Google account switching updates the current active account in the google_accounts.json configuration file and then uses browser automation steps to navigate back to the original service URL.