Run stealth Chromium browser automation with CloakBrowser
Use CloakBrowser as a supervised Playwright/Puppeteer-compatible browser runtime for high-friction browser automation and anti-bot test environments.
npx skills add agentskillexchange/skills --skill run-stealth-chromium-browser-automation-with-cloakbrowser
Use this skill when an operator needs a browser automation agent to run a Playwright- or Puppeteer-shaped workflow against sites that block stock automation, while keeping the task bounded, reviewable, and compliant with the target site’s rules. The operator installs CloakBrowser, swaps the browser launch/import in an existing automation script, configures proxies or locale/timezone only when required, and runs the agent task with human oversight of navigation, extracted data, and side effects. Invoke it for supervised QA flows, scraping/research jobs with permission, bot-detection compatibility testing, and agent browser sessions that need a real Chromium binary rather than JavaScript stealth patches. The boundary is a browser-runtime substitution for a concrete automation workflow; it is not a general web-scraping license, not CAPTCHA solving, not autonomous account abuse, and not a generic browser product listing.
What this skill actually does
Inputs and prerequisites: Python or Node.js, CloakBrowser package, Playwright/Puppeteer-compatible automation script, optional Docker/proxy configuration.
Setup notes: Install with `pip install cloakbrowser` for Python or `npm install cloakbrowser playwright-core` for Node.js; on first run the stealth Chromium binary downloads automatically. For Docker smoke testing, upstream documents `docker run –rm cloakhq/cloakbrowser cloaktest`.
Source and verification boundary: use https://cloakbrowser.dev/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.