Browser
Low RiskHeadless browser automation for web navigation, element interaction, and content extraction.
Editorial assessment
Where Browser fits
Browser is currently positioned as a automation skill for teams automating browsers, app flows, and web data collection. Based on the available metadata, the core job to be done is straightforward: headless browser automation for web navigation, element interaction, and content extraction.
The current description adds a practical clue about how the skill behaves in the field: a headless browser tool that automates web page navigation and interaction. extract clean, readable text content from any url, interact with page elements programmatically, and build web automation workflows. ideal for web scraping, testing, and data collection tasks. source: https://clawhub.ai/pshotts/browser version: 1.0.0. Combined with a manual install path, this makes Browser easier to evaluate than pages that only list a name and external link.
Browser can usually be trialed quickly, as long as the source and permissions still get reviewed. No explicit permission list is published in the current record, so verify the runtime surface in the source repository before rollout.
Best fit
teams automating browsers, app flows, and web data collection
Install surface
Ask the maintainer for a verified install path before adoption.
Source signal
Public source link available
Workflow tags
Headless browser, Web automation, and Scraping
Adoption posture
Install command not documented
Risk review
Can usually be trialed quickly, as long as the source and permissions still get reviewed
Best-fit workflows
Browser is best evaluated in automation environments where headless browser automation for web navigation, element interaction, and content extraction
Shortlist it when your team is actively comparing options for headless browser, web automation, and scraping workflows
Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption
About
A headless browser tool that automates web page navigation and interaction. Extract clean, readable text content from any URL, interact with page elements programmatically, and build web automation workflows. Ideal for web scraping, testing, and data collection tasks. Source: https://clawhub.ai/pshotts/browser Version: 1.0.0
Rollout checklist
Review the source repository at https://clawhub.ai/pshotts/browser and confirm the README, maintenance activity, and install notes are still current.
Document a reproducible install path before trying to operationalize Browser across multiple machines or contributors.
Capture the permissions and runtime surface during the first install, because the current record does not yet publish a detailed permission map.
Map Browser against the rest of your stack in headless browser, web automation, and scraping workflows so the team knows whether it is a standalone tool or a supporting utility.
FAQ
What does Browser help with?
Browser is positioned as a automation skill. Based on the current summary and tags, it is most relevant for teams automating browsers, app flows, and web data collection, especially when the workflow requires headless browser automation for web navigation, element interaction, and content extraction.
How should I evaluate Browser before using it in production?
Start with the source repository or original documentation, document a reproducible install path, and only move to production after you verify permissions, dependencies, and rollback steps.
Why does this page include editorial guidance instead of only the upstream docs?
ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.
Who is the best first user for Browser?
The best first evaluator is usually the operator or engineer already responsible for automation workflows, because they can verify whether Browser matches the current stack, risk tolerance, and maintenance expectations.
Related Skills
Electron App Automation with agent-browser and CDP
通过 Chrome DevTools Protocol 利用 agent-browser 实现对任何 Electron 应用（Slack、VS Code、Discord 等）的自动化控制。
Electron App Automation via CDP and agent-browser
通过 Chrome DevTools Protocol 和 agent-browser 实现对任何 Electron 应用（Slack、VS Code、Discord 等）的自动化控制。
Molt Market
Agent-to-agent freelance marketplace with escrow, milestones, and USDC payments.