
Browser Scrape
- 672 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
browser-scrape is a deprecated ruflo plugin skill shim that scrapes URLs via Bash for developers migrating to the browser-extract replacement with AIDefence and cognitive containers.
About
browser-scrape is a ruflo plugin skill deprecated since v0.2.0 and scheduled for removal in v0.3.0. It remains a thin backward-compatibility shim pointing developers to browser-extract, which adds RVF cognitive containers per session, mandatory AIDefence PII and prompt-injection gates, persistent browser-templates namespaces, and automatic browser-selectors updates for DOM drift recovery. The legacy skill accepts a URL argument and uses allowed tools Bash and Read. Developers should invoke browser-extract instead; browser-scrape only matters when older ruflo workflows or scripts still reference the v0.1 interface.
- browser-scrape
Browser Scrape by the numbers
- 672 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #549 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill browser-scrapeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 672 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
What replaces ruflo browser-scrape skill?
Use browser-scrape for development tasks
Who is it for?
Teams on ruflo plugin v0.1–v0.2 still calling browser-scrape who need a documented upgrade path to browser-extract.
Skip if: New scraping workflows—use browser-extract directly instead of the deprecated browser-scrape shim.
When should I use this skill?
User references browser-scrape, ruflo v0.1 scraping, or needs migration guidance to browser-extract.
What you get
Migration path to browser-extract, deprecation timeline notes, and legacy URL scrape shim behavior.
- Migration mapping to browser-extract
By the numbers
- Deprecated since plugin v0.2.0
- Scheduled removal in v0.3.0
Files
Browser Scrape (deprecated)
Deprecated since plugin v0.2.0. Removed in v0.3.0.
>
Use `browser-extract` instead. It provides the same scraping capability plus:
>
- RVF cognitive container per session (replayable, federatable)
- Mandatory AIDefence PII + prompt-injection gates
- Persistent browser-templates namespace for reusable recipes- Automatic browser-selectors namespace updates so DOM drift is recoverableMigration
| 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." >&2The 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.
Related skills
FAQ
Is browser-scrape still supported in ruflo?
browser-scrape is deprecated since ruflo plugin v0.2.0 and will be removed in v0.3.0. It is a thin compatibility shim; new work should use browser-extract for scraping plus AIDefence and cognitive containers.
What does browser-extract add over browser-scrape?
browser-extract replaces browser-scrape with RVF cognitive containers per session, mandatory AIDefence PII and prompt-injection gates, persistent browser-templates recipes, and automatic browser-selectors updates when DOM structure drifts.