gmail-oauthSet up Gmail API access via gog CLI with manual OAuth flow. Use when setting up Gmail integration, renewing expired OAuth tokens, or troubleshooting Gmail authentication on headless servers.
Install via ClawdBot CLI:
clawdbot install kai-jar/gmail-oauthGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://oauth2.googleapis.com/tokenCalls external URL not in known-safe list
https://console.cloud.google.comUses known external API (expected, informational)
cloud.google.comAI Analysis
The skill's external API calls (Google OAuth and Cloud Console) are consistent with its stated purpose of setting up Gmail API access. The 'unknown data sink' signal for oauth2.googleapis.com is a false positive, as this is the legitimate Google OAuth token endpoint required for the authentication flow. No credential harvesting, hidden instructions, or obfuscation is present.
Generated Feb 24, 2026
A customer service team uses this skill to set up Gmail API access for an AI agent that automatically categorizes and responds to customer inquiries. It enables the agent to read incoming emails, send templated replies, and manage labels for tracking issues, improving response times and organization.
A marketing agency integrates this skill to automate email campaign tracking and follow-ups. The AI agent monitors Gmail for campaign responses, sends personalized follow-up emails, and compiles reports on engagement metrics, streamlining outreach efforts and reducing manual workload.
An individual uses this skill to set up a personal AI assistant that manages email tasks, such as filtering spam, scheduling reminders from emails, and drafting replies. It helps organize inboxes and save time on daily email management for busy professionals.
A DevOps team deploys this skill on a headless server to monitor system alerts sent via Gmail. The AI agent reads emails for error notifications, triggers automated responses or alerts, and logs issues, ensuring reliable system oversight without manual intervention.
A company offers a subscription-based service that uses this skill to provide automated email management features, such as sorting, responding, and analytics. Revenue is generated through monthly or annual user fees, with tiers based on email volume and advanced features.
A consulting firm uses this skill to help clients set up and customize Gmail API integrations for their specific workflows. Revenue comes from project-based fees for implementation, training, and ongoing support, targeting businesses needing tailored email automation solutions.
A developer creates a free app with basic email management features using this skill, then monetizes through premium upgrades like advanced analytics, team collaboration tools, or priority support. Revenue is generated from in-app purchases or premium subscriptions.
💬 Integration Tip
Ensure the Google Cloud project is published to avoid token expiration issues, and use minimal scopes like gmail.modify to simplify the OAuth flow and reduce user permission prompts.
Scored Apr 19, 2026
Audited Apr 16, 2026 · audit v1.0
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.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
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).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.