browser-scrape

Redirects deprecated browser scraping invocations to the browser-extract skill.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill browser-scrape
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-scrape
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-browser/skills/browser-scrape
Command: npx skills add https://github.com/ruvnet/claude-flow --skill browser-scrape

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves backward compatibility for workflows still calling the deprecated browser-scrape command, ensuring old invocations continue to work while guiding users toward the modern browser-extract replacement.

Core Features & Use Cases

  • Deprecation Shim: Accepts the legacy /browser-scrape <url> invocation and delegates execution to browser-extract.
  • Migration Guidance: Provides a mapping table showing how v0.1 commands translate to v0.2 equivalents, including template usage.
  • Use Case: A team with automation scripts written against plugin v0.1 can keep running /browser-scrape <url> without breakage while planning their migration to browser-extract before v0.3.0 removes this shim.

Quick Start

Run the browser-scrape skill with a target URL and it will emit a deprecation notice and delegate the scraping to browser-extract.

Frequently Asked Questions about browser-scrape

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

FAQPage Schema
How do I migrate from browser-scrape to browser-extract?

Replace `/browser-scrape <url>` with `/browser-extract <url>` in your commands. If you relied on templates, use `/browser-extract <url> --template <name>` instead, and selector storage moves automatically to the browser-templates and browser-selectors namespaces.

What is the replacement for the browser-scrape skill?

browser-extract is the replacement, adding an RVF cognitive container per session, AIDefence PII and prompt-injection gates, and persistent browser-templates and browser-selectors namespaces for reusable recipes and DOM drift recovery.

Does browser-scrape still work after plugin v0.2.0?

Yes, it works as a thin shim in v0.2.x: it prints a deprecation notice to stderr and delegates to browser-extract. It is scheduled for removal in v0.3.0, so migrate before upgrading.

Why does browser-scrape print a deprecation notice?

The notice is written to stderr and captured in the agent transcript so callers see the remediation path. The shim preserves no behavior beyond the redirect, so any custom extraction shape must be ported to browser-extract templates.

When should I stop using browser-scrape?

Stop using it before upgrading to plugin v0.3.0, when the shim is removed. Port any custom extraction logic to browser-extract using the --template flag to encode reusable recipes.