google-master

Unify OAuth authentication and configuration across Google service integration skills.

2|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/abdullahbeam/nexus-design-abdullah --skill google-master-abdullahbeam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-master
Source: https://github.com/abdullahbeam/nexus-design-abdullah/tree/main/00-system/skills/google/google-master
Command: npx skills add https://github.com/abdullahbeam/nexus-design-abdullah --skill google-master-abdullahbeam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-auth, google-auth-oauthlib, google-api-python-client, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates redundant code, inconsistent authentication flows, and repeated setup documentation across multiple Google service integration skills, removing the need to rebuild OAuth logic, error handling, and configuration steps for each new Google workspace tool.

Core Features & Use Cases

  • Unified OAuth Authentication: Single login grants access to all supported Google services (Gmail, Docs, Sheets, Calendar, Drive, Tasks, Slides) with one securely stored access token.
  • Shared Reference Library: Pre-built setup guides, error troubleshooting documentation, and API pattern references that ensure consistent behavior across all Google skills.
  • Pre-flight Configuration Checks: Built-in scripts that validate dependencies, OAuth credentials, and authentication status before any Google operation, with clear, actionable fix instructions for common issues. Use case: If you are building or maintaining multiple Google workspace automation skills, this library ensures all of them use the same authentication flow, error handling, and setup process, cutting down development time and eliminating inconsistencies.

Quick Start

Any Google integration skill you use automatically leverages this shared library to handle authentication, configuration validation, and error troubleshooting with no manual setup required from you.

Frequently Asked Questions about google-master

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

FAQPage Schema
How do I handle Google Workspace OAuth authentication across multiple Python integrations?

Unified Google Workspace authentication uses a shared backend library to provide a single securely stored OAuth token for all services. This eliminates redundant login flows and standardizes access across Gmail, Sheets, and Drive.

What is the best way to manage Google API credentials for Python automation scripts?

Managing Google API credentials for Python automation is best achieved through a shared configuration infrastructure with pre-flight validation scripts. This setup verifies dependencies and OAuth credentials before operations, ensuring consistent behavior and reducing maintenance overhead.

Do I need to configure google-api-python-client separately for Gmail, Calendar, and Drive?

You do not need to configure google-api-python-client separately for Gmail, Calendar, and Drive. A unified shared backend leverages one OAuth token and shared configuration infrastructure to access all supported Google services automatically.

How do I troubleshoot Google API integration errors and configuration issues?

Troubleshooting Google API integration errors involves using pre-built reference documentation and configuration validation scripts. These tools check authentication status and dependencies before operations, providing clear, actionable fix instructions for common issues.

Can I use a single OAuth token for Google Sheets, Docs, and Slides automation?

You can use a single OAuth token for Google Sheets, Docs, and Slides automation. A unified shared backend library supports consistent, unified access to all supported Google workspace services via one securely stored access token.

Why does my Google Workspace integration skill keep rebuilding authentication logic?

Your Google Workspace integration keeps rebuilding authentication logic because it lacks a shared library. Implementing a unified backend eliminates redundant OAuth code, setup documentation, and error handling logic across multiple Google service tools.