scrape

## When to invoke Use to extract data from a page — "scrape", "get data from", "pull", "extract from", "what's on this page". Read-only: for form fills, clicks, or submissions use the browse daemon's interaction verbs, not this skill. # /scrape — Pull data from a page {{include lib/snippets/browse-setup.md}} If `BROWSE_NOT_AVAILABLE`: fall back to `curl` + an HTML parse for static pages (note that JS-rendered content and screenshots are unavailable), or stop and tell the user the browse shim is needed. ### 0. Match — is this already a skill? Before prototyping a new scrape, check whether a codified skill already covers this target: ```bash ls ~/.claude/skills/ 2>/dev/null | grep -iE '<site-or-domain-keyword>' || echo "NO_MATCH" ``` If a matching skill exists, suggest running it (`/that-skill`) instead of re-deriving the flow. Only prototype when there's no match. ### 1. Pin the target Confirm the URL and exactly which fields the user wants (single record, or a list with per-item fields). If it's ambiguous, ask once with AskUserQuestion. ### 2. Navigate and inspect ```bash "$B" goto <url> "$B" text # full visible text — orient yourself ``` For structured values, pull them by selector with `js` (the stateless shim evaluates against a fresh load) — e.g. a list of prices: ```bash "$B" js "Array.from(document.querySelectorAll('.price')).map(e => e.textContent.trim())" ``` If the page is interactive (needs a click to reveal data), start the daemon and use a ...