Menu
DEPRECATED in v0.2.0 -- use browser-extract instead; this is a thin shim for backward compatibility, removed in v0.3.0
Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation
| name | browser-scrape |
| description | DEPRECATED in v0.2.0 -- use browser-extract instead; this is a thin shim for backward compatibility, removed in v0.3.0 |
| argument-hint | <url> |
| allowed-tools | Bash Read |
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
| 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 |
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.