browsh

**Quick judgment**: This skill is a solid option if you explicitly want a modern text-based browser that can handle JavaScript-heavy sites through a terminal, but it depends on external binaries (Browsh and Firefox) and an interactive TUI, which limits portability and full automation. Best suited for power users or human-in-the-loop workflows, not for headless scraping. **Strengths** - Renders complex, modern web pages via headless Firefox while presenting them in a terminal-friendly text UI. - Filters ads and reduces bandwidth usage, good for constrained or remote environments. - Works well over SSH or in tmux/PTY sessions when a full GUI browser is unavailable. **Key risks / limitations** - **Environment dependencies**: Requires both `browsh` and `firefox` to be installed and in `PATH`; will fail in minimal or locked-down containers. - **Interactive TUI**: Designed for interactive use inside a PTY. This makes it harder to use for fully automated data extraction compared with HTTP/HTML-focused skills. - **Resource usage**: Headless Firefox is relatively heavy; may be slow or resource-intensive on small machines. **Recommended scenarios** - You are comfortable with terminal TUIs and need occasional, interactive browsing of complex sites in a non-GUI environment. - You’re operating over SSH or on servers where installing Firefox and Browsh is acceptable. - You value bandwidth savings and ad filtering more than pixel-perfect rendering or GUI convenience. **Not ideal for** - Purely automated scraping or structured data extraction from the web. - Minimal environments where installing Firefox/Browsh is not possible. - Users unfamiliar with keyboard-driven terminal interfaces.