oauth-helperAutomate OAuth login flows with user confirmation via Telegram. Supports 7 providers: Google, Apple, Microsoft, GitHub, Discord, WeChat, QQ. Features: - Auto-detect available OAuth options on login pages - Ask user to choose via Telegram when multiple options exist - Confirm before authorizing - Handle account selection and consent pages automatically
Install via ClawdBot CLI:
clawdbot install helloliuyongsheng-bot/oauth-helperGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://accounts.google.comUses known external API (expected, informational)
discord.comAudited Apr 16, 2026 · audit v1.0
Generated Mar 1, 2026
A social media manager needs to log into various analytics dashboards (e.g., Hootsuite, Buffer) that support OAuth logins from providers like Google or GitHub. This skill automates the login process across platforms, saving time and reducing manual errors by handling provider-specific flows and user confirmations via Telegram.
An e-commerce business uses multiple services (e.g., Shopify, Stripe) that require OAuth logins from Google or Microsoft for account linking. This skill streamlines setup by detecting available login options, confirming with users, and automating authorization, ensuring secure and efficient integration without manual intervention.
Developers frequently access coding platforms like GitHub, GitLab, or cloud services (e.g., AWS via Google login) that use OAuth. This skill assists by scanning login pages for supported providers, prompting selection via Telegram, and handling consent pages, reducing friction in daily workflows and project setups.
Students or educators log into learning management systems (e.g., Coursera, edX) that offer OAuth logins from Google or Microsoft. The skill automates the login flow by detecting options, confirming with users, and managing provider-specific steps, enabling quick access to courses and resources with minimal effort.
Businesses targeting Chinese markets use apps that require WeChat or QQ logins, which often involve QR code scans. This skill handles these providers by capturing QR codes, sending them to users via Telegram for mobile confirmation, and automating redirects, simplifying access for non-technical users.
Offer this skill as part of a monthly subscription for businesses needing automated OAuth logins across multiple platforms. Charge based on the number of providers supported or login frequency, providing ongoing updates and support for new OAuth integrations and detection patterns.
Provide a free version with basic OAuth support for limited providers (e.g., Google and GitHub) and a paid tier unlocking all 7 providers, advanced error handling, and priority Telegram response times. This attracts individual users while monetizing enterprises requiring comprehensive automation.
License this skill to digital agencies or IT service providers who integrate it into their own client offerings. Customize it with agency branding and specific provider configurations, charging a flat fee or per-client usage to streamline login processes for their customers.
💬 Integration Tip
Ensure the Clawd browser is pre-logged into supported OAuth providers and configure Telegram channels properly to avoid timeouts and errors during user confirmations.
Scored Apr 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.
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.