Back to Registry
Google
WeChat
QQ
Google
View Author Profile
Official Verified
oauth-helper
Automate 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
skill-install — Terminal
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/helloliuyongsheng-bot/oauth-helperOr
OAuth Helper
Automate OAuth login with Telegram confirmation. Supports 7 major providers.
Supported Providers
| Provider | Status | Detection Domain |
|---|---|---|
| ✅ | accounts.google.com | |
| Apple | ✅ | appleid.apple.com |
| Microsoft | ✅ | login.microsoftonline.com, login.live.com |
| GitHub | ✅ | github.com/login/oauth |
| Discord | ✅ | discord.com/oauth2 |
| ✅ | open.weixin.qq.com | |
| ✅ | graph.qq.com |
Prerequisites
- Clawd browser logged into the OAuth providers (one-time setup)
- Telegram channel configured
Core Workflow
Flow A: Login Page with Multiple OAuth Options
When user requests to login to a website:
1. Open website login page
2. Scan page for available OAuth buttons
3. Send Telegram message:
"🔐 [Site] supports these login methods:
1️⃣ Google
2️⃣ Apple
3️⃣ GitHub
Reply with number to choose"
4. Wait for user reply (60s timeout)
5. Click the selected OAuth button
6. Enter Flow B
Flow B: OAuth Authorization Page
When on an OAuth provider's page:
1. Detect OAuth page type (by URL)
2. Extract target site info
3. Send Telegram: "🔐 [Site] requests [Provider] login. Confirm? Reply yes"
4. Wait for "yes" (60s timeout)
5. Execute provider-specific click sequence
6. Wait for redirect back to original site
7. Send: "✅ Login successful!"
Detection Patterns
URL patterns:
- accounts.google.com/o/oauth2
- accounts.google.com/signin/oauth
- accounts.google.com/v3/signin
Apple
URL patterns:
- appleid.apple.com/auth/authorize
- appleid.apple.com/auth/oauth2
Microsoft
URL patterns:
- login.microsoftonline.com/common/oauth2
- login.microsoftonline.com/consumers
- login.live.com/oauth20
GitHub
URL patterns:
- github.com/login/oauth/authorize
- github.com/login
- github.com/sessions/two-factor
Discord
URL patterns:
- discord.com/oauth2/authorize
- discord.com/login
- discord.com/api/oauth2
URL patterns:
- open.weixin.qq.com/connect/qrconnect
- open.weixin.qq.com/connect/oauth2
URL patterns:
- graph.qq.com/oauth2.0/authorize
- ssl.xui.ptlogin2.qq.com
- ui.ptlogin2.qq.com
Click Sequences by Provider
Account selector: [data-identifier], .JDAKTe
Auth buttons: button:has-text("Allow"), button:has-text("Continue")
Apple
Email input: input[type="email"], #account_name_text_field
Password: input[type="password"], #password_text_field
Continue: button#sign-in, button:has-text("Continue")
Trust device: button:has-text("Trust")
Microsoft
Account selector: .table-row[data-test-id]
Email input: input[name="loginfmt"]
Password: input[name="passwd"]
Next: button#idSIButton9
Accept: button#idBtn_Accept
GitHub
Email: input#login_field
Password: input#password
Sign in: input[type="submit"]
Authorize: button[name="authorize"]
2FA: input#app_totp
Metadata
AI Skill Finder
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skill Add to Configuration
Paste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-helloliuyongsheng-bot-oauth-helper": {
"enabled": true,
"auto_update": true
}
}
}Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.