browser-anti-bot-etiquette

Detect anti-bot blocks in browser automation and stop gracefully with user handoff.

38|6|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/7757/Fan-Browser-Agent --skill browser-anti-bot-etiquette-7757
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-anti-bot-etiquette
Source: https://github.com/7757/Fan-Browser-Agent/tree/main/skills/browser/browser-anti-bot-etiquette
Command: npx skills add https://github.com/7757/Fan-Browser-Agent --skill browser-anti-bot-etiquette-7757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a website blocks browser automation with CAPTCHAs, rate limits, interstitial challenges, or silent shadow-blocks, agents often enter destructive retry loops that escalate the block and waste turns. This Skill teaches the agent to recognize the block, stop driving the page, and hand control back to the user with a clear report. ## Core Features & Use Cases - Block Recognition: Identifies blank pages, reload loops, challenge text ("Verify you are human", 403/429), and silent shadow-blocks using browser observation tools. - Graceful Stop Rule: Permits at most one gentle recovery attempt (a single settle or reload), then captures a screenshot and challenge text as evidence before reporting. - Human Handoff: Routes CAPTCHAs and logins to the human in the visible browser instead of solving or brute-forcing them, and respects robots, paywalls, and rate-limit boundaries. - Use Case: While filling a form, the page starts showing a Cloudflare "Checking your browser" interstitial on every reload. The agent confirms the pattern, takes one screenshot, stops, and tells the user exactly what wall it hit and what it needs from them. ## Quick Start When the page keeps reloading with a "verify you are human" challenge, stop retrying, take a screenshot, and tell me what is blocking the task.

Frequently Asked Questions about browser-anti-bot-etiquette

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle CAPTCHAs during browser automation?▼

Do not solve CAPTCHAs programmatically. Pause the automation and let the human complete the reCAPTCHA, hCaptcha, or Turnstile challenge in the visible browser, then re-observe the page and continue from the post-challenge state.

What should a browser agent do when a site blocks automation?▼

Confirm the block is a pattern rather than a one-off failure, make at most one gentle recovery attempt such as a single reload, capture a screenshot and the challenge text, then stop and report the block type to the user.

How can I tell a shadow-block from a slow page load?▼

A shadow-block shows actions landing successfully while the page state never advances across repeated observations. A slow page eventually progresses after waiting, so use settle or wait commands first before concluding you are blocked.

Why does retrying a blocked page make things worse?▼

Repeated reloads and clicks raise your automation fingerprint with the site's bot detection, which can escalate the block to the user's IP address or account. One gentle recovery attempt followed by a clean stop is the correct response.

Can a browser agent bypass login walls or paywalls?▼

No. The agent should never guess credentials, brute-force logins, or circumvent paywalls. It should ask the user to authenticate manually in the visible browser and then resume on the authenticated page.

When should I not treat a page as blocked?▼

Do not treat ordinary slow loads or content below the fold as blocks. Use wait or settle commands for slow pages and scrolling for hidden content first; only repeated non-progress or explicit challenge text indicates a real block.