pinchtablisted

# PinchTab Skill Use PinchTab as the lightweight browser layer in a three-layer stack: - Scrapling: extraction-first - PinchTab: low-token browser inspection and lightweight interaction - `playwright-ext`: reliable browser execution Keep `playwright-ext` as the final fallback path, and hand simpler extraction-heavy tasks back to Scrapling when a real browser is no longer necessary. ## When to Use This Skill Triggered by: - "pinchtab" - "browser automation with low token usage" - "multi-step website operation" - "tab/session management" - "agent browser control" ## Prerequisite Check ```bash pinchtab --version curl -fsS --max-time 3 http://127.0.0.1:9867/health codex mcp get playwright-ext ``` If you need to fetch installation assets from GitHub, use local proxy env: ```bash HTTP_PROXY=http://127.0.0.1:7897 HTTPS_PROXY=http://127.0.0.1:7897 <download-command> ``` ## Core Workflow 1. Verify PinchTab binary and health endpoint. 2. Use PinchTab first for navigation, snapshots, page text reads, and lightweight browser steps. 3. After meaningful actions, verify actual page state with URL/title/text/snapshot checks instead of trusting a transport-level success response. 4. If the task becomes pure extraction work, hand it to Scrapling for cheaper and more reproducible data collection. 5. If the first PinchTab action fails, run quick triage before considering fallback. 6. Compare repair cost vs fallback cost, then choose repair or `playwright-ext`. 7. In responses, explicit