pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, log into sites with a persistent profile, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API when the CLI is unavailable. Prefer this skill for token-efficient browser work driven by stable accessibility refs such as `e5` and `e12`.
Best for Web testing automationWorks with GitHub
⌘source
- author
@pinchtab- language
- Go
★8.8kstars
641forks
Apr 21, 2026
✦overview.md
Key Features
- ·Automates browser interactions via CLI commands
- ·Uses stable accessibility references for reliable element targeting
- ·Extracts page text with low token overhead
- ·Manages persistent browser profiles and instances
- ·Supports screenshots, PDF exports, and form filling
- ·Provides HTTP API fallback for specific use cases
Use Cases
- →Automating login sequences for testing web applications
- →Scraping text content from dynamic websites
- →Filling and submitting web forms in batch processes
- →Generating screenshots or PDFs of web pages for documentation
- →Maintaining logged-in sessions across multiple automation tasks
Best for
- ✓Web testing automation
- ✓CI/CD pipelines requiring browser interactions
- ✓Data extraction from interactive websites
Not ideal for
- !Simple HTTP API calls without browser rendering
- !One-off manual browser tasks
FAQs
name
pinchtab
description
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, log into sites with a persistent profile, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API when the CLI is unavailable. Prefer this skill for token-efficient browser work driven by stable accessibility refs such as `e5` and `e12`.
metadata:{"openclaw":{"requires":{"bins":["pinchtab"],"anyBins":["google-chrome","google-chrome-stable","chromium","chromium-browser"]},"homepage":"https://github.com/pinchtab/pinchtab","install":[{"kind":"brew","formula":"pinchtab/tap/pinchtab","bins":["pinchtab"]},{"kind":"go","package":"github.com/pinchtab/pinchtab/cmd/pinchtab@latest","bins":["pinchtab"]}]}}
Browser Automation with PinchTab
PinchTab gives agents a browser they can drive through stable accessibility refs, low-token text extraction, and persistent profiles or instances. Treat it as a CLI-first browser skill; use the HTTP API only when the CLI is unavailable or you need profile-management routes that do not exist in the CLI yet.
Preferred tool surface:
- Use
pinchtabCLI commands first. - Use
curlfor profile-management routes or non-shell/API fallback flows. - Use
jqonly when you need structured parsing from JSON responses.
Core Workflow
Every PinchTab automation follows this pattern:
- Ensure the correct server, profile, or instance is available for the task.
- Navigate with
pinchtab nav <url>orpinchtab instance navigate <instance-id> <url>. - Observe with
pinchtab snap -i -c,pinchtab snap --text, orpinchtab text, then collect the current refs such ase5. - Interact with those fresh refs using
click,fill,type,press,select,hover, orscroll. - Re-snapshot or re-read text after any navigation, submit, modal open, accordion expand, or other DOM-changing action.
Rules:
$install
1-click copynpx skills add pinchtab/pinchtab --skill pinchtabSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.