Run lightweight headless browser automation with Obscura
Use Obscura as a lightweight headless browser runtime for agent scraping, page inspection, parallel extraction, and CDP-driven Playwright or Puppeteer workflows.
npx skills add agentskillexchange/skills --skill run-lightweight-headless-browser-automation-with-obscura
Use Obscura when an agent needs a fast headless browser runtime for JavaScript-rendered pages, scraping, page inspection, screenshots, or browser tasks that can run through a CLI, CDP server, Puppeteer, or Playwright. It is built in Rust, runs V8, supports Chrome DevTools Protocol connections, and documents direct fetch, parallel scrape, proxy, stealth, Docker, and Playwright/Puppeteer integration paths.
What this skill actually does
Invoke this instead of a normal browser or hosted browser product when the operator wants a self-hosted automation runtime that can be scripted by an agent, scaled for repeated scraping jobs, or swapped into existing CDP-based browser automation code. The scope boundary is the browser execution layer and repeatable automation commands; it is not a general scraping platform, proxy vendor, hosted cloud browser listing, or broad web automation strategy.
Inputs and prerequisites: Obscura binary or Docker image; optional puppeteer-core or playwright-core for CDP-driven automation; optional proxy configuration for scraping workflows.
Setup notes: Download the latest platform archive from https://github.com/h4ckf0r0day/obscura/releases, extract the obscura and obscura-worker binaries together, or run docker run -d –name obscura -p 127.0.0.1:9222:9222 h4ckf0r0day/obscura. Build from source with git clone https://github.com/h4ckf0r0day/obscura.git && cd obscura && cargo build –release.
Source and verification boundary: use https://github.com/h4ckf0r0day/obscura 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.