browser-guide
Best practices for using the managed browser — handling login walls, CAPTCHAs, lazy-loaded content, paywalls, and tab cleanup.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install teamwiseflow-wiseflow-browser-guide
Repository
Skill path: wiseflow/skills/browser-guide
Best practices for using the managed browser — handling login walls, CAPTCHAs, lazy-loaded content, paywalls, and tab cleanup.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: TeamWiseFlow.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install browser-guide into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/TeamWiseFlow/wiseflow before adding browser-guide to shared team environments
- Use browser-guide for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: browser-guide
description: Best practices for using the managed browser — handling login walls, CAPTCHAs, lazy-loaded content, paywalls, and tab cleanup.
metadata:
{
"openclaw":
{
"emoji": "🌐",
"always": true,
},
}
---
# Browser Best Practices
Follow these rules whenever you use the `browser` tool to interact with web pages.
## 1. Login Prompts
When a page shows a login wall (sign-in form, "please log in" banner, OAuth redirect, etc.):
1. **Try the browser's built-in password manager first**: check whether the login form has auto-filled credentials from saved passwords. If so, use them to complete the login.
2. If no saved credentials are available, **do NOT make up usernames or passwords, and do NOT attempt to register a new account**.
3. Send a message to the user: _"xx 页面需要登录,浏览器中没有预存密码,请在浏览器中完成登录或注册,完成后请通知我。"_(xx 为页面标题).
4. Wait for the user to confirm.
5. If no response arrives within **5 minutes**, assume the user is unavailable and continue with whatever content is accessible.
## 2. Simple Verification / CAPTCHA
When a page shows a one-click verification challenge (e.g., a button labelled "去验证", "Verify", "I'm not a robot", or a simple checkbox):
1. Try clicking the verification button/checkbox directly.
2. Wait a few seconds for the page to refresh.
3. Take a snapshot to check whether normal content has loaded.
4. If the page now shows the expected content, continue your task.
## 3. Complex Verification Fallback
If the simple click in Step 2 above **fails** — the page still shows a challenge, the challenge is a puzzle/slider/image-selection CAPTCHA, or an error occurs:
1. **Do NOT retry blindly.** Stop attempting automated verification.
2. Send a message to the user: _"xx 页面有验证码,我无法解决,请在浏览器中完成,完成后请通知我。"_(xx 为页面标题).
3. Wait for the user to confirm.
4. If no response arrives within **5 minutes**, continue with whatever content is accessible.
## 4. Lazy-Loaded Content
When a page uses lazy loading (infinite scroll, "load more" sections, content that appears only after scrolling):
1. Before scrolling, assess whether the not-yet-loaded content is **relevant** to the current task.
2. If relevant, simulate human-like scrolling: scroll down incrementally, pause briefly between scrolls to allow content to load, then take a snapshot to capture the new content.
3. Repeat until the needed content is visible or no more new content loads.
4. Do NOT scroll too fast, do it as a human would. After 7 times of scrolling, you should stop this turn.
5. If not relevant, skip scrolling and work with what is already loaded.
## 5. Paywall / Subscription Walls
When a page indicates that content is behind a paywall or requires a specific subscription (e.g., "Subscribe to continue reading", "Continue reading with a WSJ subscription", premium-only banners):
1. Send a message to the user describing the situation: _"xx 页面需要订阅,请在浏览器中登录有效账号或者完成付费,完成后请通知我。"_(xx 为页面标题).
2. Wait for the user to confirm.
3. If no response arrives within **5 minutes**, continue with whatever content is accessible (summary, headline, or any visible excerpt).
## 6. QR Code Login
Some platforms (e.g., WeChat Official Account backend at mp.weixin.qq.com, Xiaohongshu creator center, X/Twitter) show a QR code on the login page instead of a password form. When this happens:
1. Use `snapshot` to locate the QR code image element on the page.
2. Take a screenshot scoped to the QR code area and send it to the user as an image with the message: _"xx 页面需要扫码登录,请用手机扫描截图中的二维码完成登录,完成后请通知我。"_(xx 为平台名称,例如"微信公众号后台"、"小红书创作者中心"、"X").
3. After sending, poll the page every **3 seconds** using `snapshot`: check for signs of successful login such as a URL change away from the login page, disappearance of the QR code element, or appearance of a username, avatar, or dashboard element.
4. Once a successful login is detected, resume the original task without waiting for the user to reply.
5. If no scan occurs within **3 minutes**, send the message: _"扫码超时,我将继续处理当前可访问的内容。"_ and continue with whatever is accessible.