
Auth Manager
- 35 installs
- 82 repo stars
- Updated August 2, 2026
- aaaaqwq/claude-code-skills
auth-manager is a Claude Code skill that manages web login and session state across platforms using OpenClaw's built-in browser with a single shared Chrome profile and periodic availability checks.
About
auth-manager is a Claude Code skill (documented in Chinese) that manages web login and session state across platforms using OpenClaw's built-in browser and a single shared Chrome profile. A developer uses it to periodically check whether logins are still valid, authorize new platforms, and let other agents inherit those sessions. It prefers fast curl/CLI checks and falls back to browser snapshots, with a cron job that alerts on expired sessions.
- Manages web login/session state across platforms using OpenClaw's built-in browser under one shared Chrome profile
- Checks login validity via curl/CLI first (gh auth status, API tokens), falling back to browser snapshots for rendered si
- Runs a scheduled cron (09:00/21:00) that alerts on expired sessions and distinguishes timeout errors from real expiry
Auth Manager by the numbers
- 35 all-time installs (skills.sh)
- Ranked #1,185 of 2,719 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
auth-manager capabilities & compatibility
free; uses existing platform logins
- Capabilities
- session management · login check · auth monitoring · platform authorization
- Works with
- github · chrome
- Use cases
- orchestration
- Pricing
- Free
What auth-manager says it does
网页登录态管理。使用 OpenClaw 内置 browser (profile=openclaw) 统一管理各平台登录状态,定期检查可用性。
npx skills add https://github.com/aaaaqwq/claude-code-skills --skill auth-managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 35 |
|---|---|
| repo stars | ★ 82 |
| Last updated | August 2, 2026 |
| Repository | aaaaqwq/claude-code-skills ↗ |
What it does
A developer uses it to keep browser login sessions valid across many platforms and share them among agents.
Who is it for?
Maintaining and monitoring browser login sessions shared across multiple agents
Skip if: Setups not using OpenClaw's built-in browser; fbu/fast-browser-use is explicitly forbidden
When should I use this skill?
Checking or refreshing login/session state across platforms, or authorizing a new platform login
What you get
- session availability status file
- expiry alerts
- authorized platform logins
By the numbers
- 9 known platforms configured (GitHub, AIXN, Polymarket, LinuxDo, X, etc.)
- Auth-check cron runs twice daily at 09:00 and 21:00
Files
Auth Manager v4.0 — 平台登录态管理
统一使用 OpenClaw 内置 browser (profile=openclaw),所有平台共享同一个 Chrome profile。
⚠️ 禁止使用 fbu / fast-browser-use,已废弃。
架构 — 单一 Profile 模型
~/.openclaw/browser/openclaw/user-data/ ← 唯一的 Chrome profile(内置 browser)
~/.openclaw/auth-platforms.json ← 平台配置
~/.openclaw/auth-session-state.json ← 检查结果状态为什么统一?
- 所有 agent(quant/ops/main 等)共享同一 browser profile
- 一次登录,全部可用。不存在"这个 agent 没登录"的问题
- OAuth 链式登录(如Provider-A 依赖 GitHub)自动继承
核心职责
职责 1: 检查登录态(定期 cron)
优先级:curl/CLI > 内置 browser
方法 A: curl/CLI 检查(快速、不占资源)
# GitHub — 最可靠
gh auth status 2>&1
# AIXN — curl API
TOKEN=$(python3 -c "import json; print(json.load(open('/home/aa/.openclaw/chrome-profiles/provider-session.json')).get('token',''))" 2>/dev/null)
curl -s --max-time 10 'https://ai.9w7.cn/api/user/info' -H "Authorization: Bearer $TOKEN"
# Provider-A — curl
COOKIE=$(python3 -c "import json; print(json.load(open('/home/aa/.openclaw/chrome-profiles/your-provider-session.json')).get('cookie',''))" 2>/dev/null)
curl -s --max-time 10 'https://your-provider.example.com/api/user/info' -H "Cookie: $COOKIE"方法 B: 内置 browser 检查(需要渲染的站点)
# 导航到目标页面
browser(action='navigate', targetUrl='<check_url>', profile='openclaw')
# 等待加载后截取快照
browser(action='snapshot', compact=true, maxChars=2000, profile='openclaw')适用平台:Polymarket、LinuxDo、X、抖音、小红书
判定逻辑:
- 快照包含
logged_in_indicators关键词 → ✅active - 快照包含
login_page_indicators关键词 → ❌expired - 超时/网络错误 → ⚠️
error(不是 expired!区分清楚)
职责 2: 新平台授权
当需要为新平台登录时:
# 1. 用内置 browser 打开登录页
browser(action='navigate', targetUrl='https://platform.com/login', profile='openclaw')
# 2. 截图给用户确认页面
browser(action='screenshot', profile='openclaw')
# 3. 如果需要用户操作(扫码等),等待用户确认后再 snapshot 验证
browser(action='snapshot', compact=true, profile='openclaw')登录成功后,cookie/localStorage/IndexedDB 自动保存在 ~/.openclaw/browser/openclaw/user-data/。
职责 3: 其他 agent 使用登录态
所有 agent 调用内置 browser 时自动继承登录态:
# quant agent 访问 polymarket — 自动已登录
browser(action='navigate', targetUrl='https://polymarket.com', profile='openclaw')
# ops agent 检查 github — 自动已登录
browser(action='navigate', targetUrl='https://github.com', profile='openclaw')无需任何额外配置。profile=openclaw 是共享的。
平台配置
~/.openclaw/auth-platforms.json:
{
"platforms": {
"platform_id": {
"name": "显示名称",
"check_url": "https://example.com/dashboard",
"login_url": "https://example.com/login",
"check_method": "browser|curl|cli",
"logged_in_indicators": ["关键词1", "关键词2"],
"login_page_indicators": ["登录", "Sign in"],
"enabled": true
}
}
}已知平台特性(9个)
| 平台 | 检查方式 | 登录方式 | 账号 | 备注 |
|---|---|---|---|---|
| GitHub | gh auth status (CLI) | 账密/OAuth | aAAaqwq | 最可靠 |
| AIXN | curl API | 账密 | 2067089451@qq.com | session.json token |
| Provider-A | curl API | GitHub OAuth | github_210817 | 依赖 GitHub 登录态 |
| Polymarket | 内置 browser | 钱包/OAuth | Portfolio $41.62 | 检查"portfolio"关键词 |
| LinuxDo | 内置 browser | 账密/OAuth | aaqwqaa68 | Cloudflare 站点 |
| X (Twitter) | 内置 browser | 账密 | @Daniel_Li666 | 可能有验证码 |
| 小红书 | 内置 browser | App扫码/手机号 | 69464fc5... | check: xiaohongshu.com/user/profile/me |
| 内置 browser | 账密/OAuth | Jealous-Carrot-9574 | reCAPTCHA 需人工通过 | |
| 抖音创作者 | 内置 browser | App扫码 | aa (61747337251) | check: creator.douyin.com/creator-micro/home |
状态文件格式
~/.openclaw/auth-session-state.json:
{
"checkedAt": "2026-03-07T09:00:00+08:00",
"platforms": {
"github": { "status": "active", "account": "aAAaqwq", "method": "cli" },
"polymarket": { "status": "active", "detail": "Portfolio $41.56", "method": "browser" }
}
}status 值: active | expired | error
Cron 任务
- Auth 检查 cron:
1f2eb5a5— 每天 09:00/21:00 执行 - 过期则推送告警到 DailyNews 群
- 全部正常则静默
铁律 ⚠️
1. 禁止使用 fbu / fast-browser-use — 已废弃 2. 统一使用 `profile='openclaw'` — 所有 browser 操作 3. 旧 profile 目录 `~/.openclaw/chrome-profiles/<platform>/` 已废弃,仅保留 session.json 供 curl 读取 token/cookie 4. 超时 ≠ 过期 — 网络问题标记为 error,不标记为 expired 5. 每个检查最多 15 秒 — 避免阻塞
迁移说明(v3 → v4)
- 旧版:每个平台独立 fbu Chrome profile (
~/.openclaw/chrome-profiles/<platform>/) - 新版:所有平台共享内置 browser profile (
~/.openclaw/browser/openclaw/user-data/) - 内置 browser 已有全部平台的 IndexedDB/cookie 数据,无需手动迁移
- 旧
chrome-profiles/目录已于 2026-03-07 彻底删除(释放 ~1.7GB) - 旧
<platform>-session.json文件也已删除(token 已过期)
🔐 Browser & Auth 统一规则
所有 agent 必须遵守。这是全局规则,不是建议。
唯一 Chrome Profile
路径: ~/.openclaw/browser/openclaw/user-data/
调用: browser(profile='openclaw')所有浏览器操作统一使用 `profile='openclaw'`。一个 profile,所有 agent 共享。
❌ 禁止
fast-browser-use/fbu— 已废弃(除非 Daniel 明确要求用于特殊场景省 token)~/.openclaw/chrome-profiles/<platform>/— 旧 profile 目录,不再使用- 启动独立 Chrome 进程(
google-chrome --user-data-dir=...)
✅ 必须
- 浏览器操作 →
browser(action=..., profile='openclaw') - 登录态检查 → 优先 curl/CLI,备选内置 browser
- 新平台登录 →
browser(action='navigate', targetUrl='...login', profile='openclaw')
平台检查速查
| 平台 | 方式 | 命令 |
|---|---|---|
| GitHub | CLI | gh auth status |
| AIXN | curl | curl -H "Authorization: Bearer $TOKEN" https://ai.9w7.cn/api/user/info |
| Provider-A | curl | curl -H "Cookie: $COOKIE" https://your-provider.example.com/api/user/info |
| Polymarket | browser | browser(navigate → polymarket.com/portfolio, profile=openclaw) |
| LinuxDo | browser | browser(navigate → linux.do, profile=openclaw) |
| X | browser | browser(navigate → x.com/home, profile=openclaw) |
| 抖音 | browser | browser(navigate → creator.douyin.com, profile=openclaw) |
| 小红书 | browser | browser(navigate → creator.xiaohongshu.com, profile=openclaw) |
文件位置
| 文件 | 用途 |
|---|---|
~/.openclaw/browser/openclaw/user-data/ | 唯一 Chrome profile |
~/.openclaw/auth-platforms.json | 平台配置(URL、关键词) |
~/.openclaw/auth-session-state.json | 最近检查结果 |
~/clawd/skills/auth-manager/SKILL.md | 完整 skill 文档 |
~/clawd/skills/auth-manager/BROWSER_RULES.md | 本文件 |
Related skills
FAQ
How does it check login status?
It prioritizes curl/CLI checks (like gh auth status or API token requests) and falls back to built-in browser snapshots for sites that need rendering, judging by logged-in vs login-page keyword indicators.
Why one shared profile?
All agents share the profile=openclaw Chrome profile, so a single login is usable everywhere and chained OAuth logins are inherited automatically.