gcalendar-setup

Provision Google Apps Script endpoints to expose calendar data to local tools.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/al-stev/field-eng-skills --skill gcalendar-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcalendar-setup
Source: https://github.com/al-stev/field-eng-skills/tree/main/.claude/skills/gcalendar-setup
Command: npx skills add https://github.com/al-stev/field-eng-skills --skill gcalendar-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the one-time deployment and configuration of a Google Apps Script web app that acts as a secure bridge to expose Google Calendar data to the local /gcalendar integration, eliminating manual copy-paste of URLs, keys, and repeated OAuth flows.

Core Features & Use Cases

  • Apps Script Deployment Guide: Step-by-step instructions to create, paste, and deploy the Apps Script code that returns calendar JSON.
  • Secure Key Generation & Storage: Generates a random API key and saves the Apps Script URL and key into the local credentials file (GCALENDAR_APPSCRIPT_URL and GCALENDAR_APPSCRIPT_KEY).
  • CDP + Okta Integration: Uses a Chrome debug instance (CDP) signed into Okta to authenticate and call the Apps Script endpoint for verifying calendar access.
  • Verification & Troubleshooting: Includes verification via a Python helper to list calendars and a troubleshooting section for common authorization and timeout failures.
  • Use Case: Prepare your personal Google account so the /gcalendar skill can read shared and primary calendars for scheduling and availability checks.

Quick Start

Set up my Google Calendar Apps Script endpoint and store the web app URL and API key for use with the /gcalendar integration.

Frequently Asked Questions about gcalendar-setup

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

FAQPage Schema
How do I set up a Google Calendar integration to expose calendar data to local tools?

Deploying a Google Apps Script web app returns calendar JSON data to local tools via a web app URL, a generated API key, and a Chrome CDP Okta-authenticated session for secure access.

How does Chrome CDP and Okta authentication work for reading shared Google Calendars?

Chrome CDP and Okta authentication works by using a running Chrome debug instance signed into Okta to authenticate and call the Apps Script endpoint, verifying primary and shared calendar access.

Do I need Python and uv tooling to verify Google Calendar Apps Script credentials?

Yes, you need local Python and uv tooling to persist and verify credentials, including running a Python helper to list calendars and troubleshoot authorization or timeout failures.

What's the best way to generate and store an API key for an Apps Script web app?

The best way to generate and store an API key for an Apps Script web app is to use automated generation, saving the key and URL into local GCALENDAR_APPSCRIPT_KEY and GCALENDAR_APPSCRIPT_URL variables.

Why does my Google Calendar Apps Script endpoint return an authorization failure?

Your Google Calendar Apps Script endpoint returns an authorization failure when the Chrome debug instance is not signed into Okta, or the GCALENDAR_APPSCRIPT_URL and GCALENDAR_APPSCRIPT_KEY credentials are not properly saved.

Can I use this Apps Script setup for scheduling and availability checks across multiple calendars?

Yes, you can use this Apps Script setup for scheduling and availability checks, as it reads both primary and shared calendars from your personal Google account through the /gcalendar workflow.