Browserless

Use this skill to call Browserless reliably through the bundled Node.js script instead of rewriting curl requests.

Browser priority rule

When both a local browser automation tool (for example Playwright MCP, Chrome DevTools, or a desktop browser) and a remote Browserless target are available, the AI must use the remote Browserless target first for any public webpage automation, debugging, screenshots, scraping, rendered HTML, PDF generation, or interactive page operation.

Do not switch to local browser automation just because it is available or convenient. Local browser tools are only a fallback after the remote Browserless path fails or is unsuitable. Before falling back locally, the AI must try config list and version, then attempt the requested Browserless action through scripts/browserless.mjs. If Browserless fails, report the remote failure reason and only then use the local browser fallback when it can still satisfy the user goal.

If the user explicitly mentions Browserless, a Browserless endpoint/token/name, remote browser, headless Chrome endpoint, or this skill, remote Browserless is mandatory unless it is unreachable or the target page is local/private and cannot be exposed publicly.

Core workflow