google-oauth-integration

Name: google-oauth-integration
Availability: InStock
Author: orient-bot

Document Google OAuth architecture for token storage and tool registration.

Updated Aug 23, 2026

Search Tags:#debugging #authentication #api integration #token management #service integration #google oauth

Ready to run

npx skills add https://github.com/orient-bot/orient --skill google-oauth-integration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: google-oauth-integration
Source: https://github.com/orient-bot/orient/tree/main/.claude/skills/google-oauth-integration
Command: npx skills add https://github.com/orient-bot/orient --skill google-oauth-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to setting up and managing Google OAuth integration, ensuring secure access to Google services like Calendar and Gmail within the Orient platform.

Core Features & Use Cases

OAuth Architecture: Understand token storage, refresh mechanics, and environment variable requirements.
Tool Registration: Learn how to register new Google tools for execution.
Debugging: Troubleshoot common issues like "Unknown tool" errors and token access problems.
Use Case: When integrating Google Calendar for meeting scheduling, this Skill helps you correctly configure OAuth credentials, store tokens securely, and ensure the agent can access calendar data without manual intervention.

Quick Start

Follow the symlink setup instructions to ensure multi-package access to Google OAuth tokens.

Frequently Asked Questions about google-oauth-integration

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

FAQPage Schema

How do I set up Google OAuth token storage for accessing Calendar and Gmail APIs?▼

Google OAuth token storage requires configuring environment variables and following symlink setup instructions to ensure multi-package access to tokens for Calendar and Gmail APIs. This architecture allows secure token retrieval and refresh mechanics within the platform.

How does ToolRegistry differ from ToolExecutorRegistry for Google API integration?▼

ToolRegistry and ToolExecutorRegistry manage Google API access differently: ToolRegistry handles tool registration while ToolExecutorRegistry manages execution. This distinction ensures new Google tools are correctly registered for execution and accessible by the agent without manual intervention.

Why am I getting "Unknown tool" errors when accessing Google Calendar or Gmail?▼

"Unknown tool" errors during Google Calendar or Gmail access typically indicate incorrect tool registration. You need to properly register new Google tools using the ToolRegistry and ensure OAuth credentials and environment variables are correctly configured for the agent to access API data.

Can I use Google OAuth integration for secure access to Google Tasks APIs?▼

Yes, Google OAuth integration supports secure access to Google Tasks APIs along with Calendar and Gmail. The integration documents token file locations, symlink requirements, and environment variable configuration to enable the agent to access these Google services automatically.

What's the best way to troubleshoot token access problems with Google OAuth?▼

Troubleshooting Google OAuth token access problems involves verifying token file locations, checking symlink requirements for multi-package access, and validating environment variable configuration. The integration architecture documents these scenarios to help resolve common token access issues.

Do I need environment variables configured before integrating Google OAuth with my tools?▼

Yes, environment variables must be configured before Google OAuth integration to ensure secure access to Google services. The OAuth architecture requires proper environment variable setup and token storage configuration to enable the agent to access Calendar, Gmail, and Tasks APIs without manual intervention.