google-connect

Configures OAuth credentials and authentication for Google Workspace API integration.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill google-connect-fahadimdad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-connect
Source: https://github.com/FahadImdad/Nexus-Fahad/tree/main/00-system/skills/google/google-connect
Command: npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill google-connect-fahadimdad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-auth, google-auth-oauthlib, google-api-python-client.

What problem does it solve? Setting up Google Workspace integration requires navigating Google Cloud Console, enabling seven separate APIs, configuring OAuth consent screens, and managing credentials — a confusing multi-step process that blocks users from accessing Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides programmatically. ## Core Features & Use Cases - Guided Setup Wizard: Walks users through creating a Google Cloud project, enabling all 7 Google APIs, configuring the OAuth consent screen, and generating OAuth client credentials. - Config Pre-flight Check: Runs a validation script that detects whether credentials are missing, need authentication, or are fully configured, then routes to the correct workflow. - Authentication Management: Handles OAuth login, token refresh, reconnection, and disconnection through shared scripts. - Use Case: A user says "connect google" and is guided step-by-step through Google Cloud setup, after which they can immediately run commands like "list my upcoming calendar events" or "send email". ## Quick Start Say "connect google" to start the setup wizard and link your Google account to Nexus.

Frequently Asked Questions about google-connect

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

FAQPage Schema
How do I connect my Google account to access Gmail and Calendar programmatically?

Run the setup wizard by saying "connect google". It guides you through creating a Google Cloud project, enabling the required APIs, configuring OAuth consent, and saving your Client ID and Secret to a .env file before running the OAuth login flow.

What Google APIs need to be enabled for Workspace integration?

Seven APIs must be enabled in Google Cloud Console: Gmail API, Google Docs API, Google Sheets API, Google Calendar API, Google Drive API, Google Tasks API, and Google Slides API. One OAuth setup grants access to all of them.

Why does Google OAuth show an unverified app warning?

The warning appears because the app uses an External OAuth consent screen without Google verification. It is safe to proceed by clicking Continue, but you must add your own email as a test user in the OAuth consent screen settings first.

How do I fix an expired or invalid Google access token?

Run the reconnect workflow with "reconnect google", which removes the old token and starts a fresh OAuth login flow. If the client credentials themselves are invalid, verify the Client ID and Secret stored in the .env file.

Where are Google OAuth credentials and tokens stored?

The Client ID, Client Secret, and Project ID are stored in a .env file at the Nexus root, while the OAuth access token is saved to 01-memory/integrations/google-token.json. Both locations are excluded from git via .gitignore.