google-connect_skill

This skill guides you through connecting Nexus to Google Workspace, enabling access to Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides.

Python

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill abdullahbeam/nexus-design-abdullah --skill google-connect

SKILL.md10.3 KB

Overview

This skill helps you connect Nexus to Google Workspace services (Gmail, Docs, Sheets, Calendar, Drive, Tasks, Slides) using a guided setup and OAuth flow. It runs a pre-flight config check, walks you through Google Cloud project and OAuth configuration, installs required libraries if needed, and performs authentication. One-time setup grants access to all seven services for ongoing commands and automations.

How this skill works

Every run begins with a config validation script that returns a status code indicating whether credentials are missing, need login, or are ready. Based on that result the skill routes you to full setup, authentication, or a confirmation that Google is already connected. It saves client credentials to a .env file and stores OAuth tokens separately; re-authentication and disconnect flows are provided for token refresh or removal.

When to use it

When you say: “connect google”, “setup google”, or “configure google”
If the config check reports missing credentials (needs full setup)
If the config check reports credentials exist but require login (run OAuth)
To refresh access after token expiry or scope change: “reconnect google”
To remove Nexus access: “disconnect google”

Best practices

Run the pre-flight config check before proceeding to avoid duplicate steps
Create a dedicated Google Cloud project and use descriptive names like “Nexus Integration”
Use Desktop app OAuth client and add your email as a test user on the consent screen
Keep .env entries for GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_PROJECT_ID but keep token files out of version control
If an API fails, enable that specific Google API in the Cloud Console before retrying

Example use cases

First-time setup: guide a user through creating a Google Cloud project, enabling APIs, and saving OAuth credentials
Authenticate an existing setup when the token has expired using the OAuth login flow
Show status when already connected and list available commands for Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides
Disconnect Nexus from Google by removing the stored token while retaining .env credentials for future reuse
Install required Python dependencies automatically before initiating OAuth if libraries are missing

FAQ

It runs a script that returns exit codes: 0=already configured, 1=credentials exist but need login, 2=missing credentials requiring full setup.

Where are client credentials and tokens stored?

Client ID, secret, and project ID are saved to .env at the Nexus root; OAuth tokens are stored in a separate token JSON file ignored by version control.

How do I refresh an expired token?

Run the reconnect flow which executes the OAuth login process to obtain a new token.