gcal-oauth-bridgeInteract with the Calendar Bridge — a self-hosted Node.js service that provides a persistent REST API for Google Calendar events. Handles OAuth token auto-re...
Install via ClawdBot CLI:
clawdbot install danielkillenberger/gcal-oauth-bridgeGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/DanielKillenberger/gcal-oauth-bridgeUses known external API (expected, informational)
cloud.google.comAudited Apr 17, 2026 · audit v1.0
Generated Mar 22, 2026
A freelance consultant uses the skill to check upcoming client meetings and project deadlines directly through their AI assistant. It helps them avoid double-booking and plan their week efficiently without manually opening Google Calendar.
A distributed team lead employs the skill to quickly view team-wide events across multiple calendars, such as stand-ups or deadlines, ensuring alignment. It reduces the need for constant calendar checks during busy workdays.
A small business owner integrates the skill to monitor daily appointments and customer bookings via their AI assistant. This streamlines operations by providing instant access to schedule details without switching applications.
A university researcher uses the skill to track upcoming conferences, lab meetings, and grant deadlines. It aids in balancing multiple projects by offering quick calendar insights through voice or text queries.
An individual leverages the skill to manage personal events like family gatherings, workouts, and reminders through their AI assistant. It simplifies daily planning by centralizing calendar access in a conversational interface.
Offer the skill as a free add-on for existing productivity tools, with premium features like advanced analytics or multi-calendar sync available via subscription. This attracts users while generating recurring revenue from power users.
License the skill to companies for internal use, providing enhanced security, custom integrations, and dedicated support. It targets organizations needing reliable calendar access for teams without OAuth hassles.
Provide paid services for setting up and maintaining the Calendar Bridge, including OAuth configuration, server deployment, and troubleshooting. This model caters to non-technical users or businesses lacking IT resources.
💬 Integration Tip
Ensure the Calendar Bridge service is running locally on port 3000 and properly authenticated via OAuth before using the skill; for remote servers, set up SSH tunneling to access the localhost endpoint securely.
Scored Jun 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Host static files on subdomains with optional authentication. Use when you need to serve HTML, images, CSS, JS, or any static content on a dedicated subdomain. Supports file upload, basic auth, quota management, and automatic SSL via Caddy. Commands include sf sites (create/list/delete), sf upload (files/directories), sf files (list/delete).
Use the botauth CLI to list, search, and retrieve secrets from the user's unlocked botauth vault with per-request approval in the desktop app. Use when a tas...
Use when adding, fixing, or improving how an app authenticates users or protects an API, or when using or configuring any Auth0 feature — signing users in and out, sessions and tokens, guarding routes and endpoints, MFA, SSO, Organizations, RBAC, custom domains, Universal Portals for hosted account