google-direct-oauth

Authenticate Google OAuth for Gmail and Calendar with local token storage.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill google-direct-oauth-uniquecrete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-direct-oauth
Source: https://github.com/Uniquecrete/ThinkFasterv1/tree/main/Skills/zo-google-direct-oauth
Command: npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill google-direct-oauth-uniquecrete

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It solves the problem of getting secure, direct access to your Google Calendar and Gmail without relying on third-party OAuth providers or intermediaries.

Core Features & Use Cases

  • Direct OAuth for Google APIs: Connects to Google Calendar and Gmail using your own Google Cloud OAuth credentials.
  • Local credential storage: Saves OAuth artifacts on the Zo Computer at /home/.z/google-oauth/ for reuse by other Zo skills.
  • Token refresh daemon: Runs a background service that refreshes tokens every 4 hours so access stays reliable.

Use Case: When you need Zo to read recent emails and list events from your calendar using direct Google Calendar API and Gmail API access backed by long-lived refresh tokens.

Quick Start

Tell Zo: upload your Google OAuth client JSON credentials file and run the setup flow so it can authorize, store tokens locally, and start the refresh daemon.

Frequently Asked Questions about google-direct-oauth

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

FAQPage Schema
How do I set up direct Google OAuth for Gmail and Calendar API access?

To set up direct Google OAuth for Gmail and Calendar API access, you upload your Google Cloud OAuth client JSON credentials file to authorize the connection, store tokens locally, and start a refresh daemon.

Does this Google OAuth integration require third-party providers?

No, this Google OAuth integration does not require third-party providers. It connects directly to Gmail and Google Calendar using your own Google Cloud OAuth credentials for secure API access.

How does the token refresh daemon maintain stable Google API access?

The token refresh daemon maintains stable Google API access by running a background service that automatically refreshes OAuth tokens every four hours, ensuring long-running sessions remain reliable.

Where are Google OAuth tokens stored for reuse by other skills?

Google OAuth tokens are stored locally on your computer at `/home/.z/google-oauth/`. This local credential storage allows other compatible skills to reuse the authenticated API access.

Can I use my own Google Cloud Console credentials to read emails and list calendar events?

Yes, you can use your own Google Cloud Console credentials to read recent emails and list calendar events. The integration handles OAuth callback and token exchange for required Google API scopes.

What are the limitations of using direct OAuth for Google Calendar and Gmail APIs?

A limitation of using direct OAuth is that you must provide and manage your own Google Cloud OAuth credentials. Additionally, stable access requires a continuously running token refresh daemon for long-lived sessions.