About browser-scrape
A deprecated skill that redirects browser-scraping requests to `browser-extract`. It emits a deprecation notice and does not preserve extraction behavior beyond forwarding the request.
Key features
- 01Redirects requests to `browser-extract`
- 02Emits a deprecation notice
- 03Supports migration to `--template` usage
Use cases
- 01Replace an old `/browser-scrape` invocation
- 02Move template-based scraping to `browser-extract`
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/browser-scrapein Claude Code to confirm it loaded.
Details
From the project READMEBrowser Scrape (deprecated)
Deprecated since plugin v0.2.0. Removed in v0.3.0.
Use
browser-extractinstead. It provides the same scraping capability plus:
- RVF cognitive container per session (replayable, federatable)
- Mandatory AIDefence PII + prompt-injection gates
- Persistent
browser-templatesnamespace for reusable recipes- Automatic
browser-selectorsnamespace updates so DOM drift is recoverable
Migration
| v0.1 invocation | v0.2 equivalent |
|---|---|
/browser-scrape <url> | /browser-extract <url> |
/browser-scrape <url> (with template intent) | /browser-extract <url> --template <name> |
Manual selector storage in browser-patterns namespace | Automatic — browser-extract writes to browser-templates and browser-selectors |
Behavior of this shim
This skill delegates to browser-extract. Calling it emits a deprecation notice and proceeds.
# This skill is intentionally minimal — it just points the agent at the new skill.
echo "browser-scrape is deprecated; running browser-extract instead." >&2
The deprecation notice is captured in the agent's transcript so callers see the remediation. There is no behavior preserved here beyond the redirect — if you depended on a specific extraction shape, port to browser-extract and use --template to encode it.